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

Target Profiles

Target Profiles

Why Target Profiles Matter

The target profile is part of the translation request. Together with sourceProfile, it selects the exact registered route and therefore the translation direction.

The service does not translate "Patient to Patient". It translates a registered source profile to a registered target profile, for example:

• BgZ-Patient -> nl-core-Patient
• BgZ-Patient -> patient-eu-core
• BgZ-Patient -> patient-eu-eps
• BgZ-Patient -> xib-Patient
• ACP-Patient -> ACP-Patient in PZP 2020
• patient-eu-eps -> BgZ-Patient
• nl-core-Patient -> patient-eu-core

Different target families have different profile rules, extensions, slicing, and terminology expectations.

Output Families

Family	Meaning	Examples
nl-core	Dutch R4 output based on installed nl-core 2020 profiles	nl-core-Patient, nl-core-Problem, nl-core-Procedure-event
eu-base	European R4 base/core profile output	patient-eu-core, condition-eu-core, procedure-eu-core
EPS	European Patient Summary resource profiles or document Bundle	patient-eu-eps, condition-obl-eu-eps, bundle-eu-eps
PZP 2020 ACP	Matching R4 ACP target for PZP 2017 ACP input	ACP-Patient, ACP-AdvanceDirective, ACP-TreatmentDirective
XIB	Local draft R4 profile family generated by this project; accepted as source only through explicit xib-to-logical maps	xib-Patient, xib-Problem, xib-AdvanceDirective
base R4	Plain R4 target when no implemented family profile exists	Appointment, MedicationDispense, Provenance

How To Choose

Choose	When
nl-core	the receiver expects Dutch-profile-first output
eu-base	the receiver expects European base/core output
EPS resource profile	the receiver expects a Patient Summary resource profile
EPS document Bundle	the receiver expects a Patient Summary document
PZP 2020 ACP	the source is a supported PZP ACP profile and the receiver expects the matching ACP target
XIB	the receiver expects the local draft XIB target family while preserving the supported logical-model data points
base R4	the route exists but there is no implemented profile-family target

After choosing the family, check Translation Matrix. The exact pair must be listed.

Current Shape By Source Family

Source family	Typical targets
BgZ package-local profiles	nl-core, eu-base, EPS, XIB, or base R4 depending on concept
BgZ exchange dependent Dutch STU3 profiles	nl-core, eu-base, EPS, XIB, or base R4 depending on concept
PZP 2017 ACP profiles	matching PZP 2020 ACP, supported generic parent targets, selected EU Base targets, selected EPS targets, and XIB
PZP 2020 ACP R4 profiles	XIB, matching PZP 2020 ACP, supported generic parent targets, selected EU Base targets, and selected EPS targets
R4 source profiles	Dutch STU3 targets for reverse routes, or supported R4 target families for R4-to-R4 routes
PZP ACP QuestionnaireResponses	extracted PZP 2020 resources in an R4 Bundle

Important Boundaries

• BgZ resources do not target PZP ACP profiles.
• PZP targets are not inferred from generic BgZ semantics.
• PZP ACP-Procedure can target nl-core-Procedure-event, but not EU Base or EPS Procedure in the current public route index because those targets require performed timing and the PZP Procedure profiles keep it optional.
• PZP health-professional Practitioner and PractitionerRole can target EU Base Practitioner and PractitionerRole because those shared logical models validate against the installed EU Base profiles.
• XIB profiles are accepted as source profiles only where explicit xib-to-logical maps and registry routes exist.
• EPS document Bundle support is a Bundle-level contract, not just a row in the single-resource matrix.
• Base R4 targets are explicit route choices, not accidental fallback behavior.

Validation

Validation uses the same target profile selected for translation.

That means:

• nl-core output is validated against the requested nl-core profile
• eu-base output is validated against the requested EU profile
• EPS output is validated against the requested EPS profile or document Bundle profile
• PZP output is validated against the requested PZP 2020 profile
• XIB output is validated against generated local draft XIB profiles when transform-time validation is enabled. Those profiles are independent future-NL profiles: they extend EU Base/Core wherever those parents exist and fit the supported source data, otherwise plain R4. They do not inherit directly from nl-core or PZP; supported NL/PZP data points outside the selected parent are explicit XIB slices or local XIB extension definitions.
• base R4 output is validated against the base R4 StructureDefinition selected by the route