European Health Data Space

2029 is closer than a replacement programme

Three dates decide it: 2027, 2029, 2031. A provider has two routes. Replace the record system, or put a conforming layer above it.

  • Dates from the Regulation
  • The overlay route, stated
  • No vendor comparison
2029 is closer than a replacement programme

26 March 2029

patient access and interoperability

Layer, not replacement

a conforming route without migration

Why this became a budget question

Regulation (EU) 2025/327 entered into force on 26 March 2025 and the preparatory period runs to 2027. What changed is who pays. The obligations attach to the provider and to the systems the provider already runs, not to the ministry that negotiated them. A record system installed today is in scope from 2031. The question is no longer whether to act, but whether the action is a replacement programme or a layer.

What applies, and from when

Per obligation. The dates are the Regulation's, not ours.

26 March 2025
Entry into force. Preparatory period begins. No obligation attaches to a provider yet.In force
26 March 2027
Member States designate authorities. The Commission sets requirements for healthcare ICT systems through secondary legislation.In force
26 March 2029: primary use
Patient access and interoperability apply to essential patient data, electronic prescriptions and dispensations, and to the EHR systems holding them.In force
26 March 2029: secondary use
Chapter IV: data permits, the national catalogue, opt-out, statistical requests, through Health Data Access Bodies.In force
26 March 2031
Imaging, test results and discharge reports. Chapter III applies to systems already deployed before this date. Sensitive categories enter secondary use.In force
26 March 2035
Third countries with adequate standards may join HealthData@EU.In force
What a provider is accountable for
Patient access to the listed categories, interoperability of the systems holding them, and the record of who accessed what.In force
What a provider is not accountable for
The permit process itself, which sits with the Health Data Access Body.In force

Replacement or a layer

What each route has to deliver. Two routes, never named vendors.

RequirementReplace the record systemAdd a conforming layer above it
Patient access to the listed dataDelivered by the new systemDelivered by the layer, read through HL7 FHIR R4
Interoperability of the holding systemDelivered by the new systemDepends on what the existing system exposes
Structured export of the listed categoriesNativeMapped and written back as FHIR resources
Audit of accessNativeImmutable, exportable trail in the layer
Clinical risk during transitionMigration of live clinical dataNo migration; the record does not move
Time to first compliance stepProcurement plus implementation cycleA pilot without deep integration
Cost carrierCapital programmeOperating cost per practice or site
What stays with your existing systemNothingThe clinical record, under national health-record law
Status keyIn forceIn progressReadiness

In force: applies today and can be evidenced. In progress: under way and dated. Readiness: the position is prepared and the market opens next.

What a provider asks first

Is our hospital in scope?

If you hold essential patient data, prescriptions or dispensations, yes, from 26 March 2029. If you hold imaging, results or discharge reports, from 26 March 2031, including on a system deployed today.

Do we have to replace our information system?
What if our system exposes nothing?
Who enforces it?
What should we do in 2026?

Find out where you stand

The assessment names the categories you hold, what your system exposes, and the obligations you cannot meet today. A working document, not a proposal.

See what an overlay covers

Monthly briefing

The signal, once a month.

What changed in European health data, what we shipped, and what it means for a provider. Nothing else.

One email a month. One click to leave.