Automating the production of CDA R2 artefacts using

openEHR Archetypes and Templates.

Making Health

Compute

December 5th, 2007

Challenges for Implementing CDA R2 messaging

1.2

Health Services\Vendor System

s

HL7 V2 Messaging

Hea

lth S

ervi

ces\

Vend

or S

yste

ms

• 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 System

s

CDA R2 Messaging

Hea

lth S

ervi

ces\

Vend

or S

yste

ms

• 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 System

s

CDA R2

Hea

lth S

ervi

ces\

Vend

or S

yste

ms

• 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

Translation layer using

standardised XML

transforms

Highlyabstract 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

DocumentValidates

1.6

CDA(CCD) CDA R2ValidatesopenEHR CEN

13606

Archetype based standard XSL Transform

Template Data

Document

Standard Transform for CCD

openEHR Display

The Process (2)

1.7Software Demonstration