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

Structure Maps

Structure Maps

What These Are

These are the concrete translation rules used by the runtime.

Each map is a checked-in .map source file. The runtime loads them directly, so the IG should make them easy to inspect rather than hiding them behind prose.

Route Families

The map files are grouped by route family:

  • bgz2017-to-logical/ for BgZ STU3 source content
  • nlcore2017-to-logical/ for Dutch nl-core source-side reuse routes
  • zib2017-to-logical/ for zib source-side reuse routes
  • logical-to-nlcore/ for logical to Dutch R4 target maps
  • logical-to-eubase/ for logical to European R4 target maps
  • logical-to-r4/ for logical to plain R4 where no profile-specific target is used
  • shared/ for datatype helper rules shared across routes
  • eafspraak2017-to-logical/ for the supported appointment source route

Concrete Map Files

Patient

  • src/main/resources/mappings/structuremaps/bgz2017-to-logical/Bgz2017PatientToLogicalPatient.map
  • src/main/resources/mappings/structuremaps/nlcore2017-to-logical/Nlcore2017PatientToLogicalPatient.map
  • src/main/resources/mappings/structuremaps/zib2017-to-logical/Zib2017PatientToLogicalPatient.map
  • src/main/resources/mappings/structuremaps/logical-to-nlcore/LogicalPatientToNlcorePatient.map
  • src/main/resources/mappings/structuremaps/logical-to-eubase/LogicalPatientToEubasePatient.map

Problem

  • src/main/resources/mappings/structuremaps/bgz2017-to-logical/Bgz2017ProblemToLogicalProblem.map
  • src/main/resources/mappings/structuremaps/nlcore2017-to-logical/Nlcore2017ProblemToLogicalProblem.map
  • src/main/resources/mappings/structuremaps/zib2017-to-logical/Zib2017ProblemToLogicalProblem.map
  • src/main/resources/mappings/structuremaps/logical-to-nlcore/LogicalProblemToNlcoreProblem.map
  • src/main/resources/mappings/structuremaps/logical-to-eubase/LogicalProblemToEubaseCondition.map

Procedure

  • src/main/resources/mappings/structuremaps/bgz2017-to-logical/Bgz2017ProcedureToLogicalProcedure.map
  • src/main/resources/mappings/structuremaps/nlcore2017-to-logical/Nlcore2017ProcedureToLogicalProcedure.map
  • src/main/resources/mappings/structuremaps/zib2017-to-logical/Zib2017ProcedureToLogicalProcedure.map
  • src/main/resources/mappings/structuremaps/logical-to-nlcore/LogicalProcedureToNlcoreProcedureEvent.map
  • src/main/resources/mappings/structuremaps/logical-to-eubase/LogicalProcedureToEubaseProcedure.map

Supporting Maps

Supporting maps are also part of the concrete runtime:

  • src/main/resources/mappings/structuremaps/bgz2017-to-logical/Bgz2017FunctionalOrMentalStatusToLogicalFunctionalOrMentalStatus.map
  • src/main/resources/mappings/structuremaps/nlcore2017-to-logical/Nlcore2017FunctionalOrMentalStatusToLogicalFunctionalOrMentalStatus.map
  • src/main/resources/mappings/structuremaps/zib2017-to-logical/Zib2017FunctionalOrMentalStatusToLogicalFunctionalOrMentalStatus.map
  • src/main/resources/mappings/structuremaps/logical-to-nlcore/LogicalFunctionalOrMentalStatusToNlcoreFunctionalOrMentalStatus.map
  • src/main/resources/mappings/structuremaps/logical-to-eubase/LogicalFunctionalOrMentalStatusToEubaseMedicalTestResult.map
  • src/main/resources/mappings/structuremaps/logical-to-r4/LogicalMetadataToR4Provenance.map
  • src/main/resources/mappings/structuremaps/logical-to-r4/LogicalAppointmentToR4Appointment.map
  • src/main/resources/mappings/structuremaps/logical-to-r4/LogicalMedicationDispenseToR4MedicationDispense.map

How To Read A Map

The maps typically follow the same shape:

  1. identify the source profile family
  2. normalize source semantics into the logical model
  3. select the target family
  4. map the logical fields into the profile-specific R4 resource

That pattern is deliberate. It keeps source semantics, intermediate semantics, and target semantics visible as separate steps.