I ran into something while reviewing a template and I’d like to check whether my understanding is correct. Our template uses the same archetype several times in different roles, e.g. CLUSTER.medication.v2 appears 12 times, renamed per slot to different names to cover different parts of our use case. In the exported OPT (and web template) from Archetype Designer this survives only for the template’s original language. Looking at the file: the primary language names are inlined as on each C_ARCHETYPE_ROOT in , so they can differ per instance; all other languages sit in / , and there is exactly one block per archetype, no per-instance dimension in the schema at all. So in our case the 12 English names are preserved, while German gets a single value per at-code: every one of those 12 clusters ends up with the same name, defined by the first instance of the archetype in the OPT. Questions: Is this a known and accepted limitation of the OPT 1.4 format, or is it something tooling could handle differently? For those running multilingual systems: Do you work with actual multilingual OPTs? If yes, what do you choose as primary language? Is there a recommended practice? I’m starting to lose hope of using multilingual templates without dozens of workarounds. Tagging translation group organizers, in case you are interested: @heidi.koikkalainen @ciprian

For my understanding, this is a known limitation of the current ADL1.4/ .oet position. In ADL2 those slot parent renames generate specialised nodes which are carried in the ontology section just like any other node. However ADL1.4 does not have any mens of specialising nodes inside templates, so the ‘rename’ is carried in the node name/value , but not backed by an atCode in the ontology. Example here of a slot fill parent rename Urinary catheter The Better AD does actually create these specialised atCodes internally (in native.json format) but these are dropped in the .opt generation. I think the different names should be retained for the primary language of the .opt but not in the ontology. So if the primary opt language is German, you should see the different node names in German but you will not see the English equivalents in the ontology. This is one of the key drivers for getting over to ADL2 and .opt2.

Translations lost in OPT when an archetype is used multiple times

Implementation Formats

erik.sundvall (Erik Sundvall) 24 September 2026 14:25 3

Topic		Replies	Views
Limitation preventing multilingual repeated parts in the OPT (operational template) export format Archetype Designer	2	1246	26 April 2023
Multilingual templates and templated value sets Specifications template	16	785	27 January 2026
Alignment of languages and translations in templates (was: Invalid language codes in languages codeset) Technical (archive)	4	41	2 April 2014
Exporting from Ocean Template Designer with multiple languages Technical (archive)	0	20	15 December 2016
Support of multilingual annotations Archetype Designer template	19	393	27 January 2025
AD support for multilingual editing of templated value sets Archetype Designer	7	190	11 October 2024
Bug in export of ORDINAL texts defined in templates Archetype Designer	3	934	5 April 2023
Flattened archetype is lacking terminology and language bindings REQUESTS	21	987	30 July 2021
Unique paths for nodes in multiple instances of one archetype in the same OPT Technical (archive)	10	74	13 July 2018
Templates "Default Language" ADL tools , template	2	113	23 October 2024

Translations lost in OPT when an archetype is used multiple times

Related topics