Thank you Ian, you are right, null_flavour tag is not needed.
But in the previous post I proposed also an other change: in the original
ADL code
ELEMENT[at0033] occurrences matches {0..1} matches { -- Comment
value matches {
DV_TEXT matches {*}
}
}
value doesn't have the existence attribute specified.
Being the default for existence attribute {1..1}, a DV_TEXT value tag is
required! But when we have an empty Comment, we cannot have a DV_TEXT value
tag, so we can neither have the whole ELEMENT structure, and so we cannot
specificy a null_flavour!
To be able to do this, this extension would be needed:
ELEMENT[at0033] occurrences matches {0..1} matches { -- Comment
value existence matches {0..1} matches {
DV_TEXT matches {*}
}
}
regards
leo
Ian McNicoll-3 wrote:
>
> Hi Leo,
>
> No it works the other way round. All of the null flavours are
> automatically
> available unless you specifically constrain them out.
>
> Ian
>
> Dr Ian McNicoll
> office / fax +44(0)141 560 4657
> mobile +44 (0)775 209 7859
> skype ianmcnicoll
> ian.mcnicoll at oceaninformatics.com
> ian at mcmi.co.uk
>
> Clinical Analyst Ocean Informatics openEHR Archetype Editorial Group
> Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health
> Scotland
>
>
--
View this message in context:
http://old.nabble.com/Empty-string-for-DV_TEXT-tp28993527p29024820.html
Sent from the openehr-technical mailing list archive at Nabble.com.
