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

Concept Translation

Concept Translation

What This Page Covers

Some fields need coded value translation, not only structural copying. Those translations are explicit and local to the mapping runtime.

The service uses ConceptMaps where a route needs code translation or normalization. It does not perform open-ended terminology inference.

ICPC-1-NL To SNOMED CT

When a clinical Coding uses ICPC-1-NL, the runtime can translate it to SNOMED CT.

Recognized ICPC systems include:

ICPC system form	Canonical
URL	http://hl7.org/fhir/sid/icpc-1-nl
OID URN	urn:oid:2.16.840.1.113883.6.98

The ConceptMap canonical is:

• http://terminologie.nictiz.nl/ns/ConceptMap/icpc1nl-snomed

The repository includes a local fragment for published examples. Broader coverage can use NTS when configured in the runtime environment.

Other Local ConceptMaps

The repository also carries ConceptMaps for route-specific normalization.

Area	Purpose
Patient	contact relationship and language coding normalization
Problem	verification-status translation to R4 and nl-core
PZP QuestionnaireResponse extraction	answer booleans, treatment choices, observation methods, medical policy goals, contact-point use, UZI specialty, default codings
General display normalization	normalize coded displays where target validation expects a specific form

ConceptMaps live under:

• src/main/resources/mappings/conceptmaps

Local terminology fragments live under:

• src/main/resources/terminology

How To Read Translation Results

Code translation may appear in the translationReport as:

Report group	Meaning
mapped	coding copied without semantic code change
changed	coding translated, normalized, or recoded
added	target coding added by target profile or map rule
deleted	source coding intentionally not represented

The report is a review artifact. Target conformance is checked by R4 validation.

Boundary

The service does not guess a code mapping when no ConceptMap route exists.

Missing terminology coverage should remain visible as a mapping or validation issue, not be hidden in controller logic.