Datatypes R2 Issue 73

Introduction

for true traceability of what the constraint rules in force at the time data is instatiated, we need the value set ID. In addition, this is needed to properly support OTH.

? backward compatible to a limited degree.

Discussion

 type ConceptDescriptor alias CD specializes ANY {
           ST         code;
           ST         displayName;
           UID        codeSystem;
           ST         codeSystemName;
           ST         codeSystemVersion;
           ED         originalText;
           OID        valueSet;
           DATE       valueSetVersion;
           LIST<CR>   qualifier;
           SET<CD>    translation;
           BL         equal(ANY x);
           BL         implies(CD x);
  demotion  ED;
 };
 

Note that there is a problem with the relationship between OTH and multiple valueset specifications with templates that needs resolution with OTH

Motion: add OID valueSet and DATE valueSetVersion to CD, and to note the problem with multiple valuesets and OTH for resolution with the OTH/conformance problems

Disposition

Motion in INM 2 May 2007: We approve the addition to valueSet : OID and valueSetVersion : Date to CD, CE, and CV. If a CD has nullFlavor OTH, then either codeSystem or valueSet must be populated.

What is "DATE"? I disagree to this addition of valueSet OID, it's too complicated. Gschadow 21:55, 2 June 2007 (CDT)

Status

Approved

Links

Back to Data Types R2 issues