EU Health Data API
0.1.0 - ci-build
150
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
This section defines the API requirements for EHR systems that provide imaging study manifests (references to DICOM imaging studies).
For detailed content profiles, see the EU Imaging Study Manifest IG.
Imaging Manifests can be accessed via document exchange.
| Actor | Description | CapabilityStatement |
|---|---|---|
| Document Consumer | Retrieves imaging manifests | EEHRxF Document Consumer |
| Document Access Provider | Serves imaging manifests | EEHRxF Document Responder |
For document-based access, use the Document Exchange transactions.
The Imaging Manifest is differentiated via the following DocumentReference fields:
18748-4 (Diagnostic imaging Study) — the LOINC code used for document searchMedical-Imaging (EHDS Priority Category) is an informative classification; see Document Search Strategy.The EURIDICE MADO profile defines both a FHIR encoding and a DICOM KOS encoding for imaging manifests. When a system supports both representations, it publishes two DocumentReference resources linked via relatesTo:
| DocumentReference | contentType |
type (LOINC) |
Content |
|---|---|---|---|
| FHIR Manifest | application/fhir+json |
18748-4 | FHIR ImagingStudy manifest |
| DICOM KOS | application/dicom |
18748-4 | DICOM Key Object Selection |
The two DocumentReferences are linked using relatesTo.code = transforms — each is a different technical representation of the same imaging study manifest. Document Consumers query by type and select the representation they can consume based on contentType.
This pattern was chosen (#50) because it works across all Document Sharing transports (MHD, XDS, XCA) without requiring content negotiation at the server.
See Example: Imaging Study Manifest — FHIR and Example: Imaging Study Manifest — DICOM KOS for instances showing the dual pattern.
Search for all imaging manifests (both representations):
GET [base]/DocumentReference?patient.identifier=http://example.org/national-id|123456789&type=http://loinc.org|18748-4&status=current
Search for imaging reports:
GET [base]/DocumentReference?patient.identifier=http://example.org/national-id|123456789&type=http://loinc.org|85430-7&status=current
Note: Both imaging reports and imaging manifests use the
Medical-Imagingpriority category. Usetypeto distinguish them:85430-7for reports,18748-4for manifests.
DICOM image access is in scope for EHDS and is covered by the EURIDICE MADO profile. The imaging manifest (discovered via MHD) describes which studies and series are available; the actual image retrieval uses IHE RAD transactions (WADO-RS, etc.) defined within MADO and outside the scope of this IG.