There is only one openEHR implementation, the template data schemas are just a tool to transform data from other formats into and out of the openEHR reference model using the semantics of the clinical archetypes models. The TDS are not intended to replace openEHR, but enable it for those that are not openEHR compliant. The result of using a TDS is openEHR for standard information sharing. The reality is, most systems are not built on a particular standard reference model such as HL7 or openEHR, they are proprietary models which move their data into these standard models for interoperable exchange. The TDS provides a means for these systems to move their data into clinical data models and mechanically transform them into technical data models, such as openEHR. Think of it as standard mechanism for data transformation rather than a standard data exchange, where the semantics of the archetypes are maintained at each stage in the pipeline.
Heath From: [email protected] [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Williamtfgoossen at cs.com Sent: Saturday, 24 November 2007 6:46 AM To: openehr-technical at openehr.org Subject: Antw: Re: Compact XML format...? In een bericht met de datum 23-11-2007 16:55:12 West-Europa (standaardtijd), schrijft timothywayne.cook at gmail.com: IHMO, any system that is "not interested in the full semantics of the openEHR model" is not compliant with openEHR and is just a stand alone system. Much like the various HL7 implementations that require interface engines to make the transition. This seems only relevant to compare with the HL7 v2. V3 has no various implementations, but one standard implementation of messages. The v3 content can vary, similar to archetype variations. Sincerely yours, dr. William TF Goossen director Results 4 Care b.v. De Stinse 15 3823 VM Amersfoort email: Results4Care at cs.com phone + 31654614458 fax +3133 2570169 Dutch Chamber of Commerce number: 32121206 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071124/83bd2f97/attachment.html>
