Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3 R2

9.4.7 Resource FamilyMemberHistory - Mappings

Maturity Level : N/A
Responsible Owner: Patient Care icon Work Group Standards Status : Informative Security Category : Patient Compartments : Patient

Mappings:

FiveWs Pattern Mapping

Workflow Pattern

HL7 V2 Mapping

RIM Mapping

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

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

FamilyMemberHistory clinical.general
    identifier FiveWs.identifier
    status FiveWs.status
    patient FiveWs.subject[x] FiveWs.subject
    date FiveWs.recorded
        actor     recorder FiveWs.author
FiveWs.who     asserter FiveWs.source
    reason FiveWs.why[x]

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

FamilyMemberHistory Event
    identifier Event.identifier
    instantiatesCanonical Event.instantiatesCanonical     instantiatesUri Event.instantiatesUri     status Event.status
    patient Event.subject
    reason Event.reason
    note Event.note

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

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 icon , provides additional guidance on transforming an HL7 v2 message to FHIR resources for FHIR R4 and FHIR R6.
    instantiatesCanonical     instantiatesUri
FamilyMemberHistory Not in scope for v2
    identifier
    status
    dataAbsentReason
    patient
    date
    participant         function     recorder
        actor     asserter REL-7.1 identifier + REL-7.12 type code
    name
    relationship
    sex
    born[x]
    age[x]
    estimatedAge
    deceased[x]
    reason
    note
    condition
        code
        outcome
        contributedToDeath
        onset[x]
        note
    procedure
        code
        outcome
        contributedToDeath
        performed[x]
        note

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

.participation.functionCode .player
FamilyMemberHistory Observation[classCode=OBS, moodCode=EVN]
    identifier id
    instantiatesCanonical .outboundRelationship[typeCode=DEFN].target     instantiatesUri .outboundRelationship[typeCode=DEFN].target     dataAbsentReason .reasonCode
    patient participation[typeCode=SBJ].role
    date participation[typeCode=AUT].time
    participant .participation[typeCode=PRF]         function     recorder .participation[typeCode=AUT].role
        actor     asserter .participation[typeCode=INF].role
    name name
    relationship code
    born[x] player[classCode=LIV, determinerCode=INSTANCE]. birthDate (could be URG)
    age[x] participation[typeCode=SBJ].act[classCode=OBS,moodCode=EVN, code="age"].value
    deceased[x] player[classCode=LIV, determinerCode=INSTANCE].deceasedInd, deceasedDate (could be URG) For age, you'd hang an observation off the role
    reason .reasonCode
    note inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=ActCode#ANNGEN].value
    condition inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=ActCode#ASSERTION, value<Diagnosis]
        code .value
        outcome outboundRelationship[typeCode=OUTC)].target[classCode=OBS, moodCode=EVN, code=ActCode#ASSERTION].value
        onset[x] inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="Subject Age at measurement", value<Diagnosis].value[@xsi:typeCode='TS' or 'IVL_TS'] Use originalText for string
        note inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=ActCode#ANNGEN].value