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 1.2 Health Services\Vendor Systems HL7 V2 Messaging Health Services\Vendor Systems 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 1.3 Health Services\Vendor Systems CDA R2 Messaging Health Services\Vendor Systems 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 1.4 Health Services\Vendor Systems CDA R2 Health Services\Vendor Systems 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’ Translation layer using standardised XML transforms Highly abstract schema

The Process (1) 1.5 openEHR Standarised Knowledge Environment Client Data Client Schema Validates Client System Archetypes Templates Implementation Standardised XML Environment Template Data Schema Generate from Tools Template Data Document Validates

1.6 CDA (CCD) CDA (CCD) CDA R2 Validates openEHR CEN CEN Archetype based standard XSL Transform Template Data Document Standard Transform for CCD openEHR Display The Process (2)

1.7 Software Demonstration