A string, a code, it does not matter. As long as both the string or the code are derived from a controlled normative list.
Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 On 29-jun-2006, at 16:01, Thomas Beale wrote: > This lifecycle state at the moment is defined as a string value > within Resource_description (so it can have translations). This is > probably the wrong model, and I would advocate a coded feature in > Authored_resource itself (in the same way as there is a coded > feature in the Version class). [For those wondering why such a > model was chosen in the first place, I believe it was to mimic > either CEN knowledge meta-data or HL7 template semantics]. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060629/ba25176a/attachment.html>
