70 likes | 203 Views
Automating the production of CDA R2 artefacts using openEHR Archetypes and Templates. Making Health Compute. December 5 th , 2007 . Challenges for Implementing CDA R2 messaging. Health ServicesVendor Systems. Health ServicesVendor Systems. HL7 V2 Messaging. Well understood
E N D
Automating the production of CDA R2 artefacts using openEHR Archetypes and Templates. Making Health Compute December 5th, 2007
Challenges for Implementing CDA R2 messaging Health Services\Vendor Systems Health Services\Vendor Systems HL7 V2 Messaging • Well understood • Lots of expertise • Many tools for V2 integration • Many systems natively support V2 messaging at some level
Challenges for Implementing CDA R2 messaging Health Services\Vendor Systems Health Services\Vendor Systems CDA R2 Messaging • Less well known/understood • Highly abstract schema – complex to express semantics • Little expertise • Few tools • Expensive to re-engineer systems to natively support CDA
A practical first step Highly abstract schema Health Services\Vendor Systems Translation layer using standardised XML transforms Translation layer using standardised XML transforms Health Services\Vendor Systems CDA R2 • XML is well understood • XML expertise is common • XML Tools are widely available • Able to be automated • CDA messages conform to an agreed standardised schema and reduce the need for ‘pre-negotiation’
The Process (1) Client System Client Data Client Schema openEHRStandarised Knowledge Environment Validates Archetypes Templates Generate from Tools Implementation Standardised XML Environment Template Data Schema Template Data Document Validates
The Process (2) Template Data Document Archetype based standard XSL Transform openEHR CEN 13606 CDA (CCD) CDA R2 Validates Standard Transform for CCD openEHR Display