yeah, but you are fixing everything else, because this is an
alternative that would be chosen as a whole (if defining code is
local::at0003 and value is 2 then dv_coded_text.value should also be
fixed to whatever value is decided)
2012/4/4 Thomas Beale <thomas.beale at oceaninformatics.com>:
> On 04/04/2012 13:29, Diego Bosc? wrote:
>
> Yes, but what I mean is this
>
> DV_ORDINAL [at0006] matches {
> value matches {|2|}
> symbol matches {
> DV_CODED_TEXT matches {
> value matches {???????????????????????} --
> value is obligatory and I don't know what to put there
> defining_code matches {[local::at0003]} --
> +++
> }
> }
>
>
> Diego,
>
> the value field is obligatory in the data, not in the archetype. You don't
> have to constrain every RM element in an archetype, only what makes sense.
>
> - thomas
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
