EU Health Data API
1.0.0-ballot - ballot 150

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

Cross-Border Exchange via NCP

Overview

Cross-border exchange routes through National Contact Points (NCPs) over the MyHealth@EU network (Art. 23(2)). When a patient from Country A receives care in Country B, Country B's NCP requests the patient's data from Country A's NCP, which then queries national infrastructure to retrieve it.

This IG defines the Interoperability Component API surface used at the final step — how national infrastructure (or the NCP itself) queries EHR systems for the patient's data.

Scope

NCP-to-NCP exchange over MyHealth@EU is governed by the NCPeH API specification, not by this IG. National infrastructure design — how a Member State routes an NCP query to the holding EHR systems — is a Member State choice (see Cross-Organization via National Infrastructure).

Participants

Architecture

Country B facility → NCP-B → MyHealth@EU → NCP-A → National infrastructure →  EHR system
                       └──── NCPeH API ────┘        └──── MS choice ────┘     └ This IG ┘

All layers exchange EEHRxF-formatted data.

Authorization

Cross-border patient consent, health-professional authentication in the requesting country, and authorization at the NCP and national-infrastructure layers are governed by MyHealth@EU and Member State infrastructure — not by this IG. At the Interoperability Component API surface, the consumer is an authorized national-infrastructure component; how that authorization was established is out of scope here.