Implementation timeline

  1. 2025
    26 MarchIn force

    Regulation (EU) 2025/327 entered into force. No obligations applied yet.

  2. 2027
    26 MarchRegulation applies

    General application begins: patient rights over their health data, national digital health authorities, and EU governance structures.

  3. 2029
    26 MarchStructured data duties begin

    The first priority categories must be exchangeable in the European format: patient summaries, electronic prescriptions and electronic dispensations. Secondary-use obligations also begin, served through national health data access bodies.

  4. 2031
    26 MarchRemaining priority categories

    Medical imaging studies and related reports, medical test results including laboratory results, and discharge reports join the requirement.

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.

01

The standard path

The hospital prepares the requested extract and hands it to the national health data access body. This national organisation assesses the request and serves the extract to the approved applicant in a secure environment.

02

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 solves.

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 process 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 costs 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 in active development.

  1. 01

    Exchange format

    The European exchange format (EEHRxF) is standard-neutral by design, and its specifications remain in development through 26 March 2027.

    FHIR R4 is the working target across the industry, and it is not yet a mandated standard. Amorphous delivers FHIR R4 and OMOP CDM today and tracks the specification as it evolves, so the mapping updates when the format does.

  2. 02

    Secure environment rules

    The implementing act defining technical requirements for secure processing environments, under Article 73(5), has not been published. Those requirements apply from 2029.

    The regulation itself already states the structural requirements: named-individual access, confined modification rights, isolation between permits. The technical detail follows in the implementing act.

  3. 03

    Data quality label

    Article 78 introduces a data quality and utility label for datasets. Its implementing act is not yet adopted.

    The expected dimensions are completeness, uniqueness, accuracy, validity, timeliness and consistency. Data that is structured and accuracy-measured from the start positions you well for whatever final shape the label takes.

None of this changes the core obligation: describe what you hold and be able to serve it, structured and coded. Waiting for the final specifications only shortens your runway to 2029.

Key terms