The dates
Regulation (EU) 2025/327 entered into force on 26 March 2025 and applies in stages:
- 26 March 2027 — national digital health authorities and contact points in place, Member States joining MyHealth@EU, and the Commission's technical specifications for the European exchange format published.
- 26 March 2029 — patient summaries, ePrescriptions and eDispensations. EHR systems processing those categories have to comply.
- 26 March 2031 — medical imaging, laboratory results and discharge reports, with the obligations extending to systems already in service.
- 26 March 2035 — the final transitional provisions complete.
The shape of that timeline matters more than any single date. A system chosen in 2026 is the system in service in 2029, so the question is not when the obligation starts but whether what you buy now will meet it without being replaced or rebuilt.
What is actually required
An EHR system has to carry an interoperability component able to exchange personal electronic health data in the European Electronic Health Record exchange Format (EEHRxF).
EEHRxF is not a new standard invented for the occasion. It is assembled from work that already exists — HL7 FHIR implementation guides, including the HL7 Europe ones, alongside IHE profiles — across six priority categories: patient summary, laboratory results, hospital discharge reports, imaging reports, imaging manifests and medical prescriptions.
So the practical consequence is narrow and concrete: health data will have to leave your system as FHIR resources conforming to European profiles. Whatever a system does internally, that is the shape of the exit.
Where Jengu starts from
Jengu holds clinical data as FHIR resources natively. The FHIR resource is the domain model the platform works with, not an export format written over a private one — a lab order, a result, a prescription, an encounter are FHIR resources from the moment they are created, through every step that touches them, to the point they leave.
That is the whole of the claim on this page, and it is worth being precise about what follows from it. European profiles are constraints on resources: a required element, a bound value set, a fixed identifier system. Applying a profile to a resource you already hold is ordinary conformance work. Producing one from a proprietary model is a mapping project, and it is a mapping project that has to be maintained for as long as both models exist.
The difference is not a matter of effort in 2029. It is whether the work is finite.
What we do not claim
- Jengu is not certified against the EHDS conformity requirements. The technical specifications those will be assessed against are due from the Commission in 2027; nobody is certified against them today, and any vendor saying otherwise is describing something else.
- We do not publish the European Patient Summary or ePrescription implementation guides today. They are profile work on resources already in place rather than new plumbing, and they are on the roadmap as such.
- Connecting to MyHealth@EU is national infrastructure, arranged per Member State through its national contact point, not something a platform provides on its own.
Sources
The dates and obligations on this page are drawn from the Commission's own material. Where this page and the Commission disagree, the Commission is right and we want to hear about it.
Talk to us
If you are weighing a system now against obligations that land in 2029, we are happy to go through the detail — including the parts where the honest answer is "not yet".
Write to jengu@jengu.cloud.