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/bvdh/jwg-api/ and changes regularly. See the Directory of published versions
Document exchange using IHE MHD (Mobile Health Documents) transactions. This IG inherits MHD transactions as-is, with constraints specific to EEHRxF content.
See Actors and Transactions for detailed actor groupings.
This IG uses the following IHE MHD transactions:
| Transaction | Direction | Description | Scope |
|---|---|---|---|
| ITI-67 | Document Consumer → Document Access Provider | Find Document References | system/DocumentReference.rs |
| ITI-68 | Document Consumer → Document Access Provider | Retrieve Document | See note below |
| ITI-65 | Document Producer → Document Access Provider | Provide Document Bundle | system/DocumentReference.c, system/Binary.c or system/Bundle.c |
ITI-68 Scope Note: The required scope depends on the document format. For non-FHIR documents (PDF), use
system/Binary.r. For FHIR Documents (IPS, laboratory reports as FHIR Bundles), usesystem/Bundle.r. See FHIR Documents vs Binary below.
sequenceDiagram
participant Consumer as Document Consumer
participant Provider as Document Access Provider
rect rgb(255, 248, 240)
Note over Consumer,Provider: Find Document References (MHD ITI-67)
Consumer->>Provider: GET /DocumentReference?patient=...&type=...
Provider-->>Consumer: Bundle of DocumentReferences
end
rect rgb(255, 245, 238)
Note over Consumer,Provider: Retrieve Document (MHD ITI-68)
Consumer->>Provider: GET [attachment.url from DocumentReference]
Provider-->>Consumer: Document content
end
ITI-68 retrieves the document from the URL specified in DocumentReference.content.attachment.url. The URL format depends on the document type:
| Document Format | attachment.url | Content-Type |
|---|---|---|
| PDF and other non-FHIR | /Binary/[id] |
application/pdf, etc. |
| FHIR Document (IPS, etc.) | /Bundle/[id] |
application/fhir+json or application/fhir+xml |
This follows MHD Section 2:3.65.4.1.2.1, which specifies the FHIR Document Publish Option: when the DocumentReference.content.attachment.url points at a FHIR Document Bundle, that Bundle is retrieved directly without Binary encoding.
Implementation Note: FHIR Documents do not require base64 encoding into a Binary resource. The document Bundle is stored and retrieved as a native FHIR Bundle resource.
This IG follows the IHE Document Sharing approach:
The EHDS priority categories are defined by Article 14 of the EHDS Regulation. We define codes specifically for EEHRxF that map directly to these regulatory categories.
See EEHRxFDocumentPriorityCategoryCS for the complete list.
| LOINC Code | Priority Category |
|---|---|
60591-5 |
Patient Summary |
18842-5 |
Hospital Discharge Report |
11502-2 |
Lab Result |
68604-8 |
Diagnostic Imaging Report |
See EEHRxFDocumentTypeVS for the complete list.
The examples below show queries using both category (EHDS priority category) and type (LOINC document type). Either can be used depending on your use case.
By type (LOINC):
GET [base]/DocumentReference?patient=Patient/123&type=http://loinc.org|60591-5&status=current
By category (EHDS priority):
GET [base]/DocumentReference?patient=Patient/123&category=http://hl7.eu/fhir/euridice-api/CodeSystem/eehrxf-document-priority-category-cs|Patient-Summaries&status=current
By type (LOINC):
GET [base]/DocumentReference?patient=Patient/123&type=http://loinc.org|11502-2&status=current
By category (EHDS priority):
GET [base]/DocumentReference?patient=Patient/123&category=http://hl7.eu/fhir/euridice-api/CodeSystem/eehrxf-document-priority-category-cs|Laboratory-Reports&status=current
By type (LOINC - imaging reports only):
GET [base]/DocumentReference?patient=Patient/123&type=http://loinc.org|68604-8&status=current
By category (EHDS priority - includes both reports and manifests):
GET [base]/DocumentReference?patient=Patient/123&category=http://hl7.eu/fhir/euridice-api/CodeSystem/eehrxf-document-priority-category-cs|Medical-Imaging&status=current
Note: The
Medical-Imagingcategory includes both imaging reports and imaging manifests. To distinguish between them, use thetypecode orformatCode. See Imaging Manifest for details.
By type (LOINC):
GET [base]/DocumentReference?patient=Patient/123&type=http://loinc.org|18842-5&status=current
By category (EHDS priority):
GET [base]/DocumentReference?patient=Patient/123&category=http://hl7.eu/fhir/euridice-api/CodeSystem/eehrxf-document-priority-category-cs|Discharge-Reports&status=current
Document Producers publish documents by POSTing a transaction Bundle:
POST [base]
Content-Type: application/fhir+json
The Bundle contains DocumentReference + Binary resources. See IHE MHD ITI-65 for details.
Open Issue #3: We are seeking input on MHD publication transaction options. See MHD Publication Transaction Options for discussion.