CD2 - Revision history

Kheitmann at 17:48, 27 January 2026

2026-01-27T17:48:53Z

Kheitmann at 14:58, 12 August 2024

2024-08-12T14:58:39Z

Kheitmann at 13:57, 6 August 2024

2024-08-06T13:57:41Z

Kheitmann: Created page with "

Code mappings and multilingual support

The capability of managing locally used coded concepts and reference terminologies, and that of providing re..."

2024-08-06T13:39:11Z

Created page with "<h2>Code mappings and multilingual support</h2> The capability of managing locally used coded concepts and reference terminologies, and that of providing re..."

New page

<h2>Code mappings and multilingual support</h2>
The capability of managing locally used coded concepts and reference terminologies, and that of providing receiving providers with human readable information in a language that can be understood by them, are critical aspects to be taken in account in the cross-border sharing of documents. This section summarizes some of the requirements related to these aspects, including also
additional needs derived from the European cross-border services and some lessons learned by the EU/US Trillium Bridge Project.
The European cross-border services (Myhealth@EU), formerly known as eHDSI, use a business to business exchange infrastructure based on a network of country gateways that mediate access to the national infrastructures. The EU Patient Summary (EU PS) is used as a “pivot” document for the cross-border exchange. Local PS using data/document formats are in fact remapped into
the eHDSI PS. The document exchanged is processed each time it passes through one of these gateway applying the needed syntactical transformation, code mappings. and translation of the code designations. Finally, in the current practice the received PSs are displayed using specialized display tools that build a human readable representation of the PS in the target language
using the translated designations reported in the coded entries.
The adoption of translated narratives in the received document has been one of the indications received by the Trillium Bridge Project. This in fact allows extending multilingual support for the cross-border patient summaries to a wider set of potential consumers (EHR-or PHR systems), without requiring specialized viewers as applied in the eHDSI services.
<h3>Concept code mapping</h3>
In several real world use cases the records used as source for the Patient Summaries may use locally adopted terminologies, which are mapped to the reference value sets when possible, or otherwise used directly to provide uncoded information. This leads to a series of requirements listed below and detailed further in section "Design conventions and principles".
<ul>
<li>
When the original coded concept is mapped to one of the coded concepts included in the reference value sets (called hereafter reference code/coded concept), both the original and the reference codes SHALL be reported in the IPS instance.
</li>
<li>
When the original coded concept is not mapped to one of the coded concepts included in the reference value sets, the original code SHALL be reported in the IPS instance as well as the indication that mapping was not successful.
</li>
<li>
When the original record, for a specific coded element, is not able to provide coded but only textual information, this information SHALL be reported in the IPS instance.
</li>
</ul>
This guide also accommodates these situations:
<ul>
<li>
The original record may support multi-coding. The IPS instance should make clear whether the additional codes belong to the original content or are the result of post hoc concept code mapping.
</li>
<li>
The original record may include references to the pieces of text the coding was derived from. If present, the IPS instance should preserve this link between the original code and the referred text.
</li>
<li>
Distinct original and reference coded concepts may belong to the same code system. This may be the result of a different level of granularity between the original and the reference value sets, or the result of format transformation - e.g. CCD document is used as input for generating an IPS. The requirement of recording both coded concepts applies also to these cases.
</li>
</ul>
<h3>Multilingual support</h3>
Multilingual support by IPS can be split in two categories of action:
<ol>
<li>
The translation of coded concept designations (displayName)
</li>
<li>
The translation of the narrative.
</li>
</ol>
These actions may deal with various choices:
<ul>
<li>
Translation to the language of the receiving care provider: a foreign provider retrieves a translated copy of the IPS from the patient's country of affiliation…
</li>
<li>
Translation to a commonly agreed language: an English version of the IPS is prepared.
</li>
<li>
Predefined set of translations included in the shared IPS.
</li>
</ul>
This guide does not favor any of these solutions. All of them are supported.
<h4>Translation of Designations</h4>
The European Cross-border services requires that for “safety and liability reasons” all of the original coded terms (designations, displayName) shall be recorded in the exchanged documents together with at least the English and the receiving country language terms (designations, displayName) associated with the reference codes. The designations translated in the receiving
country language are used to generate the human readable content shown to the receiving provider. No free text translation is applied in this case. In order to accomplish this objective, the IPS should have the capability to record one or more designations, possibly indicating the language used. The solution chosen to fulfill this requirement is specified in section 4.6.
<h4>Narrative Translation</h4>
Narrative translation covers two kinds of operations:
<ul>
<li>
Translation of the original narrative text, which can be automated (e.g. using translation services) and/or human curated.
</li>
<li>
Creation of new narrative for the target language, based on the coded entries.
</li>
</ul>
The level of quality and liability obtained depends on the solution adopted and on the quality of the translation service used. It is out of the scope of this guide to suggest any of these solutions. In all cases, however:
<ul>
<li>
the language of the narrative should be identifiable
</li>
<li>
the original and the translated narrative should be clearly distinguished
</li>
<li>
the translation methodology applied (e.g. derived from the coded entries; translated by a generic service;..) should be noted
</li>
</ul>

@@ Line 1: / Line 1: @@
-<html><h2>Code mappings and multilingual support</h2>
+== Code mappings and multilingual support ==
                  <p>The capability of managing locally used coded concepts and reference terminologies, and that of providing receiving providers with human readable information in a language that can be understood by them, are critical aspects to be taken in account in the cross-border sharing of documents. This section summarizes some of the requirements related to these aspects, including also
                      additional needs derived from the European cross-border services and some lessons learned by the EU/US Trillium Bridge Project.</p>
@@ Line 6: / Line 8: @@
                      using the translated designations reported in the coded entries.</p>
                  <p>The adoption of translated narratives in the received document has been one of the indications received by the Trillium Bridge Project. This in fact allows extending multilingual support for the cross-border patient summaries to a wider set of potential consumers (EHR-or PHR systems), without requiring specialized viewers as applied in the eHDSI services.</p>
-                <h3>Concept code mapping</h3>
+</html>
                  <p>In several real world use cases the records used as source for the Patient Summaries may use locally adopted terminologies, which are mapped to the reference value sets when possible, or otherwise used directly to provide uncoded information. This leads to a series of requirements listed below and detailed further in section "Design conventions and principles".</p>
                  <ul>
@@ Line 25: / Line 29: @@
                      </li>
                  </ul>
-                <h3>Multilingual support</h3>
+</html>
                  <p>Multilingual support by IPS can be split in two categories of action:</p>
                  <ol>
@@ Line 43: / Line 49: @@
                  </ul>
                  <p>This guide does not favor any of these solutions. All of them are supported.</p>
-                <h4>Translation of Designations</h4>
+</html>
                  <p>The European Cross-border services requires that for “safety and liability reasons” all of the original coded terms (designations, displayName) shall be recorded in the exchanged documents together with at least the English and the receiving country language terms (designations, displayName) associated with the reference codes. The designations translated in the receiving
                      country language are used to generate the human readable content shown to the receiving provider. No free text translation is applied in this case. In order to accomplish this objective, the IPS should have the capability to record one or more designations, possibly indicating the language used. The solution chosen to fulfill this requirement is specified in section 4.6.</p>
-                <h4>Narrative Translation</h4>
+</html>
                  <p>Narrative translation covers two kinds of operations:</p>
                  <ul>

@@ Line 9: / Line 9: @@
                  <p>In several real world use cases the records used as source for the Patient Summaries may use locally adopted terminologies, which are mapped to the reference value sets when possible, or otherwise used directly to provide uncoded information. This leads to a series of requirements listed below and detailed further in section "Design conventions and principles".</p>
                  <ul>
-                     <li>
+                     <li>When the original coded concept is mapped to one of the coded concepts included in the reference value sets (called hereafter reference code/coded concept), both the original and the reference codes <strong>SHALL</strong> be reported in the IPS instance.
                      </li>
-                     <li>
+                     <li>When the original coded concept is not mapped to one of the coded concepts included in the reference value sets, the original code <strong>SHALL</strong> be reported in the IPS instance as well as the indication that mapping was not successful.
                      </li>
-                     <li>
+                     <li>When the original record, for a specific coded element, is not able to provide coded but only textual information, this information <strong>SHALL</strong> be reported in the IPS instance.
                      </li>
                  </ul>
                  <p>This guide also accommodates these situations:</p>
                  <ul>
-                     <li>
+                     <li>The original record may support multi-coding. The IPS instance should make clear whether the additional codes belong to the original content or are the result of post hoc concept code mapping.
                      </li>
-                     <li>
+                     <li>The original record may include references to the pieces of text the coding was derived from. If present, the IPS instance should preserve this link between the original code and the referred text.
                      </li>
-                     <li>
+                     <li>Distinct original and reference coded concepts may belong to the same code system. This may be the result of a different level of granularity between the original and the reference value sets, or the result of format transformation - e.g. CCD document is used as input for generating an IPS. The requirement of recording both coded concepts applies also to these cases.
                      </li>
                  </ul>
@@ Line 34: / Line 28: @@
                  <p>Multilingual support by IPS can be split in two categories of action:</p>
                  <ol>
-                     <li>
+                     <li>The translation of coded concept designations (displayName)
                      </li>
-                     <li>
+                     <li>The translation of the narrative.
                      </li>
                  </ol>
                  <p>These actions may deal with various choices:</p>
                  <ul>
-                     <li>
+                     <li>Translation to the language of the receiving care provider: a foreign provider retrieves a translated copy of the IPS from the patient's country of affiliation…
                      </li>
-                     <li>
+                     <li>Translation to a commonly agreed language: an English version of the IPS is prepared.
                      </li>
-                     <li>
+                     <li>Predefined set of translations included in the shared IPS.
                      </li>
                  </ul>
@@ Line 60: / Line 49: @@
                  <p>Narrative translation covers two kinds of operations:</p>
                  <ul>
-                     <li>
+                     <li>Translation of the original narrative text, which can be automated (e.g. using translation services) and/or human curated.
                      </li>
-                     <li>
+                     <li>Creation of new narrative for the target language, based on the coded entries.
                      </li>
                  </ul>
                  <p>The level of quality and liability obtained depends on the solution adopted and on the quality of the translation service used. It is out of the scope of this guide to suggest any of these solutions. In all cases, however:</p>
                  <ul>
-                     <li>
+                     <li>the language of the narrative should be identifiable
                      </li>
-                     <li>
+                     <li>the original and the translated narrative should be clearly distinguished
                      </li>
-                     <li>
+                     <li>the translation methodology applied (e.g. derived from the coded entries; translated by a generic service;..) should be noted
                      </li>
                  </ul>
 </html>

@@ Line 1: / Line 1: @@
-<h2>Code mappings and multilingual support</h2>
+<html><h2>Code mappings and multilingual support</h2>
                  <p>The capability of managing locally used coded concepts and reference terminologies, and that of providing receiving providers with human readable information in a language that can be understood by them, are critical aspects to be taken in account in the cross-border sharing of documents. This section summarizes some of the requirements related to these aspects, including also
                      additional needs derived from the European cross-border services and some lessons learned by the EU/US Trillium Bridge Project.</p>
@@ Line 79: / Line 79: @@
                      </li>
                  </ul>