# Bind multiple value sets to an dv_coded_text within a template

**Category:** [Archetype Designer](https://discourse.openehr.org/c/archetype-designer/30)
**Created:** 2021-02-15 07:08 UTC
**Views:** 914
**Replies:** 10
**URL:** https://discourse.openehr.org/t/bind-multiple-value-sets-to-an-dv-coded-text-within-a-template/1293

---

## Post #1 by @birger.haarbrandt

Hi there, 

in FHIR it is possible to provide multiple value sets/external codings to an element value:

![image|439x147](upload://ixCM3vq83xp1zuqqVMxgmc9sADt.png) 

 However, in AD Designer it seems the user is limited to choose only one when further contraining a template:

![image|326x500](upload://qM1jIlG1PL9wISTwDw2xIUz9TIg.png)  

What would be the correct way to represent this in templates? Asking for our modellers.

---

## Post #2 by @ian.mcnicoll

In openEHR this would be handled by the defining_code and other mappings. Currently we have a way of constraining the defining_code but not the mappings. I'm not even sure what that would look like in ADL. TheOcean tools would not support that either - @yampeku = what about LinkEhr?

We can define multiple 'bindings' but these are advisory, not formal constraints.

It is a gap, I agree.

---

## Post #3 by @yampeku

Yes, it's supported

![imagen|605x500](upload://4m3jnCHCQTy6jtieJUe0kZ13X48.png) 

In ADL, something like this (assuming you at least put a target)

![imagen|655x270](upload://bRnWHgE2BVUJEYePEPN9QYaLF4j.png)

---

## Post #4 by @birger.haarbrandt

Thanks, I think the most important question is how this would be presented in OET and OPT for now

---

## Post #5 by @yampeku

Not different from any other alternative I assume

---

## Post #6 by @birger.haarbrandt

would you mind show an example?

---

## Post #7 by @yampeku

Same example in OPT

    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                  <rm_attribute_name>mappings</rm_attribute_name>
                  <existence>
                    <lower_included>true</lower_included>
                    <upper_included>true</upper_included>
                    <lower_unbounded>false</lower_unbounded>
                    <upper_unbounded>false</upper_unbounded>
                  </existence>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>TERM_MAPPING</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0008</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>target</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>1</lower>
                        <upper>1</upper>
                      </existence>
                    </attributes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>TERM_MAPPING</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0012</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>target</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>1</lower>
                        <upper>1</upper>
                      </existence>
                    </attributes>
                  </children>
                  <children xsi:type="C_COMPLEX_OBJECT">
                    <rm_type_name>TERM_MAPPING</rm_type_name>
                    <occurrences>
                      <lower_included>true</lower_included>
                      <upper_included>true</upper_included>
                      <lower_unbounded>false</lower_unbounded>
                      <upper_unbounded>false</upper_unbounded>
                      <lower>0</lower>
                      <upper>1</upper>
                    </occurrences>
                    <node_id>at0016</node_id>
                    <attributes xsi:type="C_SINGLE_ATTRIBUTE">
                      <rm_attribute_name>target</rm_attribute_name>
                      <existence>
                        <lower_included>true</lower_included>
                        <upper_included>true</upper_included>
                        <lower_unbounded>false</lower_unbounded>
                        <upper_unbounded>false</upper_unbounded>
                        <lower>1</lower>
                        <upper>1</upper>
                      </existence>
                    </attributes>
                  </children>
                </attributes>

[openEHR-EHR-GENERIC_ENTRY.Medication.v1.opt|attachment](upload://rst4puQKv0iu8DZ3E5CSRHx3AC5.opt) (49.6 KB)

---

## Post #8 by @ian.mcnicoll

Thanks - .oet might be tricky but it should be easy enough to get this into AD native json, which is largely just AOM2

---

## Post #9 by @birger.haarbrandt

Well, does not really help as long as we cannot deploy it into an openEHR CDR and CKM :(

---

## Post #10 by @yampeku

What is the issue? It should be legal OPT (or ADL2)

---

## Post #11 by @birger.haarbrandt

[quote="ian.mcnicoll, post:8, topic:1293"]
AD native json
[/quote]

@yampeku: was referring to this

---


**Canonical:** https://discourse.openehr.org/t/bind-multiple-value-sets-to-an-dv-coded-text-within-a-template/1293
**Original content:** https://discourse.openehr.org/t/bind-multiple-value-sets-to-an-dv-coded-text-within-a-template/1293