# AD shows wrong value set in Swedish

**URL:** <https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323>\
**Category:** Tool Support\
**Created:** [23 September 2026 09:50 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323 "2026-09-23T09:50:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pernilla.olsson1](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/p/c4cdca/32.png) [@pernilla.olsson1](https://discourse.openehr.org/u/pernilla.olsson1)\
**Post date:** [23 September 2026 09:50 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/1 "2026-09-23T09:50:57Z")

</div>

We have a template that contains multiple instances of the same archetype (`EVALUATION.recommendation`). The different instances are used to document different types of treatment decisions made during a multidisciplinary team (MDT) meeting.

In the template, we have configured an externally coded value set for each instance of the Recommendation archetype. Each instance should have its own value set, containing different values depending on the type of treatment decision being documented.

Everything appears to work correctly when viewing the template in **English**. Each instance displays the externally coded value set that we configured for that specific instance.

However, when we switch to the **Swedish translation** in Archetype Designer and look at the resulting form in the **Forms** tab, the value sets do not appear as expected. Instead, it seems that the values configured for the **first instance** of the Recommendation archetype are repeated for the subsequent instances as well.

In other words, the template contains different externally coded value sets for the different instances, and these are displayed correctly in English. The problem only appears when viewing the Swedish translation, where the form seems to use the translated value set from the first instance for all instances.

We have encountered a somewhat similar issue with the names of the archetype instances. Since all instances are still based on `EVALUATION.recommendation`, we added an annotation (`L10n.sv`) to each instance in the template, containing the Swedish translation we want to use for that particular instance. This prevents all instances from being displayed with the same Swedish name as the first instance.

Do we need to do something similar for the externally coded value sets to ensure that each instance has its own Swedish translation? If so, we are not aware of how this should be configured.

Could this be a bug in how Archetype Designer handles translations when multiple instances of the same archetype have different externally coded value sets? Or is there a specific translation or localisation configuration that we are missing?

We have not encountered this issue in our previous work with templates and translations, so we are also wondering why it occurs in this particular case and whether there is something specific that could trigger this behaviour.

---

<div class="post-metadata">

**Author:** ![pernilla.olsson1](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/p/c4cdca/32.png) [@pernilla.olsson1](https://discourse.openehr.org/u/pernilla.olsson1)\
**Post date:** [23 September 2026 09:51 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/2 "2026-09-23T09:51:48Z")

</div>

Can it be related to [Limitation preventing multilingual repeated parts in the OPT (operational template) export format](https://discourse.openehr.org/t/limitation-preventing-multilingual-repeated-parts-in-the-opt-operational-template-export-format/2760 "https://discourse.openehr.org/t/limitation-preventing-multilingual-repeated-parts-in-the-opt-operational-template-export-format/2760") ?

---

<div class="post-metadata">

**Author:** ![siljelb](https://discourse.openehr.org/user_avatar/discourse.openehr.org/siljelb/32/12_2.png) [@siljelb](https://discourse.openehr.org/u/siljelb)\
**Post date:** [23 September 2026 12:07 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/3 "2026-09-23T12:07:54Z")

</div>

I think it may be related to that earlier post, yes. @emmanuel.eschmann just explained this issue to me the other day, so maybe he could explain it further here as well?

---

<div class="post-metadata">

**Author:** ![emmanuel.eschmann](https://discourse.openehr.org/user_avatar/discourse.openehr.org/emmanuel.eschmann/32/3339_2.png) [@emmanuel.eschmann](https://discourse.openehr.org/u/emmanuel.eschmann)\
**Post date:** [24 September 2026 13:08 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/4 "2026-09-24T13:08:35Z")

</div>

I have no experience with the Forms tab in the Archetype Designer, but this problem may well have the same root cause as the behaviour we observed in the opt and Web templates generated from multilingual templates:

If we used an archetype multiple times within a template, the DE and FR translations in the opt and Web templates (when EN was selected as the primary language) would only reflect the node name, description and comment of an archetype’s first occurrence in the template for each other instance of the same archetype. The specific node names, descriptions and comments for subsequent occurrences of the same archetype were simply missing entirely from the opt and Web templates.

We described our problem in [Translations lost in OPT when an archetype is used multiple times](https://discourse.openehr.org/t/translations-lost-in-opt-when-an-archetype-is-used-multiple-times/17167) and Ian McNicoll answered that this problem stems from the definition of ADL1.4 and the opt, and that it would only be resolved by ADL2 and opt2.

@Silje, thank you very much for pointing out this thread and, in doing so, highlighting the workaround using the annotation ‘L10n’. I was not aware of this until now.

---

<div class="post-metadata">

**Author:** ![erik.sundvall](https://discourse.openehr.org/user_avatar/discourse.openehr.org/erik.sundvall/32/1961_2.png) [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Post date:** [28 September 2026 10:14 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/5 "2026-09-28T10:14:20Z")

</div>

Do any of the commonly used CDR platforms support importing more modern template formats than the old OPT XML-formats? E.g. some ADL 2-based format supporting multilingual translationa also for repeated structures. Better, DIPS, EHRBase?

---

<div class="post-metadata">

**Author:** ![emmanuel.eschmann](https://discourse.openehr.org/user_avatar/discourse.openehr.org/emmanuel.eschmann/32/3339_2.png) [@emmanuel.eschmann](https://discourse.openehr.org/u/emmanuel.eschmann)\
**Post date:** [22 October 2026 11:59 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/6 "2026-10-22T11:59:10Z")

</div>

> [@pernilla.olsson1](#):
>
> Do we need to do something similar for the externally coded value sets to ensure that each instance has its own Swedish translation? If so, we are not aware of how this should be configured.

You have to define a code for each of the items in the externally coded value sets anyway. If you make sure that this code is unique across all ValueSets of the archetype that appears multiple times in this template, then the opt will have one translation per language and code and no (further) workaround is necessary.

---

<div class="post-metadata">

**Author:** ![erik.sundvall](https://discourse.openehr.org/user_avatar/discourse.openehr.org/erik.sundvall/32/1961_2.png) [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)\
**Post date:** [23 October 2026 07:14 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/7 "2026-10-23T07:14:04Z")

</div>

@emmanuel.eschmann could you show an example (screenshot or file or link to file) of that in a language of you choise?

---

<div class="post-metadata">

**Author:** ![emmanuel.eschmann](https://discourse.openehr.org/user_avatar/discourse.openehr.org/emmanuel.eschmann/32/3339_2.png) [@emmanuel.eschmann](https://discourse.openehr.org/u/emmanuel.eschmann)\
**Post date:** [26 October 2026 14:55 UTC](https://discourse.openehr.org/t/ad-shows-wrong-value-set-in-swedish/17323/8 "2026-10-26T14:55:41Z")

</div>

[cistec.openehr.translation\_test\_consultation\_report\_excerpt.v1.opt](https://discourse.openehr.org/uploads/short-url/jC3n7nDZrenDth2rQgq7Wxl5gC2.opt) (92.9 KB)

[cistec.openehr.translation\_test\_consultation\_report\_excerpt.v1.zip](https://discourse.openehr.org/uploads/short-url/iKqVg39tFXLMdWvNlcU7qXCKIWq.zip) (96.6 KB)

Here is an example using German and French translations.

I created a template containing three occurrences of openEHR-EHR-EVALUATION.clinical\_synopsis.v1. Each occurrence contains an “External Coded” “Local terms” value set.

Since the item codes are identical in all three value sets (“Item\_1”, “Item\_2”, “Item\_3”), I assigned each value set a unique terminology name: “local\_terms\_letterhead”, “local\_terms\_salutation”, and “local\_terms\_introduction”. Alternatively, I could keep the default name “local\_terms”, but would then need to define unique item codes across all three value sets.

In the OPT, translations are stored under the xml-element “component\_ontologies” for the archetype ID, within the language-specific xml-element “term\_definitions” (e.g. language=“de” or language=“fr”). Each item translation is identified by a code attribute combining the terminology name and item code, e.g.:

```auto
<items code="local_terms_letterhead::Item_1>
   <items id="text">1ère synthèse de l'en-tête</items>
</items>

```

For all translations to be represented correctly, this combination must be unique across all value sets in all occurrences of the same archetype. This is the case in the attached example, where you will find alle 9 translated items (translated into both German and French) for each of the 3 items defined in each of the 3 valuesets. If it is not unique, the OPT contains only the translation for the first occurrence of that combination.
