OpenMRS Core FHIR Implementation Guide
0.1.0 - ci-build

OpenMRS Core FHIR Implementation Guide, published by . This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/abertnamanya/openmrs-contrib-fhir2-ig/ and changes regularly. See the Directory of published versions

Resource Profile: OMRSRelatedPerson - Mappings

Active as of 2024-12-11

Mappings for the omrs-related-person resource profile.

Mappings for FHIR HL7 vs OMRS (Relationship)

This mapping defines how a FHIR RelatedPerson resource corresponds to an OpenMRS Relationship. In OpenMRS, a Relationship connects two Person objects, while in FHIR, a RelatedPerson represents a person with a connection to a patient.

OMRSRelatedPerson
RelatedPersonOMRS Relationship

This profile maps to RelatedPerson in OMRS FHIR2

   idRelationship.uuid
   identifier
      systemRelatedPerson
      valuePerson/{personA.uuid}
   patientRelationship.personB
   name
      familyRelationship.personA.names.family
      givenRelationship.personA.names.given
   genderRelationship.personA.gender
   birthDateRelationship.personA.birthdate
   addressRelationship.personA.addresses
   period
      startRelationship.startDate
      endRelationship.endDate

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

OMRSRelatedPerson
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
   namename
      idn/a
      extensionn/a
      useunique(./use)
      text./formatted
      family./part[partType = FAM]
      given./part[partType = GIV]
      prefix./part[partType = PFX]
      suffix./part[partType = SFX]
      period./usablePeriod[type="IVL<TS>"]
   telecomtelecom
   genderadministrativeGender
   birthDateplayer.birthTime
   addressaddr
   photoplayer[classCode='PSN' and determinerCode='INSTANCE']/desc
   period.effectiveTime
      idn/a
      extensionn/a
      start./low
      end./high
   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)

OMRSRelatedPerson
RelatedPerson
   identifierFiveWs.identifier
   activeFiveWs.status
   relationshipFiveWs.class
   periodFiveWs.done[x]

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

OMRSRelatedPerson
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
   nameNK1-2
      useXPN.7, but often indicated by which field contains the name
      textimplied by XPN.11
      familyXPN.1/FN.1
      givenXPN.2 + XPN.3
      prefixXPN.5
      suffixXPN/4
      periodXPN.13 + XPN.14
   telecomNK1-5 / NK1-6 / NK1-40
   genderNK1-15
   addressNK1-4
   photoOBX-5 - needs a profile
   period
      startDR.1
      endDR.2