DK Core, MedCom messaging and sundhed.dk: three Danish FHIR products
DK Core 3.7.0 is the HL7 Denmark baseline. MedCom FHIR messaging and the sundhed.dk eHealth Infrastructure are different products. CPR uses urn:oid:1.2.208.176.1.2. Do not collapse them into one Danish FHIR server.
Ala Ben Aicha
Direct answer
DK Core 3.7.0 is the HL7 Denmark baseline. MedCom FHIR messaging and the sundhed.dk eHealth Infrastructure IG are different products. CPR uses urn:oid:1.2.208.176.1.2.
Three publications, three buyers
Danish FHIR work is easy to flatten into “dk-core”. HL7 Denmark, MedCom and the national telemedicine infrastructure publish different implementation guides. A CareCommunication message is not an eHealth CarePlan API, and neither is a substitute for DK Core Patient.
| Layer | Owner / home | Canonical / package | What it is | What it is not |
|---|---|---|---|---|
| DK Core 3.7.0 (release, 30 May 2026) | HL7 Denmark; hl7.dk/fhir/core | Official URL http://hl7.dk/fhir/core/ImplementationGuide/hl7.fhir.dk.core; package hl7.fhir.dk.core#3.7.0 on FHIR R4 |
National base for identifiers, Patient, Organization, Observation and related profiles. Listed in the Danish Health Data Authority standard catalogue after RUSA | Not a FHIR API specification yet (the IG says so), not MedCom messaging |
| MedCom Core / messaging | MedCom; medcomfhir.dk/ig | MedCom Core official URL http://medcomfhir.dk/ig/core/ImplementationGuide/medcom.fhir.dk.core; package family medcom.fhir.dk.core. Messaging, HospitalNotification, CareCommunication are separate IGs |
Message exchange (hospital notification, correspondence, acknowledgement) replacing older VANS/EDIFACT-era MedCom standards over time | Not DK Core, not a REST EHR, not sundhed.dk telemedicine |
| eHealth Infrastructure 10.0.1 (release, 11 Aug 2026) | Den telemedicinske infrastruktur; ehealth.sundhed.dk/fhir | Official URL http://ehealth.sundhed.dk/fhir/ImplementationGuide/dk.ehealth.sundhed.fhir.ig.core; package dk.ehealth.sundhed.fhir.ig.core#10.0.1 |
National telemedicine FHIR platform (CarePlan, infrastructure operations) | Not MedCom hospital messaging, not a generic national EHR |
Primary sources: DK Core 3.7.0 (published package; prefer this over build.fhir.org/ig/hl7dk/dk-core), MedCom IG index, eHealth Infrastructure 10.0.1. CI builds of MedCom (for example build.fhir.org/ig/medcomdk/dk-medcom-core) change; pin the published package the buyer names.
DK Core 3.7.0 is the current published release as of write day. Do not implement the 3.6.0/3.5.0 trees unless the contract freezes them.
The identifier: CPR
Country-specific identifier for Danish Patient is the Central Person Register number. DK Core datatype DkCoreCprIdentifier fixes:
urn:oid:1.2.208.176.1.2
Ten digits, use official, with a CPR format invariant. MedCom Core Patient also requires CPR or eCPR. Replacement identifiers (X-eCPR, D-eCPR) are separate DK Core identifier profiles — they are not CPR. Do not publish a real CPR. Keep the system URL and a dummy value in fixtures.
SOR-id identifies organisations. It does not identify patients.
What to implement first
- If the buyer needs a Danish Patient / identifier pack: DK Core 3.7.0, CPR system as above, package
hl7.fhir.dk.core#3.7.0. - If the buyer is replacing MedCom correspondence or hospital notification: the named MedCom messaging IG (CareCommunication, HospitalNotification, Acknowledgement), not the eHealth Infrastructure.
- If the buyer is on sundhed.dk telemedicine: eHealth Infrastructure 10.0.1. It depends on DK Core; it is not MedCom.
- For EHDS payloads, overlay EU Core. Neighbouring NLL is a Swedish medication-list API, not a Danish equivalent.
The HL7 FHIR R4 integration guide is the generic REST primer. MedCom MessageHeader rules override it.
What this is not
This article is not MedCom approval, not a Sundhedsdatastyrelsen certificate, not eHealth Infrastructure onboarding, and not legal advice. Implementing DK Core profiles does not enrol you in MedCom or in the telemedicine infrastructure. I do not operate those environments. Nothing here is clinical advice.
Related reading
For mapping work against DK Core or MedCom, use HL7 FHIR integration or start a project.