eHealth Infrastructure
2.9.0 - release

eHealth Infrastructure - Local Development build (v2.9.0). See the Directory of published versions

Resource Profile: ehealth-relatedperson - Mappings

Active as of 2023-08-23

Mappings for the ehealth-relatedperson resource profile.

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

ehealth-relatedperson
RelatedPersonEntity. Role, or Act, role
   textAct.text?
   containedN/A
   modifierExtensionN/A
   identifier.id
   identifier (ehealth-dk-crn-identifier)n/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
      idn/a
      extensionn/a
      codingunion(., ./translation)
      text./originalText[mediaType/code="text/plain"]/data
   namename
   telecomtelecom
   genderadministrativeGender
   birthDateplayer.birthTime
   addressaddr
   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)

ehealth-relatedperson
RelatedPerson
   identifierFiveWs.identifier
   activeFiveWs.status
   relationshipFiveWs.class
   periodFiveWs.done[x]

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

ehealth-relatedperson
RelatedPerson
   identifierNK1-33
   identifier (ehealth-dk-crn-identifier)CX / EI (occasionally, more often EI maps to a resource id or a URL)
   patientPID-3
   relationshipNK1-3
      codingC*E.1-8, C*E.10-22
      textC*E.9. But note many systems use C*E.2 for this
   nameNK1-2
   telecomNK1-5 / NK1-6 / NK1-40
   genderNK1-15
   addressNK1-4
   photoOBX-5 - needs a profile