Bind multiple value sets to an dv_coded_text within a template

Tool Support Archetype Designer
1

Hi there,

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

image

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

image
image472×723 9.97 KB

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

1 Like
2

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.

1 Like
3

Yes, it’s supported

imagen
imagen879×726 28 KB

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

imagen

4

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

5

Not different from any other alternative I assume

6

would you mind show an example?

7

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 (49.6 KB)

8

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

9

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

10

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

11

@yampeku: was referring to this

1 Like