KLGateway, published by KL. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7dk/kl-gateway/ and changes regularly. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON
• TTL

Resource Profile: KLGatewayCareGeneralEncounter - Mappings

Active as of 2024-10-31

Mappings for the klgateway-care-general-encounter resource profile.

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

KLGatewayCareGeneralEncounter
Encounter	Event
status	Event.status
type	Event.code
subject	Event.subject
period	Event.occurrence[x]
reasonReference	Event.reasonCode

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

KLGatewayCareGeneralEncounter
Encounter	Entity. Role, or Act, Encounter[@moodCode='EVN']
text	Act.text?
contained	N/A
extension
extension (basedOnIntervention)
id	n/a
url	N/A
value[x]	N/A
modifierExtension	N/A
status	.statusCode
class	.inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
id	n/a
extension	n/a
system	./codeSystem
code	./code
display	CV.displayName
type	.code
id	n/a
extension	n/a
coding	union(., ./translation)
id	n/a
extension	n/a
system	./codeSystem
code	./code
display	CV.displayName
subject	.participation[typeCode=SBJ]/role[classCode=PAT]
period	.effectiveTime (low & high)
id	n/a
extension	n/a
start	./low
end	./high
reasonReference	.reasonCode

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

KLGatewayCareGeneralEncounter
Encounter
status	FiveWs.status
class	FiveWs.class
type	FiveWs.class
subject	FiveWs.subject[x], FiveWs.subject
period	FiveWs.done[x]
reasonReference	FiveWs.why[x]

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

KLGatewayCareGeneralEncounter
Encounter
status	No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16
class	PV1-2
system	C*E.3
code	C*E.1
display	C*E.2 - but note this is not well followed
type	PV1-4 / PV1-18
coding	C*E.1-8, C*E.10-22
system	C*E.3
code	C*E.1
display	C*E.2 - but note this is not well followed
subject	PID-3
period	PV1-44, PV1-45
start	DR.1
end	DR.2
reasonReference	EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )