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!
--
Ing. Pablo Pazos Gutiérrez
Cel:(00598) 99 043 145
Skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com
[email protected]
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
