Australian Base Implementation Guide

This page is part of AU Base v4.0.0 based on FHIR R4. For a full list of available versions, see the Directory of published versions

D.4.1.4 StructureDefinition: AUBaseRelatedPerson - Mappings

Mappings for the StructureDefinition-au-relatedperson Profile.

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

AUBaseRelatedPerson
RelatedPersonEntity. Role, or Act, role
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifiern/a, II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
   active.statusCode
   patientscoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
   relationshipcode
   namename
   telecomtelecom
   genderadministrativeGender
   birthDateplayer.birthTime
   addressn/a, AD
   photoplayer[classCode='PSN' and determinerCode='INSTANCE']/desc
   period.effectiveTime
   communicationLanguageCommunication
      idn/a
      extensionn/a
      modifierExtensionN/A
      languageplayer[classCode=PSN|ANM and determinerCode=INSTANCE]/languageCommunication/code
      preferredpreferenceInd

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

AUBaseRelatedPerson
RelatedPerson
   activeFiveWs.status
   relationshipFiveWs.class
   periodFiveWs.done[x]

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

AUBaseRelatedPerson
RelatedPerson
   identifierCX / EI (occasionally, more often EI maps to a resource id or a URL)
   patientPID-3
   relationshipNK1-3
   nameNK1-2
   telecomNK1-5 / NK1-6 / NK1-40
   genderNK1-15
   addressXAD
   photoOBX-5 - needs a profile
Issues & Feedback