KLChildren implementation guide, an implementation of FBU
2.0.0 - Release

This page is part of the KLChildren (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Resource Profile: KLGatewayChildrenEncounter - Mappings

Active as of 2024-06-05

Mappings for the klgateway-children-encounter resource profile.

Mappings for Workflow Pattern (http://hl7.org/fhir/workflow)

KLGatewayChildrenEncounter
EncounterEvent
   statusEvent.status
   typeEvent.code
   subjectEvent.subject
   periodEvent.occurrence[x]
   location
      locationEvent.location

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

KLGatewayChildrenEncounter
EncounterEntity. Role, or Act, Encounter[@moodCode='EVN']
   textAct.text?
   containedN/A
   extension
   extension (basedOnIntervention)
      idn/a
      urlN/A
      value[x]N/A
   modifierExtensionN/A
   status.statusCode
   class.inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
      idn/a
      extensionn/a
      system./codeSystem
      code./code
      displayCV.displayName
   type.code
      idn/a
      extensionn/a
      codingunion(., ./translation)
         idn/a
         extensionn/a
         system./codeSystem
         code./code
         displayCV.displayName
   subject.participation[typeCode=SBJ]/role[classCode=PAT]
   period.effectiveTime (low & high)
      idn/a
      extensionn/a
      start./low
      end./high
   location.participation[typeCode=LOC]
      idn/a
      extensionn/a
      modifierExtensionN/A
      location.role

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

KLGatewayChildrenEncounter
Encounter
   statusFiveWs.status
   classFiveWs.class
   typeFiveWs.class
   subjectFiveWs.subject[x], FiveWs.subject
   periodFiveWs.done[x]
   location
      locationFiveWs.where[x]

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

KLGatewayChildrenEncounter
Encounter
   statusNo clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16
   classPV1-2
      systemC*E.3
      codeC*E.1
      displayC*E.2 - but note this is not well followed
   typePV1-4 / PV1-18
      codingC*E.1-8, C*E.10-22
         systemC*E.3
         codeC*E.1
         displayC*E.2 - but note this is not well followed
   subjectPID-3
   periodPV1-44, PV1-45
      startDR.1
      endDR.2
   location
      locationPV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43