EU Health Data API
1.0.0-ballot - ballot 150

This page is part of the EU Health Data API (v1.0.0-ballot: STU1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Open Issues

Open issues under discussion in this IG. Each has a corresponding GitHub Issue where you can add input to existing issues, or create your own.

We welcome your input via Github Issues, or by attending the weekly HL7 Europe API Workgroup Meetings.

Issue 1: Document Search and Priority Category Differentiation

GitHub Issue Priority: High

How should systems differentiate documents by EHDS Priority Category? Patient Summary, Imaging Results, Medical Test Results, and Hospital Discharge Reports are all FHIR Documents exposed via DocumentReference and MHD.

Current Approach (going to ballot)

DocumentReference .type with LOINC codes is the primary search parameter for document differentiation. The .category element is left unconstrained — servers may populate it, but it is not a required search parameter. A ConceptMap is provided mapping EHDS priority categories to LOINC codes used in .type.

Seeking Input On

  • Is .type with LOINC the right search parameter for priority category differentiation, or should .category or format play a role?
  • Does the ConceptMap approach work for your implementation context?
  • What search patterns do Member States currently use for document discovery?

Issue 9: Core Resource Set Validation

GitHub Issue Priority: Medium

The following resources are proposed as the core set for resource access (e.g. resource search entry points specifically, not all included resources). This needs validation from Priority Category owners.

Shared

  • Patient
  • Practitioner
  • Organization

Patient Summary

  • Condition
  • AllergyIntolerance
  • MedicationRequest
  • MedicationStatement
  • Immunization

ePrescription/eDispensation

  • MedicationRequest
  • MedicationDispense

Medical Test Results

  • Observation
  • DiagnosticReport

Imaging Results

  • DiagnosticReport
  • ImagingStudy

Discharge Reports

  • Encounter

Seeking Input On

  • Is this resource set appropriate for the priority categories?
  • Are any resources missing that should be included?
  • Should Encounter be required?

Issue 12: MADO Dual-Encoding for Imaging Manifests

GitHub Issue Priority: High

Imaging manifests (MADO — Manifest of DICOM Objects) may exist in both FHIR and DICOM formats. This IG specifies a dual-DocumentReference pattern: two DocumentReferences linked via relatesTo with code transforms, one pointing to the FHIR ImagingStudy representation and one to the DICOM KOS object. This enables content negotiation — consumers retrieve the format they support.

This approach was agreed by the API working group. However, alternative approaches have been proposed, including a single-DocumentReference model preferred by some in the DICOM community.

Seeking Input On

  • Does the dual-DocumentReference pattern work for your imaging infrastructure?
  • Would a single-DocumentReference with multiple content entries be preferable?
  • How does your system currently handle FHIR/DICOM content negotiation for imaging manifests?