Hi Pablo, The way to produce the ADL that you’ve posted below is with a “Choice” element.
1. Go to the Archetype Editor’s “Definition” tab. 2. Click the [+] button on the left. 3. From the drop-down list, select “New element” and “Choice”. 4. Over on the right of the screen, you will see two buttons, [+] and [-]. Click the [+] button and select “Text”. 5. Repeatedly click the [+] button to add all of the data types that will be permitted in this element. Hope that helps, Peter > On 9 Feb 2017, at 10:52, Pablo Pazos <[email protected]> wrote: > > Hi, > > I'm testing the EHRServer with alternative datatypes for the same > ELEMENT.value. > > I found the only way of doing that in the Archetype Editor is by setting the > node as Any. And there is no way to further constraint the allowed datavalues > in the AE. > > In the Template Designer I can further constraint that by specifying which > specific types can be used, to avoid the possibility of allowing any > datavalue to be there. The problem I found is that after setting the allowed > datavalues, I can't set constraints for them, e.g. if I specify Coded Text, I > can't set the code list. > > Shouldn't the datatype constraints be set also on the AE and the constraints > per allowed datavalue allowed to be set on the AE and TD? > > I've seen some ADLs/OPTs from Brazil with alternatives, and I don't know if > they are using another AE/TD or just setting the constraints by hand. For > example a problem status archetypes has this which I can't reproduce in the > Ocean's AE: > > ELEMENT[at0082] occurrences matches {0..*} matches { -- > Unspecified > value matches { > DV_TEXT matches {*} > DV_BOOLEAN matches { > value matches {True, False} > } > DV_COUNT matches {*} > } > } > > > Thanks! > _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
