EHDS ePrescription and eDispensation: HL7 Europe MPD for category 1
EHDS category 1 ePrescription and eDispensation apply from March 2029. Pin HL7 Europe Medication Prescription and Dispense 1.0.0. Distinct from the EHDS regulation explainer, from Swedish NLL, and from MyHealth@EU.
Ala Ben Aicha
Direct answer
EHDS category 1 ePrescription and eDispensation apply from March 2029. Implement HL7 Europe MPD 1.0.0 MedicationRequestEuMpd and MedicationDispenseEuMpd. This is not the Swedish NLL API and not a MyHealth@EU product you operate.
Pin MPD 1.0.0, not “European FHIR medication”
The EHDS regulation overview on this site stays the policy map. EU Core and EHDS is the Base/Core and EEHRxF category table. This page is the category 1 medication payload: how HL7 Europe profiles MedicationRequest and MedicationDispense.
On write day (19 September 2026) the published R4 IG is HL7 Europe Medication Prescription and Dispense 1.0.0 (STU 1 / trial-use), generated 11 May 2026:
- Home: hl7.eu/fhir/mpd
- Official URL:
http://hl7.eu/fhir/mpd/ImplementationGuide/hl7.fhir.eu.mpd - Package:
hl7.fhir.eu.mpd#1.0.0on FHIR R4 - Xt-EHR supported this version as alignment with EHDS logical models, not as a Commission certificate
MPD profiles MedicationRequest and MedicationDispense; it has no Composition or document-Bundle profile. The implementation notes neither encourage nor ban a national document view (Bundle + Composition); that wrapper is simply out of MPD’s profiled payload. Examples use collection Bundles for readability; implementers may use transaction Bundles. Do not treat a Composition Bundle as an MPD profile.
| MPD profile (IG name) | FHIR resource | Xt-EHR logical model | What the IG maps | What it is not |
|---|---|---|---|---|
| MedicationRequestEuMpd | MedicationRequest | EHDSMedicationPrescription | A medicinal-product prescription issued by a health professional for a patient | Not NLLMedicationRequest, not a hospital medication-administration record |
| MedicationDispenseEuMpd | MedicationDispense | EHDSMedicationDispense | A pharmacy (including online) dispense to a natural person | Not a ward administration event |
| MedicationEuMpd | Medication | EHDSMedication | Medicinal product as MPD/EU Base profiles it | Not unconstrained R4 Medication |
| DosageEuMpd | Dosage | EHDSDosage | Structured dosage on the request or dispense | Not a narrative-only sig |
Primary sources: HL7 Europe MPD 1.0.0 and the Commission EHDS regulation page (category 1 primary use: Patient Summaries and ePrescriptions/eDispensations from March 2029). The IG’s own scope repeats the EHDS restrictions: medicinal product, health professional, patient, pharmacy dispense, natural person.
The identifier: prescription / prescribed-item ID
Country-agnostic identifier on MedicationRequestEuMpd is MedicationRequest.identifier — the IG labels it prescription / prescribed item ID. Producer obligation is SHALL able-to-populate. Multi-item prescriptions share groupIdentifier. Dispense points back through MedicationDispense.authorizingPrescription to that request. Subject is Patient (EU core), not a Swedish personnummer slice and not a US member id.
National medication lists stay national. Swedish NLL is a live FHIR R4 API with NLLMedicationRequest and personnummer. Map NLL to MPD only when the contract says so.
MyHealth@EU (eHDSI) is the federated NCPeH network for cross-border Patient Summary and eP/eD services. I do not operate it. Live MyHealth@EU eP/eD in many member states is still CDA through OpenNCP; MPD is the FHIR preview the 2027 implementing acts may bind. Connecting an EHR to MPD profiles is not “going live on MyHealth@EU”.
What to implement first
- If the buyer is an EHR or pharmacy system selling into EHDS category 1: package
hl7.fhir.eu.mpd#1.0.0, MedicationRequestEuMpd + MedicationDispenseEuMpd + DosageEuMpd, identifier as above, EU Core Patient as subject. - If the buyer names a national medication API (NLL, a French or German e-prescription service): implement that IG first. Do not relabel it as MPD.
- If the buyer wants cross-border dispense: that path is the member-state NCPeH on MyHealth@EU, plus whatever CDA or FHIR payload that NCPeH currently accepts. It is not a REST call you host.
- Keep category 2 (lab, imaging, discharge — March 2031) off this backlog. The EU Core page already splits those IGs.
What this is not
This article is not an EHDS conformity assessment, not a MyHealth@EU connection, not an NCPeH, not a pharmacy licence, and not legal advice. Implementing MPD profiles in a lab does not make a product “category 1 ready” for March 2029; the 2027 implementing acts can still name different artefacts. I do not operate MyHealth@EU or NLL. Nothing here is clinical or prescribing advice.
Related reading
For mapping MPD onto existing hospital or pharmacy interfaces, use digital health interoperability or start a project.