I apologise for my rather irreverant previous post....that was an oops. Are openEHR template specialisation hierarchies a real possibility? This would be particularly useful in message profiles, and conformance level assertions made by systems.
Btw: would consider the openEHR RM classes archetypes if I was to express them somehow using CEN13606, and HL7 V3 RIM further again specialised archetypes. The choice is how general is your reference model and the assumed semantic level that comes with that. HL7 V3 templating is the using the same method whether archetyping or templating in openEHR speak, there are also many aspects of openEHR style templating in HL7 message development itself. This becomes N level modelling... - openEHR has at least 3, RM, archetype, template - HL7 V3 at least 4, RIM, DMIM, RMIM, HL7 Template (CIM + CMET) All of these have some usage description...and some 'rules' e.g must have a single entry point, must be serialisable etc. Picking your level for expressing a wire protocol is another choice; that would be in some ways be entirely based on your level of generality desired. Regards, Brett Esler -----Original Message----- From: openehr-clinical-boun...@openehr.org [mailto:openehr-clinical-bounces at openehr.org] On Behalf Of Thomas Beale Sent: Wednesday, 21 February 2007 1:52 AM To: For openEHR clinical discussions Subject: Re: CCR and openehr Heath Frankel wrote: > Andrew & Ogi, > openEHR Templates are not Forms, they are aggregations of archetypes > with further constraints. The scope of an openEHR template can be > compared with a form but define the data structure of that form. > However openEHR Templates can be used to drive the design and > generation of forms as is done using the Ocean Template Designer. The > designer has a Template Design panel where archetypes are dragged from > a archetype repository view onto the panel building up the template > structure and the archetype nodes are constrained as required in the > template. The Form Design panel allows nodes from the Template to be > dragged onto the Form and formatted as designed. This latter step is > purely an application customisation step whereas the former template > design is a knowledge development step possible used by more than one > application. > To further clarify: an openEHR template can be used to: - create a visual form (as described above by Heath) - to create a message definition, i.e. an XML-schema corresponding to the template - to create a means of displaying data, using XML/Xslt - create other generated artifacts, e.g. code skeletons, wsdl specifications etc Logically, an openEHR template corresponds to a localised specfication for a chunk of content, based on use of archetypes (which themselves may be very general). - thomas beale _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical _______________________________________________ openEHR-clinical mailing list openEHR-clinical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
