Difference between revisions of "201605 Declarative Mapping"
(→Roles) |
|||
| Line 33: | Line 33: | ||
==Roles== | ==Roles== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | === | + | === Map Designer === |
| − | + | ||
| − | FHIR Server | + | 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. |
| + | |||
| + | The designer could just edit the mappings as a set of .map files using the concrete syntax. Bonus points for being able to read and write resources from files or a server. | ||
| + | |||
| + | Map Designer must be able to read and edit the CDA mapping files. | ||
| + | |||
| + | === Map Executor === | ||
| + | |||
| + | This will be an application that takes a set of map files or resources, a CDA document and produces a FHIR Bundle Document. The test map is the one in the CCDA implementation (\maps), and the test document is the CCDA example document distributed with the CCDA R2 (see [[http://www.healthintersections.com.au/ccd.xml here]]). The output should be a Bundle that looks like [this - to be resolved closer to the day] | ||
| + | |||
| + | The executor may be wrapped in any form desired. A future step will test the execution packaged in an operation on a FHIR Server. | ||
==Scenarios== | ==Scenarios== | ||
Revision as of 07:15, 9 March 2016
Declarative Mapping
This track will explore mappings and/or a useful subset of mapping tasks using declarative languages used to address interoperability issues.
- Pre-requisites: none
Submitting WG/Project/Implementer Group
- SOA Working Group
- CGIT (approval planned)
- CCBC (approvalplanned)
Justification
There is a recognized need for mappings to facilitate interoperability across HL7 products Following on the Birds of a Feather CDA to FHIR session in Orlando, there was an agreement among the participants to pursue declarative approaches or mappings. 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
- Coordinator: Ken Lord (MDIX)
- Track Lead: TBD
Expected participants
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
Roles
Map Designer
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.
The designer could just edit the mappings as a set of .map files using the concrete syntax. Bonus points for being able to read and write resources from files or a server.
Map Designer must be able to read and edit the CDA mapping files.
Map Executor
This will be an application that takes a set of map files or resources, a CDA document and produces a FHIR Bundle Document. The test map is the one in the CCDA implementation (\maps), and 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]
The executor may be wrapped in any form desired. A future step will test the execution packaged in an operation on a FHIR Server.
Scenarios
Desclarative Mapping Use Cases:
[To do: create scenarios based on the planned scops for May and expected resources]
1. Create a new map
Precondition: ...
Action:
...
Success Criteria:
...
2. Publish a map
Precondition:
Action:
Success Criteria:
Bonus Point:
3. Execute a map
Precondition:
Action:
Success Criteria:
Bonus Point:
