Dear All: thank you all for your reply to my question! Sorry I was out last week.
Dear Health, Thank you for taking the time to explain your process getting the HL7 v2/v3 to archtypes & templates! Would it possible for you to share your XSLT with us? Even better if you can share one or two instances of HL7 messages so that I can follow your instruction steps from your slides to see how the entire process works. BTW: if anyone knows of any public available test dataset on HL7 v2, v3, 13606, X12, etc. I'd very much appreciated for their URLs. Much thanks in advanced for your help! --Wo From: openehr-technical-bounces at openehr.org [mailto:[email protected]] On Behalf Of Heath Frankel Sent: Monday, February 06, 2012 5:35 AM To: 'For openEHR technical discussions' Subject: RE: Building software to convert HL7 v2/v3 messaging into archetypes & templates Hi Wo, Not sure if anyone else has some tools for the Job, but my experience in doing this over the last 5 years is that there is no silver bullet for this task. The process is just like any integration mapping, however the commercial mapping tools that I have attempted to use and those I have attempted to build myself just don't give me the capability needed for the mapping complexity I require. One of the ley issues is support for abstract types. I would be very happy to know if others have found a better tool than those I have tried I write XSLT by hand to transform the input message (HL7 V2 needs to be converted to XML using an integration component such as Mirth) into a Template Data Document (TDD) as defined in my presentation. The TDD is validated against the Template Data Schema (TDS) generated from a Template defined in the Ocean Template Designer, which augments the document with fixed and default values in the schema. The validated TDD is then transformed using a TDD to openEHR composition transform that can be used for any template exported using the Ocean Template Designer. These transforms are applied within an integration service which also provides communication ports and message tracing. You could certainly skip the intermediate TDD step but we have found that using it provides a more concrete (domain) model of the message that you are transforming to and allows the use of standard XML schema validation tools to catch 95% of the structural errors without the need for specialised openEHR validation tools. Although as openEHR experts we benefit from this process, the advantages for those that are not is huge. The nice thing about using archetypes to define the schema of the target of a transform is that you only need to write the transform template per archetype once. Each message that uses the same input structure corresponding to this archetype can reuse the same transform. Unfortunately, the real world of integration is not so simple and different source systems, even different messages from the same source system may be different, but you still have a good starting point to tweak the transform to support the variation between implementations. I hope this helps. Regards Heath From: openehr-technical-bounces at openehr.org<mailto:openehr-technical-bounces at openehr.org> [mailto:openehr-technical-bounces at openehr.org]<mailto:[mailto:[email protected]]> On Behalf Of Chang, Wo L. Sent: Saturday, 4 February 2012 8:07 AM To: openehr-technical at openehr.org<mailto:openehr-technical at openehr.org> Subject: Building software to convert HL7 v2/v3 messaging into archetypes & templates Dear All, I hope this is the right reflector.... First of all, thanks to those who developed tools, prepared tutorials, etc.!! I have spending the last few days playing around with the followings: * Java Reference Implementation of openEHR * LiU-Archtype-Editor-0.5.2 * Archtype Editor 2.2.779 * ADL 1.5 Workbench beta * Template Designer 2.6.1213.3 * Etc. Along with reading very good tutorials on: * Intro to openEHR, Sam Heard * Knowledge-enabled approach to eHealth records, Heather Leslie * Using Archtypes with HL7 Messages and Clinical Documents, Health Frankel * EN 13606-2 Gello - DCM, Andrew McIntyre * Etc. And openEHR stable specifications on: * Introducing openEHR * Architecture Overview * Etc. And ISO 13606 Part-1 and Part-2. I truly believe the archtype/template would be the right approach for my project on long-term management and preservation of EHRs. The Java ref. implementation libraries, Archtype Editor, Template Designer are great utils/tools. My basic question is: are there any public tools available to allow me to covert HL7 v2/v3 messaging to/from archtypes/templates as described in Health Frankel's tutorial on "Using Archtypes with HL7 Messages and Clinical Documents"? I know there is deep learning curve and would very much appreciated for any pointers. Thanks in advance for any help! --Wo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120213/40335d9c/attachment.html>
