DK MedCom Notes
0.1.0 - draft
DK MedCom Notes, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-notes/ and changes regularly. See the Directory of published versions
| Official URL: http://medcomfhir.dk/ig/notes/ImplementationGuide/medcom.fhir.dk.notes | Version: 0.1.0 | |||
| Draft as of 2026-02-02 | Computable Name: MedComNotes | |||
This implementation guide (IG) is provided by MedCom to describe the use of FHIR ®© Shared Notes (Da: Deling af Journalnotater) in document based exchange of data in Danish healthcare.
This IG contains profiles supporting the MedCom document Shared Notes. The purpose of sharing notes is to make the notes from a healthcare provider - at first the general practice - available to relevant healthcare actors, thereby supporting continuity of care and providing insight into clinically relevant assessments, observations, and decisions documented by the general practitioner.
More information about the project Shared Notes from General Practice can be found here.
The MedCom document Shared Notes will be exchanged via the National Service Platform (NSP) using the Document Sharing Service (DDS), which is already used for national sharing of healthcare documents. Each document must contain only one note and related information, therefore will the system requesting the notes receive multiple document if the patient has been to multiple consultations e.g. at the general practitioner.
The FHIR standard will ensure consistent structuring of metadata and clinically relevant information, enabling Shared Notes to be searched, interpreted, and used correctly by receiving systems, clinicians and patiens.
The structure of the Shared Notes document is depicted in the following diagram:
The Shared Notes IG follows the general MedCom FHIR Document model. This includes the resources Bundle, Composition, Organization, Patient and if relevant Practitioner. To hold information about the patient's Notes, the resource Observation is also included.
The following sections describe the overall purpose of each profile.
MedComNotesBundle is used as the Bundle profile for the standard. This profiles inheritsfrom MedComDocumentBundle. The Bundle profile acts as the container for all included resources and they must all be referenced from the Bundle.entry element, which is illustrated in the examples.
MedComNotesComposition creates the structure of the document. It is specifically designed for structuring patients' Notes, inheriting from MedComDocumentComposition. The key differences are: the Composition.type is fixed to "Consult note" to standardize the document type; the Composition.title must be the following in Danish: "Journalnotat for 'CPR-nummer'"; and the Composition.section.entry is restricted to reference MedComNotesObservation.
MedComNotesObservation is the profile that specifies the note in the document. It inherits from MedComDocumentObservation and further restricts the profile, for example is valueattachment specified to only include the data as xhtml+xml, which is where the note will be included.
MedComDocumentPatient describes the basic requirements for information about citizens and patients when exchanging a document. The profile inherits from MedComCorePatient and further limit the requirements, e.g. may documents only be exchanged for patients with a CPR-number. It is not allowed to add a replacement-CPR (Danish: erstatningsCPR), as this is not supported in the infrastructure.
MedComDocumentOrganization is a profile representing Danish healthcare organizations that acts as the author institution in FHIR Documents. The profile inherits from MedComCoreOrganization.
MedComDocumentPractitionerRole represents the role of the health care professional that acts as the author person. The profile inherits from MedComCorePractitionerRole
MedComDocumentPractitioner represents the health care professional that acts as the author person. The profile inherits from MedComCorePractitioner and further requires a given and family name to be present.
A Shared Notes document includes several timestamps. These timestamps are present in the profiles MedComNotesBundle, MedComNotesComposition and MedComNotesObservation. They have different purposes:
If the Composition.date and Observation.effectiveDatetime are similar, this represents that the note has not been updated after it was generated. If the two timestamps are different, this represents that the note has been updated after it was generated.
The examples page different examples of the Shared Notes standard. Each example is accompanied by a short description of the example.
On MedCom Terminology IG all referenced CodeSystem and ValueSets developed by MedCom can be found.