Datatypes R2 Issue 51
Data Types Issue 51: CO numeric value
Dan Russler asks for an extension of CO where you could actually have a numeric value as in
<value xsi:type="CO" value="2" code="xyz" codeSystem="..." displayName="eye opening to pain"/>
and then also he wants translations, so CO would have to extend CE rather than CV.
We'd also have to add an operation
to the abstract definition of CO.
Backwards compatibility: this would be backwards compatible
Grahame: This is counter to the whole point of designing CO the way it has been designed. It was deliberately designed this way to avoid the trap of explicitly representing the order in a non-manageable fashion, and delgating the order to the CTS -> invite Dan to contribute.
Back to Data Types R2 issues