Congratulations on this excellent initiative. Please keep the list informed on progress in this area. It is most important.
Yours sincerely Wilton Braund Dr Wilton Braund Endocrinologist 19 Alexander Ave ASHFORD 5035 0411 555 723 ________________________________ From: openehr-clinical-bounces at openehr.org [mailto:[email protected]] On Behalf Of Hugh Leslie Sent: Tuesday, 3 June 2008 9:21 AM To: For openEHR clinical discussions Subject: Re: openEHR solution for DSS in epidemiology[Scanned] Hi Marivan Welcome to the list as well. We have also been doing some work in Australia with HL7 CDA and openEHR. The problem that we have been trying to solve here is how to produce CDA that is consistent without relying on multiple vendors having to re-engineer their systems to produce CDA. You will know that in the HL7 v2 world, certainly in Australia, that this approach has led to every system producing HL7v2 messages that are slightly different. Pathology companies here have to produce at least 35 different versions of the same HL7v2 message to suit all the different vendors that need these messages. This is despite them all being consistent with the Standards Australia version. We have serious concerns that the same issue may occur here with CDA R2 as vendors try to implement this highly abstract and complex specification. This will mean that interoperability will still rely on prenegotiation of messages and costly integration. We have solved this issue by using an approach that uses openEHR archetypes and templates to define the semantics of some vendor system data. We can then programatically produce a an XML schema that is based on the vendors data as represented by the archetypes and templates. This is called a Template Data Schema (TDS) and from the vendor data,using a single transform, a Template Data Document (TDD) can be produced that conforms to the Schema. Once we have the TDD, it can be transformed to either openEHR data or to CDA R2. The CDA transforms are built using a library of transforms based on archetypes. This means that if the TDD has been built using an archetype that has a transform in the library, we can build that part of the CDA using that transform. Once the library of archetype based transforms is complete, then any TDD can be converted reliably to and from CDA. This is not just an academic idea - if you are interested, I can demonstrate this process in action. One of the very nice things about this process, is that vendors need only XML expertise to make it work - they don't need to be experts in either openEHR or CDA. The format of the TDS will become part of the openEHR specification very soon. regards Hugh _______________________________________________ Dr Hugh Leslie Clinical Director Ocean Informatics Pty Ltd M: +61 404 033 767 E: hugh.leslie at oceaninformatics.com W: www.oceaninformatics.com Marivan Santiago Abrah?o wrote: Dear Folks, Dr. Cavalini's argument opens up a main concern about interoperability and standards. As Chair of HL7 Brazil, we are carrying out a discussion about the harmonization of HL7 CDA and archetypes, as on some instances there are reciprocal and complemental procedures on the specification of an EHR. In Brazil, we are developing some initiatives using HL7 v. 3 with CDA, and I am, myself, involved on a development of EHR system using archetypes, with portuguese translation, and I could figure out that archetypes may fulfill some lacks on clinical issues on HL7 and HL7 may solve some inconsistencies with interoperability on administrative issues using archetypes. Even being novice on archetypes, I am very enthusiastic with its wide open view on managing healthcare information and I look forward deep participating on the openEHR Project. The suggestion to establish a study group to work with decision support systems will provide the necessary basic grounds to strengthen the rationale on any medical system, including epidemiological surveillance. Regards, Dr. Marivan Santiago Abrah?o CHAIR HL7 Brazil e-mail : marivan at abrahao.net website: www.hl7brasil.org.br -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20080604/e0a87057/attachment.html>
