Current Build
FHIR Infrastructure Work GroupMaturity Level: n/aStandards Status: Informative

For many of the resources and other content defined in this specification, mappings are provided to other standards. These mappings are informative and are provided to help implementers of this specification understand the content and use it correctly.

Due to wide variation in the implementation of standards in healthcare, none of the mappings are authoritative or normative, and implementers always have to check local usage before using these mappings in production.

This table summarizes the mappings that may be provided through the specification:

Name Details
Logical Mapping Formal URL: http://hl7.org/fhir/logical
ClinicalTrials.gov Mapping Formal URL: http://clinicaltrials.gov
Workflow Pattern Formal URL: http://hl7.org/fhir/workflow
CDISC Define XML 2.0 metadata standard Formal URL: http://www.cdisc.org/define-xml
Mapping to NCPDP SCRIPT 10.6 Formal URL: http://ncpdp.org/SCRIPT10_6
FiveWs Pattern Mapping Formal URL: http://hl7.org/fhir/fivews
BRIDG 5.1 Mapping Formal URL: https://bridgmodel.nci.nih.gov
FHIR Composition Formal URL: http://hl7.org/fhir/composition
IHE Structured Data Capture Formal URL: http://siframework.org/ihe-sdc-profile
Canadian Dental Association eclaims standard Formal URL: http://www.cda-adc.ca/en/services/cdanet/
SNOMED CT Concept Domain Binding Formal URL: http://snomed.info/conceptdomain

Concept domain bindings link a resource or an element to a set of SNOMED CT concepts that represent the intended semantics of the instances (whether or not SNOMED CT is used to encode that data element). This set of concepts is represented using a SNOMED CT expression constraint. Note that the 'Concept domain binding' may be a superset of the 'value set binding'. These bindings help to support:

  • Quality checking FHIR resources by ensuring that (a) the intended semantics of the instances matches the valid range of the corresponding SNOMED CT attribute, and (b) the intended value set is appropriate for the intended semantics of the instances
  • Semantic checking of data instances by helping to detect potential inconsistencies caused by overlap between the semantics incorporated in two concept domains
R3-ReferalRequest Mapping Formal URL: http://hl7.org/fhir/rr
HL7 v2 Mapping Formal URL: http://hl7.org/v2
RIM Mapping Formal URL: http://hl7.org/v3
ISO 11179 Formal URL: http://metadata-standards.org/11179/

These mappings are included to indicate where properties of the data elements defined by the FHIR specification relate to similar fields in the ISO 11179 specification.

Mapping to Quality Improvement Domain Analysis Model Formal URL: http://hl7.org/qidam
DICOM Tag Mapping Formal URL: http://nema.org/dicom
MDMI Referent Index Mapping Formal URL: http://github.com/MDMI/ReferentIndexContent
V3 Pharmacy Dispense RMIM Formal URL: http://www.hl7.org/v3/PORX_RM020070UV
XDS metadata equivalent Formal URL: http://ihe.net/xds
Equivalent CAP Code Formal URL: http://cap.org/ecc
CDA (R2) Formal URL: http://hl7.org/v3/cda
Quality Improvement and Clinical Knowledge (QUICK) Formal URL: http://siframework.org/cqf
FHIR DocumentReference Formal URL: http://hl7.org/fhir/documentreference
Canadian Pharmacy Associaiton eclaims standard Formal URL: http://www.pharmacists.ca/
UDI Mapping Formal URL: http://fda.gov/UDI

UDI is a unique numeric or alphanumeric code that consists of two parts: (1) a device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device, and (2) a production identifier (PI), a conditional, variable portion of a UDI that identifies one or more of the following when included on the label of a device: (2a) the lot or batch number within which a device was manufactured; (2b) the serial number of a specific device; (2c) the expiration date of a specific device; (2d) the date a specific device was manufactured; (2e) the distinct identification code required by §1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device.

Quality Data Model Formal URL: http://www.healthit.gov/quality-data-model
FHIR AuditEvent Mapping Formal URL: http://hl7.org/fhir/auditevent
IHE Data Element Exchange (DEX) Formal URL: http://ihe.net/data-element-exchange
SNOMED CT Attribute Binding Formal URL: http://snomed.org/attributebinding

Attribute bindings link coded data elements in FHIR resources to a corresponding attribute in the SNOMED CT concept model. These bindings help to support:

  • clarifying the intended meaning of the data element
  • Quality checking the alignment between FHIR resource design and any coresponding SNOMED CT concept model
  • Composition and decomposition of data instances by indicating the SNOMED CT concept model attribute whose value may be used to decompose a precoordinated concept into this data element
W3C PROV Formal URL: http://www.w3.org/ns/prov

The provenance resource is based on known practices in the HL7 implementation space, particularly those found in the v2 EVN segment, the v3 ControlAct Wrapper, the CDA header, and IHE ATNA. The conceptual model underlying the design is the W3C provenance Specification . Though the content and format of the resource is designed to meet specific requirements for FHIR, all the parts of the resource are formally mapped to the PROV-O specification, and FHIR resources can be transformed to their W3C PROV equivalent.

Ontological RIM Mapping Formal URL: http://hl7.org/orim
LOINC code for the element Formal URL: http://loinc.org
vCard Mapping Formal URL: http://w3.org/vcard
Open EHR Archetype Mapping Formal URL: http://openehr.org
ServD Formal URL: http://www.omg.org/spec/ServD/1.0/
FHIR Provenance Mapping Formal URL: http://hl7.org/fhir/provenance
iCalendar Formal URL: http://ietf.org/rfc/2445