Dear William, CEN/tc251 EN13606 part 2 describes "this model that allows us to express it ... unbound to specific technology".
Further there is the list: - Clinical concept descriptions: -- Excel sheets, expressed as text in columns, -- CEN/tc251 or openEHR Archetypes, that are formally expressed as constraints on an underlying UML model (part 1 of EN13606), -- HL7 Templates, that are formally expressed as constraints on a derivative of an underlying (Viso) model (the HL7 v3 RIM). At this point in time CEN and HL7 are in the process of harmonising part of of the EN13606 with the work on the Clinical statement. The moment when HL7 starts to deploy the method, described in the HL7 Development Framework in stead of the Message Development Frame work, more intermediate artefacts of HL7 will be expressed in UML. Then HL7 Templates and CEN/openEHR Archetypes can become the same thing. Not only expressing the same thing but being the same thing at the level of the computer. Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 On 5-mei-2006, at 8:05, Williamtfgoossen at cs.com wrote: > > I look forward to further harmonisation work on archetypes and > templates. HL7 template group is currently working on applying > ADL / CEN 13606-2 for further work, but given the discussion above, > we might need to look for a model that allows us to express it > operational, but unbound to specific technology. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060505/7f32b523/attachment.html>
