Release 4B Snapshot #1

This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

10.2.8 Resource Media - Mappings

Orders and Observations Work GroupMaturity Level: N/AStandards Status: InformativeSecurity Category: Patient Compartments: Device, Encounter, Patient, Practitioner

Mappings:

FiveWs Pattern Mapping

Workflow Pattern

HL7 v2 Mapping

SNOMED CT Attribute Binding

SNOMED CT Concept Domain Binding

RIM Mapping

DICOM Tag Mapping

Mappings for the media resource (see Mappings to Other Standards for further information & status).

10.2.8.1 FiveWs Pattern Mapping (http://hl7.org/fhir/fivews )

Media
    identifierFiveWs.identifier
    statusFiveWs.status
    typeFiveWs.class
    modalityFiveWs.what[x]
    subjectFiveWs.subject[x]
    encounterFiveWs.context
    created[x]FiveWs.done[x]
    issuedFiveWs.recorded
    operatorFiveWs.actor
    reasonCodeFiveWs.why[x]

10.2.8.2 Workflow Pattern (http://hl7.org/fhir/workflow )

MediaEvent
    identifierEvent.identifier
    basedOnEvent.basedOn
    partOfEvent.partOf
    statusEvent.status
    modalityEvent.code
    subjectEvent.subject
    encounterEvent.encounter
    created[x]Event.occurrence[x]
    operatorEvent.performer.actor
    reasonCodeEvent.reasonCode
    noteEvent.note

10.2.8.3 HL7 v2 Mapping (http://hl7.org/v2 )

Media
    identifier
    basedOn
    partOf
    statusVaries by domain
    type
    modality
    view
    subject
    encounter
    created[x]
    issuedOBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)
    operator
    reasonCode
    bodySite
    deviceName
    device
    height
    width
    frames
    duration
    content
    noteNTE

10.2.8.4 SNOMED CT Attribute Binding (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
Media
    identifier
    basedOn
    partOf
    status
    type
    modality
    view
    subject
    encounter
    created[x]
    issued
    operator
    reasonCode
    bodySite718497002 |Inherent location|
    deviceName
    device424226004 |Using device|
    height
    width
    frames
    duration
    content
    note

10.2.8.5 SNOMED CT Concept Domain Binding (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
Media
    identifier
    basedOn
    partOf
    status
    type
    modality
    view
    subject
    encounter
    created[x]
    issued
    operator
    reasonCode
    bodySite< 123037004 |Body structure|
    deviceName
    device< 49062001 |Device|
    height
    width
    frames
    duration
    content
    note

10.2.8.6 RIM Mapping (http://hl7.org/v3 )

MediaAct[classCode="DGIMG", moodCode="EVN"]
    identifier.id
    basedOn.outboundRelationship[typeCode=FLFS].target
    partOf.inboundRelationship[typeCode=COMP].source[moodCode=EVN]
    status.status
    type.code
    modality.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
    viewDiagnosticImage.subjectOrientationCode
    subject.participation[typeCode="SUBJ"]???
    encounter.inboundRelationship(typeCode=COMP].source[classCode<=PCPR, moodCode=EVN]
    created[x].effectiveTime
    issuedparticipation[typeCode=AUT].time
    operator.participation[typeCode="PERF"]???
    reasonCode.reasonCode
    bodySitetargetSiteCode
    deviceName.participation[typeCode="DEV"].role.player.Entity[classCode="DEV"].name
    deviceparticipation[typeCode=DEV]
    height.outboundRelationship[typeCode="COMP].target[classCode="OBS", moodCode="EVN",code="<CODE>"].value
    width.outboundRelationship[typeCode="COMP].target[classCode="OBS", moodCode="EVN",code="<CODE>"].value
    frames.outboundRelationship[typeCode="COMP].target[classCode="OBS", moodCode="EVN",code="<CODE>"].value
    duration.outboundRelationship[typeCode="COMP].target[classCode="OBS", moodCode="EVN",code="<CODE>"].value
    content.text
    note.inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST]

10.2.8.7 DICOM Tag Mapping (http://nema.org/dicom )

Media
    identifier0008,0018 | ~0008,0050 | 0020,000D | 0020,000E
    basedOn
    partOf
    status
    type
    modality0008,0060 | 0008,1032
    view
    subject~0010,0020
    encounter
    created[x]
    issued
    operator0008,1060?
    reasonCode
    bodySite
    deviceName0008,0070
    device
    height0028,0010
    width0028,0011
    frames
    duration~0028,0002
    content
    note