FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

10.1.10 Resource Observation - Mappings

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

Mappings:

FiveWs Pattern Mapping

Workflow Pattern

HL7 V2 Mapping

SNOMED CT Attribute Binding

SNOMED CT Concept Domain Binding

RIM Mapping

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

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

Observation clinical.diagnostics
    identifier FiveWs.identifier
    status FiveWs.status
    category FiveWs.class
    code FiveWs.what[x]
    subject FiveWs.subject[x]
    focus FiveWs.subject[x]
    encounter FiveWs.context
    effective[x] FiveWs.done[x]
    issued FiveWs.recorded
    performer FiveWs.actor
        code FiveWs.what[x]

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

Observation Event
    identifier Event.identifier
    instantiates[x] Event.instantiatesCanonical
    basedOn Event.basedOn
    partOf Event.partOf
    status Event.status
    code Event.code
    subject Event.subject
    encounter Event.encounter
    effective[x] Event.occurrence[x]
    performer Event.performer.actor

10.1.10.3 HL7 V2 Mapping (http://hl7.org/v2 icon)

Observation OBX
    identifier OBX-21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 3) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
    instantiates[x]
    basedOn ORC
    triggeredBy ORC
        observation
        type
        reason
    partOf Varies by domain
    status OBX-11
    category
    code OBX-3
    subject PID-3
    focus OBX-3
    encounter PV1
    effective[x] OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
    issued OBR-22 (or MSH-7), or perhaps OBX-19 (depends on who observation made)
    performer OBX-15 / (Practitioner) OBX-16, PRT-5:PRT-4='RO' / (Device) OBX-18 , PRT-10:PRT-4='EQUIP' / (Organization) OBX-23, PRT-8:PRT-4='PO'
    value[x] OBX-2, OBX-5, OBX-6
    dataAbsentReason N/A
    interpretation OBX-8
    note NTE-3 (partner NTE to OBX, or sometimes another (child?) OBX)
    bodySite OBX-20
    bodyStructure
    method OBX-17
    specimen SPM segment
    device OBX-17 / PRT -10
    referenceRange OBX-7
        low OBX-7
        high OBX-7
        normalValue OBX-7
        type OBX-10
        appliesTo OBX-10
        age
        text OBX-7
    hasMember Relationships established by OBX-4 usage
    derivedFrom Relationships established by OBX-4 usage
    component containment by OBX-4?
        code OBX-3
        value[x] OBX-2, OBX-5, OBX-6
        dataAbsentReason N/A
        interpretation OBX-8
        referenceRange OBX-7

10.1.10.4 SNOMED CT Attribute Binding (http://snomed.org/attributebinding icon)

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
Observation
    identifier
    instantiates[x]
    basedOn
    triggeredBy
        observation
        type
        reason
    partOf
    status
    category
    code 116680003 |Is a|
    subject
    focus
    encounter
    effective[x]
    issued
    performer
    value[x] 363714003 |Interprets|
    dataAbsentReason
    interpretation 363713009 |Has interpretation|
    note
    bodySite 718497002 |Inherent location|
    bodyStructure
    method
    specimen 704319004 |Inherent in|
    device 424226004 |Using device|
    referenceRange
        low
        high
        normalValue
        type
        appliesTo
        age
        text
    hasMember
    derivedFrom
    component
        code
        value[x] 363714003 |Interprets|
        dataAbsentReason
        interpretation 363713009 |Has interpretation|
        referenceRange

10.1.10.5 SNOMED CT Concept Domain Binding (http://snomed.info/conceptdomain icon)

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
Observation < 363787002 |Observable entity|
    identifier
    instantiates[x]
    basedOn
    triggeredBy
        observation
        type
        reason
    partOf
    status < 445584004 |Report by finality status|
    category
    code < 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
    subject
    focus
    encounter
    effective[x]
    issued
    performer
    value[x] < 441742003 |Evaluation finding|
    dataAbsentReason
    interpretation < 260245000 |Findings values|
    note
    bodySite < 123037004 |Body structure|
    bodyStructure
    method
    specimen < 123038009 |Specimen|
    device < 49062001 |Device|
    referenceRange
        low
        high
        normalValue
        type < 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
        appliesTo < 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
        age
        text
    hasMember
    derivedFrom
    component
        code < 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
        value[x] 363714003 |Interprets| < 441742003 |Evaluation finding|
        dataAbsentReason
        interpretation < 260245000 |Findings values|
        referenceRange

10.1.10.6 RIM Mapping (http://hl7.org/v3 icon)

Observation Observation[classCode=OBS, moodCode=EVN]
    identifier id
    instantiates[x] .outboundRelationship[typeCode=DEFN].target
    basedOn .inboundRelationship[typeCode=COMP].source[moodCode=EVN]
    triggeredBy .inboundRelationship[typeCode=COMP].source[moodCode=EVN]
        observation outBoundRelationship
        type code
        reason annotation
    partOf .outboundRelationship[typeCode=FLFS].target
    status status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
    category .outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
    code code
    subject participation[typeCode=RTGT]
    focus participation[typeCode=SBJ]
    encounter inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
    effective[x] effectiveTime
    issued participation[typeCode=AUT].time
    performer participation[typeCode=PRF]
    value[x] value
    dataAbsentReason value.nullFlavor
    interpretation interpretationCode
    note subjectOf.observationEvent[code="annotation"].value
    bodySite targetSiteCode
    bodyStructure targetSiteCode
    method methodCode
    specimen participation[typeCode=SPC].specimen
    device participation[typeCode=DEV]
    referenceRange outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]
        low value:IVL_PQ.low
        high value:IVL_PQ.high
        normalValue value:IVL_PQ.normal
        type interpretationCode
        appliesTo interpretationCode
        age outboundRelationship[typeCode=PRCN].targetObservationCriterion[code="age"].value
        text value:ST
    hasMember outBoundRelationship
    derivedFrom .targetObservation
    component outBoundRelationship[typeCode=COMP]
        code code
        value[x] value
        dataAbsentReason value.nullFlavor
        interpretation interpretationCode
        referenceRange outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]