EU Health Data API, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/euridice-org/eu-health-data-api/ and changes regularly. See the Directory of published versions

Patient Summary (EPS)

This section defines the API requirements for EHR systems that provide EEHRxF data that conforms to the HL7 Europe Patient Summary content profile.

Actors

The European Patient Summary document can be accessed via document exchange

Document Exchange

For document-based access, use the Document Exchange transactions:

The Patient Summary is differentiated via the following DocumentReference fields:

• type: 60591-5 (Patient summary Document)
• category: Patient-Summaries (EHDS Priority Category)

Example Query

GET /DocumentReference?patient=123&type=http://loinc.org|60591-5&status=current

See Example: Retrieve A European Patient Summary for a complete workflow example

Resource Exchange

For resource-based access, use the Resource Access transactions to query individual clinical resources referenced in the Patient Summary.

On-Demand Patient Summary Assembly

FHIR servers can assemble Patient Summary documents on demand from clinical resources. When supported, the IPS $summary operation returns a Patient Summary Bundle directly:

GET /Patient/[id]/$summary

A server can also expose the same on-demand Patient Summary through MHD. In that pattern, ITI-67 returns an on-demand DocumentReference whose content.attachment.url points to Patient/[id]/$summary. Per MHD on-demand semantics, the DocumentReference omits content.attachment.hash and content.attachment.size.