Cumuluz Translate Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

EPS Coverage

EPS Coverage

Purpose

This page is a compact EPS support note. The route-level source of truth remains Translation Matrix.

Implemented EPS Support

Area	Source support	EPS target
Patient	BgZ BgZ-Patient, PZP ACP-Patient	patient-eu-eps
Problem	BgZ BgZ-Problem	condition-obl-eu-eps
Procedure	BgZ BgZ-Procedure	procedure-eu-eps
AllergyIntolerance	dependent Dutch STU3 zib-AllergyIntolerance	allergyintolerance-obl-eu-eps
MedicationRequest	zib-MedicationAgreement	medicationrequest-obl-eu-eps
MedicationStatement	zib-MedicationUse	MedicationStatement-eu-eps
Advance directives	selected PZP ACP Consent routes	consent-eu-eps
Health professional	selected PZP Practitioner and PractitionerRole routes	practitioner EPS profiles
Device and device use	selected PZP device routes	device EPS profiles
Document Bundle	supported source Bundle entries	bundle-eu-eps and composition-eu-eps

Important Limits

• EPS package availability does not mean a translation route exists.
• Unsupported EPS document entries fail explicitly.
• PZP Practitioner and PractitionerRole EPS routes are available as single-resource transforms, but are not standalone EPS document Bundle entries in the current Composition section set.
• Empty Composition sections do not imply resource support.

Gaps

Other EHDS/EPS package areas, such as organisation, alerts, immunisation, pregnancy, travel history, and laboratory reporting, are not registered routes unless a concrete source profile, logical model, target map, and tests exist.

Add those only when they enter project scope with source examples and target-profile decisions.