201605 Declarative Mapping
This track will explore mappings and/or a useful subset of mapping tasks to support interoperability. The emphasis will be on declarative languages, though procedural approaches may be used too.
- Pre-requisites: none
Start: 1pm Saturday
Submitting WG/Project/Implementer Group
- SOA Working Group
- CGIT (approval planned)
- CBCC (approvalplanned)
There is a recognized need for mappings to facilitate interoperability across HL7 products, and between HL7 products and other formats and data models. Following on the Birds of a Feather CDA-to-FHIR session in Orlando, there was an agreement among the participants to pursue mapping approaches -- especially those that can be expressed declaratively, though procedural mapping expressions are not excluded and may be helpful in some cases. Objectives of the track include reuseable computable artifacts that can be saved / persisted as FHIR resources from the approaches presented in the Connectathon. SOA WG has already developed "cross-paradigm" mapping guidance intended to represent the same business content in more than on structure (e.g. CDA template to FHIR profile or V2 profile components)
Proposed Track Lead
The expected participants include:
- Keith Dudley / Grahame Grieve
- MDMI Open Source Project (several participants)
- David Booth (Yosemite Project)
- SAMHSA BHITS Project
- Members of the i2b2 on FHIR team
- David Hay (Orion Health)
This is a software product that helps a user manager a set of mapping resources, and edit them, and test the mapping transform outcome interactively. Designer may offer additional assistance in Ux for mapping etc as desired. Designers implement use case #1.
This will be an application that takes a set of map files or resources, a CDA document and produces a FHIR Bundle Document. The executor may be wrapped in any form desired.
TODO: David Booth and Ken Lord to add more use case scenarios, with before and after documents.
1. Edit an existing map
The designer opens and edits the existing CDA mappings either from the map files (using the concrete syntax), or from the equivalent resources.
The map resources produced can feed into the second use case
Bonus points for being able to read and write resources from a server.
2. Execute a map
Take the CCDA draft maps, apply them to a CCDA example document, and produce a document bundle
- The test map is the one in the CCDA implementation (\maps)
- the test document is the CCDA example document distributed with the CCDA R2 (see [here]).
The output should be a Bundle that looks like [this - to be resolved closer to the day]
A future step will test the execution packaged in an operation on a FHIR Server.