1.2.0 - release

This page is part of the KL Gateway (v1.2.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Resource Profile: CareGeneralEncounter

Official URL: http://fhir.kl.dk/gateway/StructureDefinition/klgateway-care-general-encounter Version: 1.2.0
Active as of 2024-10-31 Computable Name: KLGatewayCareGeneralEncounter

Encounter for planned and completed meetings between citizens and care staff.

Scope and usage

The Encounter may be instantiated whenever citizens and practitioners meet in a Danish municipality context.

It is mandatory in FSIII to be able to express follow-up encounters on Conditions. In the planning state, these are documented by setting Encounter.status = 'planned', and Encounter.type.coding = 'opfølgning'.

Encounters which are finished may also be reported. This can be especially relevant for Encounter.type.coding = 'opfølgning' and Encounter.type.coding = 'udførelse af planlagt indsats'. Use Encounter.status 'finished'. Reporting on finished encounters is optional.

To report errors use status 'entered-in-error'

Encounter.class is mandatory in FHIR. In Danish municipalities the values are used as follows.

  • Visits in citizens homes have the code 'HH' Home health, the code is also used for services that are not strictly health related e.g. help with cleaning. This code is also used, even if the activities stretch outside the citizens residence e.g. a physiotherapist that want to see a citizen walk outside, or a social worker helping with shopping activities.
  • Sessions where the citizens visit municipality facilities e.g. for training or health prevention have the code 'AMB' Ambulatory.
  • Encounters delivered as a screen visit should be registered as 'Skærmbesøg'.
  • Encounters delivered using a phone should be registered as 'Telefonisk'

The time of the encounter is documented in Encounter.period.start and Encounter.periode.end, and Encounter.period.start is mandatory. Only planned time is mandatory to report. There is no expectation that the staff update the time if they finish a little earlier or a little later. Time of day is also not mandatory. Encounter.periode.end and time of day is encouraged when reporting on finished Encounters.

Encounters can be related to the PlannedIntervention on which they are a delivery. Use Encounter.extension[basedOnCarePlan]. Encounters can also be related to the condition or conditions which are the reason for having the encounter. This is used for documenting the condition follow-up encounter. Use Encounter.reasonReference

Conversions between Danish information model and FHIR-profile

Nedenstående tabel oversætter mellem de attributter der er defineret i den fælleskommunale informationsmodel (FKI), definerer kort den enkelte attribut på dansk og specificere hvilke af FHIR-profilens atributter der skal bruges til specifikation af indholdet

FKI-attribut Definition FHIR
borgerkontaktstatus Klasse der indikerer om kontakten er igangværende, eller om dokumentationen repræsentere en fremtidig intention eller er historisk Encounter.status
kontakttype Klasse der udtrykker typen af aktivitet der gennemføres ved kontakten Encounter.type.coding
borgerkontaktklasse Klasse, der udtrykker en generel kategori for kontaktens leveringsform. Encounter.class
borgerkontaktstart Kontaktens start, eller planlagte start Encounter.period.start
borgerkontaktslut Kontaktens sluttidspunkt, eller planlagte sluttidspunkt Encounter.period.end
borgerkontaktsubjekt Den borger kontakten vedrører Encounter.subject
borgerkontaktBaseretPå Den eller de indsatser, der er grunden til at denne kontakt udføres Encounter.extension:basedOnCarePlan
borgerkontaktTilstand Den eller de tilstande, der er grunden til at denne kontakt udføres Encounter.reasonReference

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Encounter

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..* Encounter An interaction during which services are provided to the patient
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... basedOnIntervention 0..* (Complex) [DK] kontaktIndsats
URL: http://fhir.kl.dk/gateway/StructureDefinition/BasedOnInterventionExtension
..... value[x] 1..1 Reference(CarePlannedIntervention) {b} Value of extension
... identifier 0..0
... status 1..1 code [DK] kontaktstatus
... class 1..1 Coding [DK] kontaktklasse
Binding: KontaktKlasseKoder (required)
.... version 0..0
.... userSelected 0..0
... classHistory 0..0
... type 1..* CodeableConcept Specific type of encounter
Binding: KLKontaktTyper (required)
.... coding 1..1 Coding [DK] kontakttype
..... version 0..0
..... userSelected 0..0
.... text 0..0
... serviceType 0..0
... priority 0..0
... subject 1..1 Reference(CareCitizen) {b} [DK] kontaktsubjekt
... episodeOfCare 0..0
... basedOn 0..0
... participant 0..0
... appointment 0..0
... period 1..1 Period The start and end time of the encounter
.... start 1..1 dateTime [DK] kontaktstart
.... end 0..1 dateTime [DK] kontaktslut
... length 0..0
... reasonCode 0..0
... reasonReference 0..* Reference(CareCondition) [DK] kontaktTilstand
... diagnosis 0..0
... account 0..0
... hospitalization 0..0
... location 0..0
... serviceProvider 0..0
... partOf 0..0

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Encounter.classrequiredEncounterClassCodes
http://fhir.kl.dk/gateway/ValueSet/EncounterClassCodes
from this IG
Encounter.typerequiredKLEncounterTypes
http://fhir.kl.dk/term/ValueSet/KLEncounterTypes

 

Other representations of profile: CSV, Excel, Schematron