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

Translation Matrix

Translation Matrix

How To Read This Matrix

Each row is one supported source profile route.

The service does not infer arbitrary source-to-target conversions based only on resource type. A translation is supported only when the exact source profile and target profile pair exists in the registry.

Current Supported Routes

Concept	STU3 source profile	R4 target profile
Patient	http://nictiz.nl/fhir/StructureDefinition/BgZ-Patient	http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient
Patient	http://nictiz.nl/fhir/StructureDefinition/BgZ-Patient	http://hl7.eu/fhir/base/StructureDefinition/patient-eu-core
Problem	http://nictiz.nl/fhir/StructureDefinition/BgZ-Problem	http://nictiz.nl/fhir/StructureDefinition/nl-core-Problem
Problem	http://nictiz.nl/fhir/StructureDefinition/BgZ-Problem	http://hl7.eu/fhir/base/StructureDefinition/condition-eu-core
Procedure	http://nictiz.nl/fhir/StructureDefinition/BgZ-Procedure	http://nictiz.nl/fhir/StructureDefinition/nl-core-Procedure-event
Procedure	http://nictiz.nl/fhir/StructureDefinition/BgZ-Procedure	http://hl7.eu/fhir/base/StructureDefinition/procedure-eu-core
FunctionalOrMentalStatus	http://nictiz.nl/fhir/StructureDefinition/BgZ-FunctionalOrMentalStatus	http://nictiz.nl/fhir/StructureDefinition/nl-core-FunctionalOrMentalStatus
FunctionalOrMentalStatus	http://nictiz.nl/fhir/StructureDefinition/BgZ-FunctionalOrMentalStatus	http://hl7.eu/fhir/base/StructureDefinition/medicalTestResult-eu-core
Metadata	http://nictiz.nl/fhir/StructureDefinition/BgZ-Metadata	http://hl7.org/fhir/StructureDefinition/Provenance
AllergyIntolerance	http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance	http://nictiz.nl/fhir/StructureDefinition/nl-core-AllergyIntolerance
AllergyIntolerance	http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance	http://hl7.eu/fhir/base/StructureDefinition/allergyIntolerance-eu-core
Encounter	http://nictiz.nl/fhir/StructureDefinition/zib-Encounter	http://nictiz.nl/fhir/StructureDefinition/nl-core-Encounter
CareTeam	http://fhir.nl/fhir/StructureDefinition/nl-core-careteam	http://nictiz.nl/fhir/StructureDefinition/nl-core-CareTeam
Appointment	http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment	http://hl7.org/fhir/StructureDefinition/Appointment
MedicationRequest	http://nictiz.nl/fhir/StructureDefinition/zib-MedicationAgreement	http://hl7.eu/fhir/base/StructureDefinition/medicationRequest-eu-core
MedicationStatement	http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse	http://hl7.eu/fhir/base/StructureDefinition/medicationStatement-eu-core
MedicationDispense	http://nictiz.nl/fhir/StructureDefinition/zib-AdministrationAgreement	http://hl7.org/fhir/StructureDefinition/MedicationDispense

Stable Core And Extended Coverage

The original core scope for the service is:

• Patient
• Problem
• Procedure

The service now supports additional concepts, but the core three remain the most important routes to keep stable and easy to understand.

Why Some Targets Use Base R4

Not every source concept has both an nl-core and an eu-base target in the local package set currently used by the service.

Current examples:

• BgZ-Metadata targets base R4 Provenance
• eAfspraak-Appointment targets base R4 Appointment
• zib-AdministrationAgreement targets base R4 MedicationDispense
• zib-Encounter and nl-core-careteam currently target nl-core only

This is a deliberate contract choice rather than an accidental fallback.

Target Family Reference

If you want the conceptual difference between the target families before reading the route table, see Target Profiles.