Hi Erik, I will forward a schema based on a Microbiology Result generated using the Ocean Template Designer separately.
See comments below, you have stated exactly the problem that the TDS was designed to solve. We are using this approach to integrate existing vendor software to the Ocean EhrBank where the vendor has no openEHR expertise or desire to do so (yet), they just want to have an openEHR repository. Heath > The reason for asking is that in a context where openEHR/13606 has > been compared to HL7 (mainly v3 I believe) some parties claimed it > would be easier for vendors to support HL7 than openEHR. In practice, > what they mean is probably that they are used to follow (map their > internal/legacy structures to) specific HL7 xml schemas that come out > after the long HL7 modeling process. I doubt that the vendors in this > case internally are using any HL7 v3 models. > > This is sometimes forgotten when comparing HL7 and openEHR. > > So far we have had a look at some fairly equivalent examples of XML > instances (e.g. blood pressure) from HL7 CDA (v2) and openEHR RM. Both > were fairly easy to understand when knowing the underlying models (HL7 > RIM +CDA and openEHR RM+AM) and both were a bit verbose if you were > just interested in the blood pressure. To be honest if I was a vendor > not interested in underlying models I'd probably prefer whichever I > was already used to and had people trained to work with - since none > of them tries to make life easier to me by being tailored to the > specific use case. [Heath Frankel] As you know, a template is the knowledge artefact designed for a particular use case, the TDS is a technical artefact to support the implementation of that use case. > To validate clinically both were dependent on other artifacts (HL7 > Templates or openEHR archetypes). An information provider not > interested in the underlying validation mechanisms could easily > produce data instances that are clinically invalid even though they > are valid from the perspective of the respective XML schemas. Does the > TDS-approach produce an XML schema that enforces more or all of the > specific archetype+template semantics? If not, could it be enhanced to > do that? If so I believe that some safety would be gained - if data > providers do not care to learn the full semantics of openEHR then at > least their schema-based XML-validators would enforce some of the > semantics. [Heath Frankel] Most but not all the semantics of the archetypes and templates are represented in the TDS. The reason it is not all, is due to the limitations of XML schema to do assertions between XML elements. > If we could standardize the TDSs and have accompanying standard > determinstic transformation mechanism then openEHR would have a > competitive advantage in the "just give me a simple XML schema and > instance examlpe" use-case. A use case more important than one might > think at first... [Heath Frankel] The TDS is simply a set of XML elements with names from the archetypes. If you look at the schema in an graphical XML tool such as Oxygen you will see a tree that has the same structure as the template tree displayed in the Ocean Template Designer. > Sometimes the use case is to decide on an XML format (for data > exchange) based on one of the following > 1. HL7 CDA > 2. 13606/openEHR > 3. A custom tailored XML schema > > Imagine that we using something like TDS could give an easy-to-produce > alternative to 3 that with some deterministic transformations at the > receiver also conforms to 2. (An open or free tool to produce the > schema would be of tremendous help of course.) [Heath Frankel] This is exactly the plan for the TDS.
