Just remembered children of attribute can handle multiple alternatives,
while this is syntactically correct I'm not sure if the alternatives can be
of the same object type:
<attributes xsi:type="C_SINGLE_ATTRIBUTE">
<rm_attribute_name>defining_code</rm_attribute_name>
<existence>
....
</existence>
<children xsi:type="C_CODE_REFERENCE">
<rm_type_name>CODE_PHRASE</rm_type_name>
<occurrences>
....
</occurrences>
<node_id />
*<referenceSetUri>terminology:LOINC</referenceSetUri>*
</children>
<children xsi:type="C_CODE_REFERENCE">
<rm_type_name>CODE_PHRASE</rm_type_name>
<occurrences>
....
</occurrences>
<node_id />
*
<referenceSetUri>terminology:SNOMED-CT</referenceSetUri>*
</children>
</attributes>
On Sat, Sep 15, 2018 at 2:56 PM Pablo Pazos <pablo.pa...@cabolabs.com>
wrote:
> Hi,
>
> I'm having trouble generating OPTs (1.4) from archetypes that reference
> multiple terminologies from a DV_CODED_TEXT.
>
> For instance, I have a coded node that will be coded by LOINC or
> SNOMED-CT, that can be set in the archetype. But when exporting the OPT
> from the Template Designer, only LOINC appears in this way:
>
> <children xsi:type="C_CODE_REFERENCE">
> <rm_type_name>CODE_PHRASE</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>1</lower>
> <upper>1</upper>
> </occurrences>
> <node_id />
> * <referenceSetUri>terminology:LOINC</referenceSetUri>*
> </children>
>
>
> Now, looking at the OPT schema (I think I got it from the TD), it says the
> C_CODE_PHRASE only can have one *referenceSetUri* element, so it is not
> possible to add more elements with other terminologies.
>
> So, how can we put many terminologies on the OPT?
>
> Should that be multiple values in that element? like this:
>
> *<referenceSetUri>terminology:LOINC
> terminology:SNOMED-CT</referenceSetUri>*
>
> (that looks ugly and I don't think is valid)
>
>
> I'm surprised to find this simple case can't be supported by tools or the
> OPT format itself. Any tips are welcome.
>
>
> Best,
> Pablo.
>
> --
> *Ing. Pablo Pazos Gutiérrez*
> pablo.pa...@cabolabs.com
> +598 99 043 145
> skype: cabolabs
> Subscribe to our newsletter <http://eepurl.com/b_w_tj>
> <https://cabolabs.com/>
> http://www.cabolabs.com
> https://cloudehrserver.com
>
>
--
*Ing. Pablo Pazos Gutiérrez*
pablo.pa...@cabolabs.com
+598 99 043 145
skype: cabolabs
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
<https://cabolabs.com/>
http://www.cabolabs.com
https://cloudehrserver.com
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
