1 / 7

Automating the production of CDA R2 artefacts using openEHR Archetypes and Templates.

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

chen
Download Presentation

Automating the production of CDA R2 artefacts using openEHR Archetypes and Templates.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automating the production of CDA R2 artefacts using openEHR Archetypes and Templates. Making Health Compute December 5th, 2007

  2. 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

  3. 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

  4. 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’

  5. 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

  6. 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

  7. Software Demonstration

More Related