Release 4

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: Mapping Formal URL:
Workflow Pattern Formal URL:
CDISC Define XML 2.0 metadata standard Formal URL:
Mapping to NCPDP SCRIPT 10.6 Formal URL:
FiveWs Pattern Mapping Formal URL:
BRIDG 5.1 Mapping Formal URL:
FHIR Composition Formal URL:
IHE Structured Data Capture Formal URL:
Canadian Dental Association eclaims standard Formal URL:
SNOMED CT Concept Domain Binding Formal URL:

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:
HL7 v2 Mapping Formal URL:
RIM Mapping Formal URL:
ISO 11179 Formal URL:

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:
DICOM Tag Mapping Formal URL:
MDMI Referent Index Mapping Formal URL:
V3 Pharmacy Dispense RMIM Formal URL:
XDS metadata equivalent Formal URL:
Equivalent CAP Code Formal URL:
CDA (R2) Formal URL:
Quality Improvement and Clinical Knowledge (QUICK) Formal URL:
FHIR DocumentReference Formal URL:
Canadian Pharmacy Associaiton eclaims standard Formal URL:
UDI Mapping Formal URL:

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:
FHIR AuditEvent Mapping Formal URL:
IHE Data Element Exchange (DEX) Formal URL:
SNOMED CT Attribute Binding Formal URL:

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:

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:
LOINC code for the element Formal URL:
vCard Mapping Formal URL:
Open EHR Archetype Mapping Formal URL:
ServD Formal URL:
FHIR Provenance Mapping Formal URL:
iCalendar Formal URL: