EU Health Data API, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 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

Use Case - Cross-Border via NCP

Overview

Health information is exchanged across borders through National Contact Points (NCPs) using the MyHealth@EU network.

How Cross-Border Exchange Works

NCPs communicate with each other via the MyHealth@EU network. When a patient from Country A needs care in Country B:

1. Country B's healthcare facility requests data through their NCP
2. NCPs exchange data over MyHealth@EU
3. Country A's NCP queries national infrastructure to retrieve the patient's data

This IG enables the final step: Country A's national infrastructure (or the NCP itself) acts as a Consumer to query EHR systems that are Providers of patient data.

Actors

• NCP or National Infrastructure acts as Document Consumer
• EHR systems act as Document Access Provider

Architecture

Country B Facility → NCP-B → MyHealth@EU → NCP-A → National Infrastructure → EHR System API
                                                                              ↑
                                                                    This IG defines this API

Role of This Specification

All layers exchange EEHRxF-formatted data to ensure semantic interoperability.

Authorization Context

• Patient consent for cross-border access
• Healthcare professional authentication in requesting country
• Authorization decisions at NCP, national infrastructure, and EHR system levels