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
MedicalProductOfHumanOrigin
BiologicallyDerivedProduct
id
meta
implicitRules
language
text
contained
extension
modifierExtension
productCategory
productCategory
MPHOCode
productCode
id
extension
coding
id
extension
system
version
code
display
userSelected
text
parent
request
identifier
id
extension
use
type
system
value
period
assigner
biologicalSourceEvent
id
extension
use
type
system
value
period
assigner
processingFacility
division
productStatus
expirationDate
collection
id
extension
modifierExtension
collector
sourcePatient
sourceOrganization
collected[x]
procedure
storageTempRequirements
property
id
extension
modifierExtension
type
value[x]
8.25.12.5 HL7 V2 Mapping (http://hl7.org/v2)
The mappings provided in this tab are indicative of how HL7 v2 fields relate to HL7 FHIR attributes in this resource, but is not complete and without critical HL7 v2 context. The HL7 v2-FHIR Implementation guide, located here , provides additional guidance on transforming an HL7 v2 message to FHIR resources for FHIR R4 and FHIR R6.
MedicalProductOfHumanOrigin
BiologicallyDerivedProduct
id
meta
implicitRules
language
text
contained
extension
modifierExtension
productCategory
productCategory
MPHOCode
productCode
id
extension
coding
C*E.1-8, C*E.10-22
id
extension
system
C*E.3
version
C*E.7
code
C*E.1
display
C*E.2 - but note this is not well followed
userSelected
Sometimes implied by being first
text
C*E.9. But note many systems use C*E.2 for this
parent
request
identifier
IAM-7
id
extension
use
N/A
type
CX.5
system
CX.4 / EI-2-4
value
CX.1 / EI.1
period
CX.7 + CX.8
assigner
CX.4 / (CX.4,CX.9,CX.10)
biologicalSourceEvent
id
extension
use
N/A
type
CX.5
system
CX.4 / EI-2-4
value
CX.1 / EI.1
period
CX.7 + CX.8
assigner
CX.4 / (CX.4,CX.9,CX.10)
processingFacility
division
productStatus
expirationDate
collection
id
extension
modifierExtension
collector
sourcePatient
sourceOrganization
collected[x]
procedure
storageTempRequirements
property
id
extension
modifierExtension
type
value[x]
8.25.12.6 RIM Mapping (http://hl7.org/v3)
MedicalProductOfHumanOrigin
BiologicallyDerivedProduct
Entity, Role, or Act,Material[classCode= Observation[classCode=OBS, moodCode=EVN]
id
meta
implicitRules
language
text
Act.text?
contained
N/A
extension
N/A
modifierExtension
N/A
productCategory
productCategory
MPHOCode
productCode
id
n/a
extension
n/a
coding
union(., ./translation)
id
n/a
extension
n/a
system
./codeSystem
version
./codeSystemVersion
code
./code
display
CV.displayName
userSelected
CD.codingRationale
text
./originalText[mediaType/code="text/plain"]/data
parent
request
identifier
id
id
n/a
extension
n/a
use
Role.code or implied by context
type
Role.code or implied by context
system
II.root or Role.id.root
value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period
Role.effectiveTime or implied by context
assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
biologicalSourceEvent
id
n/a
extension
n/a
use
Role.code or implied by context
type
Role.code or implied by context
system
II.root or Role.id.root
value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period
Role.effectiveTime or implied by context
assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
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 corresponding 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