Estonian Base Implementation Guide
1.1.1 - trial-use Estonia flag

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

Resource Profile: EEBaseLocation - Mappings

Draft as of 2024-07-30

Mappings for the ee-location resource profile.

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

EEBaseLocation
Locationadministrative.entity
   identifierFiveWs.identifier
   statusFiveWs.status
   operationalStatusFiveWs.status
   modeFiveWs.class
   typeFiveWs.class
   formFiveWs.class

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

EEBaseLocation
LocationEntity, Role, or Act,.Role[classCode=SDLC]
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifier.id
   status.statusCode
   operationalStatusn/a
   name.name
   alias.name
   description.playingEntity[classCode=PLC determinerCode=INSTANCE].desc
   mode.playingEntity[classCode=PLC].determinerCode
   type.code
   contact.telecom and .addr and other .role(relevant datatype properties mapped from role into extendedcontactdetail)
   addressn/a,AD
   form.playingEntity [classCode=PLC].code
   position.playingEntity [classCode=PLC determinerCode=INSTANCE].positionText
      idn/a
      extensionn/a
      modifierExtensionN/A
      longitude(RIM Opted not to map the sub-elements of GPS location, is now an OBS)
      latitude(RIM Opted not to map the sub-elements of GPS location, is now an OBS)
      altitude(RIM Opted not to map the sub-elements of GPS location, is now an OBS)
   managingOrganization.scopingEntity[classCode=ORG determinerKind=INSTANCE]
   partOf.inboundLink[typeCode=PART].source[classCode=SDLOC]
   characteristic.actrelationship[typeCode=PERT].observation
   hoursOfOperation.effectiveTime
   virtualServiceN/A
   endpointn/a

Mappings for Interface Pattern (http://hl7.org/fhir/interface)

EEBaseLocation
LocationParticipantContactable
   identifierParticipant.identifier
   statusParticipant.active
   nameParticipant.name