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

8.1.16 8.1.17 Resource Patient - Mappings

Maturity Level : N/A
Responsible Owner: Patient Administration icon Work Group Standards Status : Informative Security Category : Patient Compartments : Patient , Practitioner , RelatedPerson

Mappings:

FiveWs Pattern Mapping

Interface Pattern

HL7 V2 Mapping

LOINC code for the element

CDA (R2)

RIM Mapping

DICOM Tag Mapping

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

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

Patient administrative.individual
    identifier FiveWs.identifier
    active FiveWs.status

8.1.16.2 8.1.17.2 Interface Pattern ( http://hl7.org/fhir/interface icon )

Patient ParticipantLiving
    identifier Participant.identifier
    active Participant.active
    name Participant.name
    telecom ParticipantContactable.telecom
    gender ParticipantLiving.gender
    birthDate ParticipantLiving.birthDate
    address ParticipantContactable.address
    photo ParticipantLiving.photo
    communication ParticipantLiving.communication

8.1.16.3 8.1.17.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.
Patient
    identifier PID-3
    active
    name PID-5, PID-9
    telecom PID-13, PID-14, PID-40
    gender PID-8
    birthDate PID-7
    deceased[x] PID-30 (bool) and PID-29 (datetime)
    address PID-11
    maritalStatus PID-16
    multipleBirth[x] PID-24 (bool), PID-25 (integer)
    photo OBX-5 - needs a profile
    contact
        relationship NK1-7, NK1-3
        role NK1-7, NK1-3
        name NK1-2
        additionalName NK1-2
        telecom NK1-5, NK1-6, NK1-40
        address NK1-4
        additionalAddress NK1-4
        gender NK1-15
        organization NK1-13, NK1-30, NK1-31, NK1-32, NK1-41
        period
    communication
        language PID-15, LAN-2
        preferred PID-15
    generalPractitioner PD1-4
    managingOrganization
    link
        other PID-3, MRG-1
        type

8.1.16.4 8.1.17.4 LOINC code for the element ( http://loinc.org icon )

Patient
    identifier
    active
    name
    telecom
    gender
    birthDate 21112-8
    deceased[x]
    address
    maritalStatus
    multipleBirth[x]
    photo
    contact
        relationship
        role
        name
        additionalName
        telecom
        address
        additionalAddress
        gender
        organization
        period
    communication
        language
        preferred
    generalPractitioner
    managingOrganization
    link
        other
        type

8.1.16.5 8.1.17.5 CDA (R2) ( http://hl7.org/v3/cda icon )

Patient ClinicalDocument.recordTarget.patientRole
    identifier .id
    active n/a
    name .patient.name
    telecom .telecom
    gender .patient.administrativeGenderCode
    birthDate .patient.birthTime
    deceased[x] n/a
    address .addr
    maritalStatus .patient.maritalStatusCode
    multipleBirth[x] n/a
    photo n/a
    contact n/a
        relationship n/a
        role n/a
        name n/a
        additionalName n/a
        telecom n/a
        address n/a
        additionalAddress n/a
        gender n/a
        organization n/a
        period n/a
    communication patient.languageCommunication
        language .languageCode
        preferred .preferenceInd
    generalPractitioner n/a
    managingOrganization .providerOrganization
    link n/a
        other n/a
        type n/a

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

Patient Patient[classCode=PAT]
    identifier id
    active statusCode
    name name
    telecom telecom
    gender player[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
    birthDate player[classCode=PSN|ANM and determinerCode=INSTANCE]/birthTime
    deceased[x] player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/deceasedTime
    address addr
    maritalStatus player[classCode=PSN]/maritalStatusCode
    multipleBirth[x] player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthInd, player[classCode=PSN|ANM and determinerCode=INSTANCE]/multipleBirthOrderNumber
    photo player[classCode=PSN|ANM and determinerCode=INSTANCE]/desc
    contact player[classCode=PSN|ANM and determinerCode=INSTANCE]/scopedRole[classCode=CON]
        relationship code
        role code
        name name
        additionalName name
        telecom telecom
        address addr
        additionalAddress addr
        gender player[classCode=PSN|ANM and determinerCode=INSTANCE]/administrativeGender
        organization scoper
        period effectiveTime
    communication LanguageCommunication
        language player[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
        preferred preferenceInd
    generalPractitioner subjectOf.CareEvent.performer.AssignedEntity
    managingOrganization scoper
    link outboundLink
        other id
        type typeCode

8.1.17.7 DICOM Tag Mapping ( https://dicomstandard.org/current icon )

Patient DICOM Tag Mapping
    identifier Patient Identifier (0010,0020)
    active
    name Patient Name (0010,0010) and Person Names to Use Sequence (0010,0011)
    telecom
    gender Patient's Sex (0010,0040)
    birthDate Patient's Birth Date (0010,0030)
    deceased[x] Patient's Death Date in Alternative Calendar (0010,0034)
    address
    maritalStatus
    multipleBirth[x]
    photo
    contact
        relationship
        role
        name
        additionalName
        telecom
        address
        additionalAddress
        gender
        organization
        period
    communication
        language
        preferred
    generalPractitioner
    managingOrganization
    link
        other
        type