MnM Minutes CC 20140319
M&M Conference Call 4:00PM Eastern Time (Date above)
Attendees
Paul Knapp, Dale Nelson, Woody Beeler, Rob Hausam, Andy Stechishin, Lloyd McKenzie
Agenda
- Approve Minutes Prior Meeting on February 26
- Approve Minutes Prior Meeting on arch 5
- Consider Resolution of Hot Topic: NullFlavor_on_II
Approve Agenda, Minutes Prior Meeting on March 5 and Minutes Prior Meeting on February 26
Motion: McKenzie/Stechishin 4-0-1
Resolution of Hot Topic: NullFlavor_on_II
Consider resolution on Hot Topic posed by Paul Knapp, and linked above. Knapp outlined the issue and noted that detailed thread in e-mail had ead to the motion he wished to pursue. The motion is based on the conclusion that the Schematron rules in the current schema are more "tight" than the intent of the underlying data types specification and that this is true for both R1 and R2.
Motion: Given that the Schematron constraint expressed in the data types schemas on II are improperly overly constrained, propose to change the Schematron rule to allow both a "root" and a "nullFlavor". This should be undertaken as a technical correction. This can be implemented as a Technical Correction to the schemas for data types R1, R2, and R2b, as well as the ISO data types for R2 (if they include the Schematron). Knapp/McKenzie - Unanimous
Practical steps: Once "OKed" by CTO or TSC, Beeler will edit the HL7 schemas to correct these, and will seek to update the current "source of truth" for the ISO schemas, if they include it. Will wish to make change for May 2014 ballot and note it in the ballot introduction, and in Normative Edition 2014.
Related Questions
What about other data types issues? (Nelson) - e.g. PQ with units="KG" but value "NI". Is this legitimate? And, if so, where do we describe it?
Answer: It is allowed, but there is no general guidance on these. Have a similar issue in null flavor on associations where you might know a bunch of things, but not all. There has been specific guidance in selected circumstances, like II.
Suggest that there should be a "white paper" that summarizes how to deal with these issues. Knapp suggests that ITS should/could pursue this.
