The EHDS, explained
The European Health Data Space is an EU regulation that took effect in March 2025. It gives patients rights over their electronic health data and requires healthcare providers to make defined categories of that data available in a structured, interoperable form. The obligations arrive in stages between 2027 and 2031.
Implementation timeline
- 26 March 2025In force
- 26 March 2027Regulation applies
- 26 March 2029Structured data duties begin
- 26 March 2031Remaining priority categories
What the EHDS requires of healthcare providers
Priority data in a common format
Six categories of health data must be available in structured, interoperable electronic form.
Registered, described datasets
Health data holders must tell their national health data access body what data they hold and keep the descriptions current.
Serving authorised requests
When a health data access body issues a permit, the holder must make the data available within a fixed deadline.
Concrete enforcement
The regulation carries penalties for holders that do not cooperate.
How hospitals provide data
Every hospital is a health data holder under the regulation. The status is automatic, and the duty is the same for everyone: describe what you hold, and provide it when a permit is approved. What differs is how you provide it.
The standard path
The hospital prepares the requested extract and hands it to the national health data access body, which serves it to the approved applicant in a secure environment.
The trusted data holder path
Member states can designate hospitals as trusted health data holders under Article 72. A trusted holder assesses access applications itself and provides the data inside its own secure processing environment, so the data stays under its roof and control is retained.
Both paths stand on the same foundation: data that is described, structured, coded and of measured quality.
Building that foundation is the slow part that Amorphous can solve for you.
Infrastructure is the first step
Hospitals across Europe are investing heavily in data infrastructure: warehouses, secure environments, federated platforms. Far fewer have a plan for the data inside, which mostly sits in free text, unmeasured and unanalysable.
Structuring changes the arithmetic. A single discharge summary yields hundreds of coded, queryable data points that no system could see before. Across an archive, that multiplies what a hospital can analyse many times over. It is the estate the EHDS assumes you have, and it is what makes an institution more efficient, protects its revenue, and attracts research partners.
Readiness as a by-product
The EHDS places its obligations on hospitals. Our Data Engine converts your free text into structured, coded data and exports it in FHIR R4 and OMOP CDM. It runs continuously, so the data stays ready. The result is what the regulation requires you to be able to serve. The same structured data supports any research collaboration you choose to enter on your own terms.
Whichever path your member state offers, the work is the same. We are the layer that makes your repository's data high quality, interoperable and analysable: structured from free text, coded to standard ontologies, accuracy measured against clinician review. Your infrastructure becomes more valuable, because the data inside it finally holds what the documents always said.
Unified Data
Your existing archive, structured and coded once.
Existing Reasons
- Measure the performance of your services
- Plan capacity and cost from real figures
EHDS Readiness
- Datasets you can register and maintain current
- Permitted requests served within the deadline
Still in draft
Parts of the EHDS are not final, and it is worth knowing which ones.
- 01
Exchange format is not settled
The European exchange format (EEHRxF) is standard-neutral by design, and its specifications remain in development through 26 March 2027.
- 02
Secure environment rules are pending
The implementing act defining technical requirements for secure processing environments, under Article 73(5), has not been published. Those requirements apply from 2029.
- 03
Quality label is in development
Article 78 introduces a data quality and utility label for datasets. Its implementing act is not yet adopted.
None of this changes the core duty: describe what you hold and be able to serve it, structured and coded. Waiting for the final specifications only shortens your runway to 2029.