CDA2FHIR

Short Description

The purpose of this track is to test the conversion of the Austrian HL7 CDA Laboratory Report (Version 3.0) to FHIR by using the CDA Logical Model and the current status of the CDA2FHIR maps.

Long Description

The architecture of the Austrian EHR system (ELGA) is mainly based on HL7 CDA leveraging the IHE XDS framework. Recent national and international projects (e.g. myHealth@EU) are evaluating the use of HL7 FHIR as parallel or even as replacing architecture. As the existing CDA documents would have to be accessible in an HL7 FHIR environment as well a mapping to HL7 FHIR is required.

For this purpose, the international CDA Logical Model has been enhanced by the elements required by the Austrian CDA XML Schema. Furthermore, HL7 FHIR maps have been created in order to be used for mapping from HL7 CDA to HL7 FHIR.

We expect and hope to achieve:

  • increased understandability of maps (StructureMap)
  • increased understandability of the differences between HL7 CDA and HL7 FHIR
  • feedback regarding the current status of the maps

Type

Test the design of a Resource/set of Resources

Submitting Work Group/
Project/
Accelerator/
Affiliate/
Implementer Group  

TC FHIR - AG ELGA CDA Laborbefund zu FHIR

Track Lead(s)

Gabriel Kleinoscheg

Track Lead Email(s)

tc-fhir@hl7.at

Related Tracks

FHIR Version

FHIR R4

Specification(s) this track uses

https://github.com/HL7Austria/CDA-core-2.0/tree/cda-ext-elga (Austrian CDA Logical Model)

https://github.com/HL7Austria/CDA2FHIR (Austrian CDA2FHIR maps)

https://hl7.org/fhir/R4/structuremap.html (StructureMap)

https://build.fhir.org/mapping-language.html (Mapping Language)

Artifacts of focus

-

Expected participants

Gabriel Kleinoscheg Nikola Tanjga 

Date / Time

Monday March 13, 09:00am-03:30pm CET

Test Servers

See Test Servers

Track Details

Prerequisites (recommended)
System roles
FHIR Transformation Server (Matchbox)

For service providers, implement the following operations:

Support additional capabilities:

CDA2FHIR Transformer

Implement any one or more of:

  • Set up the transformation framework locally
  • Transform a HL7 CDA Laboratory Report (Version 3) to HL7 FHIR
  • Inspect/Edit the mapping
  • Validate the created Patient resource against the Austrian Patient profile (see Patient track)

At least one server supports all of these operations and capabilities (http://test.fhir.org/r4/). Other servers (see the list above) will support several of these operations and capabilities.

Discussion
Scenarios
1 - Setting up the transformation framework

Follow the instructions in the README of CDA2FHIR for setting up the transformation framework. Once set up proceed with the next scenario.

2 - Transformation of HL7 CDA Laboratory Report

Using the examples of HL7 CDA Laboratory Reports in GitLab test the transformation to HL7 FHIR.

You can use your local transformation environment or use the provided Matchbox server (see Test Servers).

3 - Inspect/Edit the mapping
  • Try to inspect/edit the mapping
  • POST the updated mapping to your local transformation environment 
  • Transform a HL7 CDA Laboratory Report
4 -  Validate the created Patient resource

Take the created Patient resource and validate it against the Austrian Patient profile - for detailed instructions see the description of the HL7 AT FHIR Core IG Track 2023 Track.