Danish MedCom Core
2.3.0 - Release Denmark flag

This page is part of the DK MedCom Core (v2.3.0: Release) based on FHIR R4. The current version which supercedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

Resource Profile: MedComCoreEncounter

Official URL: http://medcomfhir.dk/ig/core/StructureDefinition/medcom-core-encounter Version: 2.3.0
Active as of 2023-10-31 Computable Name: MedComCoreEncounter

An interaction between a patient/citizen and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient/citizen.

Scope and usage

This profile describes the MedComCoreEncounter. An encounter describes the interaction between a patient and one or more healthcare providers for the purpose of providing healthcare services or assessing the health status of a patient. An encounter can take place in an ambulatory, an emergency, at the citizen’s home, virtually and so on.

The base expectations when describing an encounter in a Danish context is to include the subject of the encounter which shall be a MedComCorePatient as well as a status and class, which are described below. For some specific purposes, such as HospitalNotification, there is a need for a specialization of the MedComCoreEncounter. In these cases, it will be explicitly described which encounter to use and which changed are applied.

Please refer to the tab “Snapshot Table(Must support)” below for the definition of the required content of a MedComCoreEncounter.

Status and class

A status and class shall be included MedComCoreEncounter.

The status refers to the current state of the encounter. This will most often change due to the nature an encounter, as it will pass through many statuses which follows the workflow of the encounter. A status can be ‘in-progress’ describing that the patient is present or the meeting has begun, or ‘finished’ describing that the encounter is finished.

The class describes in which setting the encounter took place. A setting of the encounter can be ‘emergency’, ‘ambulant’ or ‘inpatient’.

EpisodeOfCare identifier

The element Encounter.episodeOfCare may be included in MedComCoreEncounter.

The EpisodeOfCare identifier is used to technically connect several encounters concern the same meeting between a patient and one or more healthcare providers.

It is both possible to use a Landspatientregisteret-identifier (called LPR3-identifier) and a locally defined identifier as the EpisodeOfCare-identifier.

Whether a LPR3-identifier or a locally defined identifier is used, it shall be an UUID. The LPR3-identifier shall obey a rule stating that the UUID shall be of version 5, here more information about the LPR3-identifier can be found. Using a locally defined identifier, a system for the identifier shall be added.

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..*EncounterAn interaction during which services are provided to the patient
... status S1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
... class S1..1CodingClassification of patient encounter
Binding: MedComCoreEncounterClassCodes (required)
... subject S1..1Reference(MedComCorePatient) {b}The patient or group present at the encounter
.... episodeOfCare:All Slices Content/Rules for all slices
..... identifier S0..1IdentifierLogical reference, when literal reference is not known
.... episodeOfCare:lpr3identifier S0..1Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
..... identifier 1..1Lpr3IdentifierAn identifier intended for computation
... account 0..0
... serviceProvider S0..1Reference(MedComCoreOrganization) {b}The organization (facility) responsible for this encounter

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Encounter.classrequiredMedComCoreEncounterClass

 

Other representations of profile: CSV, Excel, Schematron