2.0.0 - Release

This page is part of the KLGatewayRehab (v2.0.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: KLGateway140Encounter

Official URL: http://fhir.kl.dk/rehab/StructureDefinition/klgateway-140-encounter Version: 2.0.0
Active as of 2024-06-14 Computable Name: KLGateway140Encounter

Encounter for first planned visits and all executed activities in a §140 care pathway

Scope and usage

klgateway-140-encounter is used whenever a citizen meets the rehabilitation staff in a Danish municipality context.

In the context of the rehabilitation repporting, all Encounter.status values may be used, but not all are mandatory. The mandatory part is:

  • To report all carried out encounters. For encounters carried out, use Encounter.status ‘finished’.
  • To report errors using status ‘entered-in-error’

Enconters that are planned, but not carried out are possible to report but not mandatory.

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 shpping activities.
  • Sessions where the citizens visit municipality facilities e.g. for training have the code “AMB” ambulatory.
  • For telehealth/telecare encounters, where the patient is contacted by telephone, by teleconference or e-mail, the code is ‘VR’ virtual.

Encounter.extension[basedOnCarePlan] should be populated with a reference to the care plan or planned intervention that describes the activities that are planned for the encounter.

The time of the encounter is documented in Encounter.period.start and Encounter.periode.end, and both attributes are 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.

Encounter.subject relates to the citizen that the encounter is about.

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
borgerkontaktklasse Klasse, der udtrykker en generel kategori for kontakten, som rækker ud over den kommunale kontekst. 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
borgerkontaktanledning Den henvisning/henvendelse, der er grunden til at denne kontakt udføres Encounter.basedOn
borgerkontaktBaseretPå Den care plan, der er grunden til at denne kontakt udføres Encounter.extension:basedOnCarePlan

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 Encounter
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... basedOnCarePlan 0..1 (Complex) [DK] kontaktBaseretPå
URL: http://fhir.kl.dk/rehab/StructureDefinition/BasedOnCarePlanExtension
..... value[x] 1..1 Reference(KLGateway140care-plan | KLGateway140PlannedIntervention) {b} Value of extension
... identifier 0..0
... status 1..1 code [DK] kontaktstatus
... class 1..1 Coding [DK] kontaktklasse
.... version 0..0
.... display 0..0
.... userSelected 0..0
... classHistory 0..0
... type
.... coding 0..0
.... text 0..0
... serviceType 0..0
... priority 0..0
... subject 1..1 Reference(KLGateway140Citizen) {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 1..1 dateTime [DK] kontaktslut
... length 0..0
... reasonCode 0..0
... reasonReference 0..0
... diagnosis 0..0
... account 0..0
... hospitalization 0..0
... location 0..0
... serviceProvider 0..0
... partOf 0..0

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron