Cumuluz Translate Implementation Guide
0.1.0 - ci-build

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

EHDS / EPS Coverage

EHDS / EPS Coverage

This page tracks the EHDS/EPS model surface against the mappings implemented in this repository. It separates installed package support, source coverage, logical models, and registered translation routes.

Status Meanings

  • Implemented: registered source-to-target route exists and is StructureMap-backed.
  • Candidate: source and logical model exist, but the EPS target map is not implemented.
  • Partial source: a related reference or embedded value exists, but not enough for a standalone EHDS resource route.
  • Not in scope: no current BgZ 2017 or PZP 2017 source route is present.

The installed EPS package is validation context only until a route is registered and backed by source-to-logical and logical-to-EPS StructureMaps. PZP ACP sources also have explicit generic parent targets where they validate against installed nl-core or base R4 parent profiles; those parent routes are separate from EPS support.

Current Implemented EPS Routes

EHDS/EPS area BgZ / Dutch STU3 source PZP source Logical model EPS target Status
EHDSPatient BgZ-Patient ACP-Patient LogicalPatient patient-eu-eps Implemented for BgZ and PZP Patient
EHDSCondition BgZ-Problem - LogicalProblem condition-obl-eu-eps Implemented for BgZ
EHDSProcedure BgZ-Procedure - LogicalProcedure procedure-eu-eps Implemented for BgZ
EHDSAllergyIntolerance zib-AllergyIntolerance - LogicalAllergyIntolerance allergyintolerance-obl-eu-eps Implemented for the BgZ dependent source profile
EHDSMedicationUse zib-MedicationUse - LogicalMedicationStatement MedicationStatement-eu-eps Implemented for medication-use statements
Medication request obligation zib-MedicationAgreement - LogicalMedicationRequest medicationrequest-obl-eu-eps Implemented although not named as a separate EHDS model in the user-facing list
EHDSHealthProfessional - ACP-HealthProfessional-Practitioner, ACP-HealthProfessional-PractitionerRole LogicalPractitioner, LogicalPractitionerRole practitioner-obl-eu-eps, practitionerrole-obl-eu-eps Implemented for PZP source profiles
EHDSDevice - ACP-MedicalDevice.Product-ICD LogicalDevice device-eu-eps Implemented for the PZP source profile
EHDSDeviceUse - ACP-MedicalDevice LogicalDeviceUseStatement deviceUseStatement-eu-eps Implemented for the PZP source profile
EHDSAdvanceDirective - ACP-AdvanceDirective, ACP-TreatmentDirective LogicalConsent consent-eu-eps Implemented for PZP source profiles
EPS document Bundle STU3 Bundle entries for the implemented EPS routes Supported PZP entries for patient, directives, device products, and device use Existing route models bundle-eu-eps plus composition-eu-eps Implemented for section- or reference-reachable entries only

EPS document assembly currently creates sections for problems, allergies, medication, advance directives, procedures, and device use where supported entries are present. PZP health-professional EPS routes are available as single-resource transforms, but standalone Practitioner and PractitionerRole entries are not added to EPS document Bundles because the current Composition section set has no health-professional section. Unsupported entries fail explicitly instead of being silently dropped.

Relevant Gaps And Candidate Routes

EHDS model Installed EPS target profile BgZ source relevance PZP source relevance Current project state Needed work
EHDSOrganisation organization-obl-eu-eps Partial organization references may exist No standalone PZP organization route Partial source only Add LogicalOrganization and source maps if a concrete source profile is selected
EHDSAttachment No dedicated installed EPS StructureDefinition; attachments are carried by resource elements Embedded attachments may exist LogicalConsent.sourceAttachment can carry directive attachment content Partial embedded data only Keep embedded unless a concrete attachment route is required
EHDSAlert flag-alert-obl-eu-eps No current BgZ alert source route ACP-InformRelativesRequest is a CommunicationRequest, not an EHDS alert Not in scope Add only if a source alert/flag profile is selected
EHDSImmunisation immunization-obl-eu-eps No current BgZ immunization source route No PZP immunization source route Not in scope Add source logical model and maps if immunization enters project scope
EHDSCurrentPregnancy observation-pregnancy-status-eu-ips No current BgZ pregnancy-status source route No PZP pregnancy source route Not in scope Add only with a selected source concept/profile
EHDSPregnancyHistory observation-pregnancy-outcome-eu-eps, observation-pregnancy-edd-eu-eps, observation-pregnancy-gestationalAge-eu-eps No current BgZ pregnancy-history source route No PZP pregnancy source route Not in scope Add only with source examples and target-profile decisions
EHDSTravelHistory observation-travel-eu-eps No current BgZ travel-history source route No PZP travel-history source route Not in scope Add only with a selected source profile
EHDSObservation No single generic observation EPS profile in the package; specific observation profiles exist BgZ-FunctionalOrMentalStatus maps to LogicalFunctionalOrMentalStatus and EU Base medical test result, not EPS PZP observation choices map to LogicalObservation for PZP 2020 Candidate only after choosing a concrete EPS observation profile Select the exact EPS observation profile before mapping
EHDSCarePlan No dedicated installed EPS CarePlan StructureDefinition in the current package No current BgZ care-plan source route ACP-MedicalPolicyGoal maps to LogicalGoal, not CarePlan Not implemented; PZP goal may be a semantic input candidate Confirm whether EHDS expects CarePlan, Goal, or another resource
EHDSLaboratoryObservation diagnosticReport-eu-eps plus observation/lab-related package content, but no implemented route No current BgZ laboratory observation source route No PZP laboratory source route Not in scope Add only with lab-specific source profiles and examples

Project-Relevant Priority Order

The most relevant remaining mappings are:

  1. PZP observation choices to concrete EPS observation profiles only where the target profile semantics are explicit.
  2. Organisation routes if a concrete source profile and LogicalOrganization model are selected.
  3. Alert, immunisation, pregnancy, travel-history, and laboratory routes only when source profiles and examples enter scope.

For BgZ, the implemented EPS Patient Summary subset is already aligned with the current implemented BgZ source surface. The missing EHDS models mostly require adding new source concepts before target mappings can be correct.

Guardrails

  • Do not infer a source route from a matching FHIR resource type alone.
  • Do not use PZP ACP target mappings as EHDS mappings without reviewing the EHDS profile requirements.
  • Do not treat an empty EPS Composition section as implemented resource support.
  • Keep unsupported EHDS targets visible until the route is registered and tested.