Hi all! When creating multilingual templates with templated value sets (ie value sets for text elements where the values are included in the template and not the archetype), it seems like there’s a limitation that prevents us from providing those value sets in more than one language. I seem to reme…

I’m pretty sure it is a limitation of ADL1.4. I might be interesting to see if it is actually supported in AD native json which is heavily based on ADL2 (which should solve the issue, at least for local template-level text terms, which I think could just be handled as internal codes. @joostholslag @…

In ADL 2 there is no such limitation - the terminologies for every part of a template can be defined n as many languages as desired, for all node names, value sets and values.

It’s great if this will be solved in ADL2+, and that transition isn’t too far off anymore. But can we work around this in the shorter term?

The only workaround I can think of is to use FHIR Valuesets, which can can carry translations. The real blocker is the ADL1.4 .opt format which simply does not have a way of carrying atcoded items introduced at template level.

This problem about multilingual templated value sets is again rearing its ugly head at us, and it’s likely we’ll get more and more of it in the coming months and years. I’m sure this is an issue also for others operating in a multilingual environment, such as Wales, Luxembourg, Catalonia or Switzerl…

We just did a test on this which worked very well. Both names and value sets are defined in the ontology for each language. When we changed the terms in the OPT the translated values was present in our Form solution. There should be tooling support for such translations. But with some handiwork it…

[image] bna: We just did a test on this which worked very well. Both names and value sets are defined in the ontology for each language. Yep! The translation section looks like this in the OPT exported from Archetype Designer: <term_definitions language="nn"> ... <items code="654576457"> …

Could the items element have a language attribute, i.e., <items language="zh-CN"> ?

The term definition is within a group of language specific items. There will be one group for each exported language. You can see this from @siljelb s example above. Where nn is one two official languages in Norway

Thanks, @bna . Can such a group have a cardinality of 1…*? I mean for manual editing.

Multilingual templates and templated value sets

Specifications

linforest (Forest) 26 September 2024 07:54 13

Thanks, @siljelb.

Such normalization would help reduce the size of the group.

AD support for multilingual editing of templated value sets

Topic		Replies	Views
AD support for multilingual editing of templated value sets Archetype Designer	7	164	11 October 2024
Limitation preventing multilingual repeated parts in the OPT (operational template) export format Archetype Designer	2	1221	26 April 2023
Translations lost in OPT when an archetype is used multiple times Formats opt , template , translation	2	66	24 September 2026
Support of multilingual annotations Archetype Designer template	19	368	27 January 2025
Bug in export of ORDINAL texts defined in templates Archetype Designer	3	919	5 April 2023
Layman's translations Clinical	17	1755	30 January 2021
Alignment of languages and translations in templates (was: Invalid language codes in languages codeset) Technical (archive)	4	27	2 April 2014
Bind multiple value sets to an dv_coded_text within a template Archetype Designer	10	953	15 February 2021
Different Languages in Template Designer Template Designer	2	1177	6 April 2020
Templates "Default Language" ADL tools , template	2	104	23 October 2024

Multilingual templates and templated value sets

Related topics