STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

10.1.8 Resource Observation - Mappings

Mappings:

RIM Mapping

HL7 v2 Mapping

Mappings for the observation resource.

10.1.8.1 Mappings for RIM Mapping (http://hl7.org/v3)

ObservationObservation[classCode=OBS, moodCode=EVN]
    identifierid
    statusstatus 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
    codecode
    subjectparticipation[typeCode=SBJ]
    encounterinboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
    effective[x]effectiveTime
    issuedparticipation[typeCode=AUT].time
    performerparticipation[typeCode=PRF]
    value[x]value
    dataAbsentReasonvalue.nullFlavor
    interpretationinterpretationCode
    commentsubjectOf.observationEvent[code="annotation"].value
    bodySitetargetSiteCode
    methodmethodCode
    specimenparticipation[typeCode=SPC].specimen
    deviceparticipation[typeCode=DEV]
    referenceRangeoutboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]
        lowvalue:IVL_PQ.low
        highvalue:IVL_PQ.high
        meaninginterpretationCode
        ageoutboundRelationship[typeCode=PRCN].targetObservationCriterion[code="age"].value
        textvalue:ST
    relatedoutBoundRelationship
        type.typeCode
        target.targetObservation
    componentoutBoundRelationship[typeCode=COMP]
        codecode
        value[x]value
        dataAbsentReasonvalue.nullFlavor
        interpretationinterpretationCode
        referenceRangeoutboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]

10.1.8.2 Mappings for HL7 v2 Mapping (http://hl7.org/v2)

ObservationOBX
    identifierOBX.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 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
    statusOBX-11
    category
    codeOBX-3
    subjectPID-3
    encounterPV1
    effective[x]OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
    issuedOBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)
    performerOBX.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
    dataAbsentReasonN/A
    interpretationOBX-8
    commentNTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)
    bodySiteOBX-20
    methodOBX-17
    specimenSPM segment
    deviceOBX-17 / PRT -10
    referenceRangeOBX.7
        lowOBX-7
        highOBX-7
        meaningOBX-10?
        age
        textOBX-7
    relatedRelationships established by OBX-4 usage
        typeN/A
        target
    componentcontainment by OBX-4?
        codeOBX-3
        value[x]OBX.2, OBX.5, OBX.6
        dataAbsentReasonN/A
        interpretationOBX-8
        referenceRangeOBX.7