Just to clarify one thing about these Template Data Schemas, they are NOT intended for exchange across system boundaries. They are used as an intermediary format, which is normalised based on archetypes and templates, for the purposes of integration between system components (note that I use the term system in the sense of a system of systems within an enterprise). For example, to import HL7 V2 messages into openEHR it is easier to move the data into an intermediate form and then into openEHR. Similarly, to export data from a proprietary database to openEHR, you can go via a intermediate form. The key here is that the intermediate form are based on normalised content models and can be the same for different data sources. It allows developers to work with the content models without being openEHR experts, resulting in reduced barriers to the take up of openEHR. The real clincher, is that there is a single transformation from any of these template-based XML schemas into openEHR. We are refining the rules for generating these schemas and the openEHR transformation and will share it with the openEHR community soon.
Regards ? Heath ? Heath Frankel Product Development Manager Ocean Informatics Ground Floor, 64 Hindmarsh Square Adelaide, SA, 5000 Australia ? ph:?+61 (0)8 8223 3075 mb: +61 (0)412 030 741 email:?heath.frankel at oceaninformatics.com > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Thomas Beale > Sent: Friday, 23 November 2007 6:17 PM > To: For openEHR technical discussions > Subject: Re: Compact XML format...? > > > I believe you are referring to what we call Template Data Schemas > (TDSs). These are an alternate schema-per-message approach, where one > template generates one schema - in such schemas, you find tagnames > coming from the archetypes, e.g. "systolic" rather than the generic > openEHR tag names. This is similar to HL7, except that here the message > schemas are generated from content models (archetypes & templates) > rather than hand-built as in HL7. What this does is provide a message > capability to openEHR based on the content models, just like any other > generated artifact, e.g. Xforms or HML or code skeletons. We have only > just developed this capability (it is still under test), and we expect > it to be attractive to certain types of provider, e.g. pathology > software vendors and labs, since it means they can use 'simple XML' to > transfer their result messages, rather than having to understand all > that weird openEHR stuff. This approach means any message (e.g. anything > currently expressed in HL7 or Edifact) can now be generated from > archetypes and templates (obviously the literal XML is different, we > don't use RIM-based XML, but the logical purpose is exactly the same). > > I will find out about example messages. > > I would expect that we will provide the relevant specifications for this > process to openEHR.org at some point, when it has stabilised. > > - thomas beale > > > Erik Sundvall wrote: > > Hi! > > > > During Medinfo2007 I believe Ocean Informatics presented a compact XML > > format for interchange of predefined information snippets that was > > used for integration purposes. I do not believe it was based on the > > official RM-schemas that cover everything but instead a compact form > > for a specific purpose (e.g. using a specific template or set of > > archetypes). Does anybody understand what I am referring to or was I > > just dreaming? > > > > Could somebody please send a snippet with an example of that format > > and possibly some description or documentation. I believe a brief > > discussion regarding this on the list could be valuable since there > > are use cases where having a standardized such a format would be of > > value. > > > > Best regards, > > Erik Sundvall > > erisu at imt.liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-227579 > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > > > > > > -- > please change your address book entry for me to > Thomas.Beale at OceanInformatics.com > *Thomas Beale* > /Chief Technology Officer/ Ocean Informatics > <http://www.oceaninformatics.com/> > > Chair Architectural Review Board, /open/EHR Foundation > <http://www.openehr.org/> > Honorary Research Fellow, University College London > <http://www.chime.ucl.ac.uk/> > > > * > * > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
