Estonian Base Implementation Guide
1.1.1 - trial-use Estonia flag

Publication Build: This will be filled in by the publication tooling

Resource Profile: EEBaseRelatedPerson - Mappings

Draft as of 2024-07-30

Mappings for the ee-related-person resource profile.

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

EEBaseRelatedPerson
RelatedPersonadministrative.individual
   identifierFiveWs.identifier
   activeFiveWs.status
   relationshipFiveWs.class
   relationship (class)FiveWs.class
   relationship (person)FiveWs.class
   periodFiveWs.done[x]

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

EEBaseRelatedPerson
RelatedPersonEntity, Role, or Act,role
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifier.id
      idn/a
      extensionn/a
      useRole.code or implied by context
      typeRole.code or implied by context
      systemII.root or Role.id.root
      valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
      periodRole.effectiveTime or implied by context
      assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
   active.statusCode
   patientscoper[classCode=PSN|ANM and determinerCode='INSTANCE']/playedRole[classCode='PAT']/id
   relationshipcode
   relationship (class)code
      idn/a
      extensionn/a
      codingunion(., ./translation)
         idn/a
         extensionn/a
         system./codeSystem
         version./codeSystemVersion
         code./code
         displayCV.displayName
         userSelectedCD.codingRationale
      text./originalText[mediaType/code="text/plain"]/data
   relationship (person)code
      idn/a
      extensionn/a
      codingunion(., ./translation)
         idn/a
         extensionn/a
         system./codeSystem
         version./codeSystemVersion
         code./code
         displayCV.displayName
         userSelectedCD.codingRationale
      text./originalText[mediaType/code="text/plain"]/data
   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 Interface Pattern (http://hl7.org/fhir/interface)

EEBaseRelatedPerson
RelatedPersonParticipantLiving
   identifierParticipant.identifier
   activeParticipant.active
   nameParticipant.name
   telecomParticipantContactable.telecom
   genderParticipantLiving.gender
   birthDateParticipantLiving.birthDate
   photoParticipantLiving.photo
   communicationParticipantLiving.communication

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

EEBaseRelatedPerson
RelatedPerson
   identifierNK1-33
      useN/A
      typeCX.5
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   patientPID-3
   relationshipNK1-3
   relationship (class)NK1-3
      codingC*E.1-8, C*E.10-22
         systemC*E.3
         versionC*E.7
         codeC*E.1
         displayC*E.2 - but note this is not well followed
         userSelectedSometimes implied by being first
      textC*E.9. But note many systems use C*E.2 for this
   relationship (person)NK1-3
      codingC*E.1-8, C*E.10-22
         systemC*E.3
         versionC*E.7
         codeC*E.1
         displayC*E.2 - but note this is not well followed
         userSelectedSometimes implied by being first
      textC*E.9. But note many systems use C*E.2 for this
   nameNK1-2
   telecomNK1-5 / NK1-6 / NK1-40
   genderNK1-15
   addressXAD
   photoOBX-5 - needs a profile