This wiki has undergone a migration to Confluence found Here
FHIR Mappings
Revision as of 02:19, 29 March 2014 by StephenChu (talk | contribs) (Created page with " Return to Patient Care <br> Return to FHIR Patient Care Resources <br> One of the objectives of FHIR is provide mapping from FHIR resources to corresponding/equivale...")
Return to Patient Care
Return to FHIR Patient Care Resources
One of the objectives of FHIR is provide mapping from FHIR resources to corresponding/equivalent HL7 v2.x message segments and v3 classes.
This page is intended to provide useful information on the mapping principles and mapping examples to help PCWG members better understand relevant mappings.
Categories of Mapping
FHIR team has identified 4 categories of mapping detail:
- - skeletel: the mappings give you the overall backbone, but don't fill out the details
- - notional: the mappings identify the elements that are equivalent in their definitions and meaning
- - definitional: the mappings link between primitive data types in both specifications and all primitives are mapped
- - executional: the mappings handle the entire value domain, and use a formal language, and an engine can use them to interconvert data
- Most of the existing FHIR mappings for v2 and CDA are notional mappings.
Mapping Examples
- Patient Resource Mapping (to HL7 v2.x):
- Diagnostic Order Mapping:
- C-CDA to FHIR Mapping: