http://hl7.org/fhir/fivews http://hl7.org/fhir/fivews.html [w5] FiveWs Pattern Mapping w5 -1 true true true http://hl7.org/fhir/workflow http://hl7.org/fhir/workflow-module.html Workflow Mapping Workflow Pattern workflow 0 true true true http://hl7.org/v2 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=185 v2 Mapping HL7 v2 Mapping v2 1 true http://loinc.org LOINC Code LOINC code for the element loinc 2 true http://snomed.org/attributebinding http://snomed.org/attributebinding SNOMED CT Attribute SNOMED CT Attribute Binding sct-attr

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
 3 true http://snomed.info/conceptdomain http://snomed.info/conceptdomain SNOMED CT Concept Domain SNOMED CT Concept Domain Binding sct-concept

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
 4 true http://hl7.org/v3/cda http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7 CDA Mapping CDA (R2) cda 5 true http://hl7.org/v3 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=186 RIM Mapping RIM Mapping rim 6 true true http://nema.org/dicom http://nema.org/dicom DICOM Mapping DICOM Tag Mapping dicom 7 true http://w3.org/vcard https://tools.ietf.org/html/rfc6350 vCard Mapping vCard Mapping vcard 8 true http://ihe.net/xds http://wiki.ihe.net/index.php/Category:DocShare XDS Mapping XDS metadata equivalent xds 9 true http://www.w3.org/ns/prov http://www.w3.org/ns/prov Prov Mapping W3C PROV w3c.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.

10 true http://ietf.org/rfc/2445 http://www.ietf.org/rfc/rfc2445.txt iCal Mapping iCalendar ical 11 true http://www.omg.org/spec/ServD/1.0/ http://www.omg.org/spec/ServD/1.0/ ServD Mapping ServD servd 12 true http://metadata-standards.org/11179/ http://metadata-standards.org/11179/ 11179 Mapping ISO 11179 iso11179

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.

13 true http://ihe.net/data-element-exchange http://wiki.ihe.net/index.php?title=Data_Element_Exchange IHE DEX mapping IHE Data Element Exchange (DEX) dex 14 true http://openehr.org http://openehr.org OpenEHR mapping Open EHR Archetype Mapping openehr 15 true http://siframework.org/ihe-sdc-profile http://wiki.siframework.org/IHE+SDC+Profile IHE SDC mapping IHE Structured Data Capture ihesdc 16 true http://siframework.org/cqf http://wiki.siframework.org/CQF QUICK mapping Quality Improvement and Clinical Knowledge (QUICK) quick 17 true http://www.cdisc.org/define-xml CDISC Define.xml 2.0 Mapping CDISC Define XML 2.0 metadata standard define.xml2.0 18 true http://www.cda-adc.ca/en/services/cdanet/ http://www.cda-adc.ca/en/services/cdanet/ CDAnet v4 Mapping Canadian Dental Association eclaims standard cdanetv4 20 true http://www.pharmacists.ca/ http://www.pharmacists.ca/ CPhA3 (Pharmacy) Mapping Canadian Pharmacy Associaiton eclaims standard cpha3pharm 21 true http://www.healthit.gov/quality-data-model http://www.healthit.gov/quality-data-model QDM Mapping Quality Data Model qdm 22 true http://hl7.org/orim ORIM Mapping Ontological RIM Mapping orim 23 true http://hl7.org/fhir/w5 http://hl7.org/fhir/fivews.html ...don't use... W5 Mapping w5 24 http://hl7.org/fhir/logical Logical Mapping Logical Mapping logical 25 true http://hl7.org/fhir/auditevent http://hl7.org/fhir/auditevent.html Auditevent Mapping FHIR AuditEvent Mapping fhirauditevent 26 true http://hl7.org/fhir/provenance http://hl7.org/fhir/provenance.html Provenance Mapping FHIR Provenance Mapping fhirprovenance 27 true http://hl7.org/qidam http://www.hl7.org/implement/standards/product_brief.cfm?product_id=378 QIDAM Mapping Mapping to Quality Improvement Domain Analysis Model qidam 28 true http://cap.org/ecc https://www.cap.org/laboratory-improvement/proficiency-testing/cap-ecc CAP Code Equivalent CAP Code cap 29 true http://fda.gov/UDI http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentification/default.htm UDI Mapping UDI Mapping 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.

30 true http://hl7.org/fhir/object-implementation Object Impl Object Implementation Information objimpl 31 http://github.com/MDMI/ReferentIndexContent http://github.com/MDMI/ReferentIndexContent MDMI Referent MDMI Referent Index Mapping mdmi 32 true http://ncpdp.org/SCRIPT10_6 http://www.ncpdp.org/NCPDP/media/pdf/NCPDPEprescribing101.pdf SCRIPT 10.6 Mapping Mapping to NCPDP SCRIPT 10.6 script10.6 33 true http://clinicaltrials.gov http://clinicaltrials.gov clinicaltrials.gov Mapping ClinicalTrials.gov Mapping clinicaltrials-gov 35 true http://hl7.org/fhir/rr R3-RR-Mapping R3-ReferalRequest Mapping rr-map 36 true http://www.hl7.org/v3/PORX_RM020070UV http://www.hl7.org/documentcenter/private/standards/v3/edition_web/domains/uvrx/uvrx_MedicationDispenseEvent.html#PORX_RM020070UV V3 Dispense Mapping V3 Pharmacy Dispense RMIM rx-dispense-rmim 37 true https://bridgmodel.nci.nih.gov https://bridgmodel.nci.nih.gov/download-model/bridg-releases/release-51/release-package BRIDG 5.1 Mapping BRIDG 5.1 Mapping BRIDG5.1 38 true http://hl7.org/fhir/composition http://hl7.org/fhir/composition.html Composition Mapping FHIR Composition fhircomposition 39 true http://hl7.org/fhir/documentreference http://hl7.org/fhir/documentreference.html DocumentReference Mapping FHIR DocumentReference fhirdocumentreference 40 true