DK MedCom Messaging
2.0.0 - Release Denmark flag

This page is part of the DK MedCom Messaging (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions


Official URL: Version: 2.0.0
Active as of 2024-02-15 Computable Name: MedComMessaging


This Implementation Guide (IG) is provided by MedCom to describe the use of FHIR ®© in message based exchange of data in Danish healthcare.

The IG contains profiles which are used to define a general messaging model for MedCom messages, like HospitalNotification, CareCommunication and Acknowledgement.

General Messaging Model

The figure below illustrates a general messaging model, which all MedCom messages will comply to. Messaging profiles are all prefixed “MedComMessaging”. Beside the profiles on the figure, a MedCom message will also include some MedComCore profiles and profiles made to support a specific use case. All together they constitute the actual content of a MedCom message. The following sections describe the overall purpose of each messaging profile.

Shows the general MedCom messaging model. Each message must at least contain the following resources: Bundle, MessageHeader, Organization and Provenance.


A Bundle resource defined to be of the type ‘message’. All profiles included in a message shall be referenced from the entry element in the MedComMessagingMessage profile, with a MessageHeader as the first resource.

Note: Be aware that entries in a message in general are unordered. Recipients of a message cannot assume any sequences of profiles.


The MessageHeader defines the sender and receiver organization of a message. In some messages it is optional to include a one or more carbon-copy receiver organization(s). From the focus element is the actual content of the message often referenced, like a Communication or Encounter resource.


This profile inherits from MedComCoreOrganization and is used to describe a sender and receiver organization. The resource constrains the MedComCoreOrganization profile to contain both a SOR identifier and an EAN identifier (also known as GLN) for addressing purposes.


The Provenance resource describes the activity of the message and who has triggered the message. Further is it used to describes the history of message activities e.g., if the message is related to a previously exchanged message.


On MedCom Terminology IG all referenced CodeSystem and ValueSets developed by MedCom can be found.


This IG has a dependency to the MedComCore IG and DK-core v. 1.1.0, defined by HL7 Denmark. This is currently reflected in MedComMessagingOrganization which inherits from MedComCoreOrganization.


More information about MedCom Messaging can be found here. MedComMessaging profiles does not alone constitute a standard, why the documentation is limited.


FHIR profiles are managed under MedCom: Source code.

A description of governance concerning change management and versioning of MedComs FHIR artefacts, can be found on the link.

Quality Assurance Report

In the Quality Assurance report (QA-report) for this IG, there is an error with the following description: Reference is remote which isn’t supported by the specified aggregation mode(s) for the reference (bundled). The error occurs when creating instances of the profiles and is due to some elements having a Bundled flag {b}, however the referenced profile is not included in a Bundle in an instance, since the instance only represents a part of the entire message. This should not influence the implementation by IT-vendors.


MedCom is responsible for this IG.

If you have any questions, please contact or write to MedCom’s stream in Zulip.