LRI+IG+Analysis+WG+Meeting+2012-02-21

include component="page" wikiName="siframework" page="LRI Header"

LRI IG Analysis Meeting Minutes
__ **Tuesday 02/21 3:00PM ET-5:00PM ET** __
 * WebEx: siframework2.webex.com **
 * Dial-In: 1-408-600-3600 **
 * WebEx Access Code: **** 660 860 390 **

**Meeting Agenda:**
[|LRI DateTime Patterns 2012-02-16.doc] ||= 10 Minutes ||= Hans Buitendijk ||
 * = **ID** ||= **Key Discussion Items** ||= **Duration** ||= **Presenter** ||
 * = 1 ||= Review of Order Parent/Observation Parent/OBX Point Matrix ||= 10 Minutes ||= Hans Buitendijk ||
 * = 2 ||= Final Review and Motion on Date/Time Pattern Analysis
 * = 3 ||= Ballot Reconciliation via the Project Management Wiki Page,beginning with Comment # References ||= 100 Minutes ||= Hans Buitendijk ||

Hans Buitendijk, David Burgess, Austin Kreisler, Brian Pech, Virginia Sturmfels, Shalina Wadhwani
 * Meeting Attendance: **

Action Items

 * **#** || **Action** || **Owner** || **Status** || **Due Date** ||
 * 1 || Final Follow-up on Constrained Value Sets for Comment #961 || Hans Buitendijk || Open ||  ||
 * 2 || Change Status of Comment #599 to "Closed" || Shalina Wadhwani || Open ||  ||
 * 3 || Review Ballot Spreadsheet for Comment # References || Hans Buitendijk || Open ||  ||

Meeting Notes

 * Announcements: **
 * Notice of intent to ballot went out yesterday (02/20)
 * In 30 days we will have 2.7.1 and the Implementation Guide out to ballot
 * Edits in Chapter 4 and 7 to V2.7.1 need to be made
 * The 2.5.1 IG needs a review for which items still need a vote, and will be accepted into OO before submission


 * Discussion of Order Parent/Observation Parent/OBX Point Matrix **
 * In the definition, the order parent and the observation parent do not have their own fields
 * It gets confusing when each category has its own order and fill number
 * A new proposal was created by Austin Kreisler making adjustments
 * Thursday, during the OO call, it will be discussed from an approval perspective
 * Austin Kreisler – the core problem is the asserting that ORC.8 needs to have the same usage as OBR.29
 * These are both the parent fields, and carry the parent identifier
 * The standard itself acknowledge they are different fields (different item numbers) but the language for the two is the same
 * This change request allows parent-child linking for both orders and results
 * Hans – can you change from an optionality “O” to an optionality “C?”
 * Austin – yes, as long as you don’t constrain


 * Final Review of Date/Time Pattern Analysis**
 * The group does not have quorum to vote, so we will make a motion next week


 * Ballot Reconciliation**
 * Hans will go through the latest reconciliation of the spreadsheet to see which items should still be closed in the “Miscellaneous” column
 * No. 961
 * Hans has touched base with Ted on OIDS
 * Tables are code systems but are not necessarily value sets because people can constrain them
 * All of the conditions that we have involve HL7 tables
 * Any OIDS that exist for tables will be replaced
 * Ted’s recommendation was that we use a mnemonic
 * If there is a constrained value set, we should properly identify them
 * Hans is still trying to get an answer on since they are constrained value sets and not code systems, why does V2 refer to a code system
 * Next meeting will make a final call on Comment 961 regarding the constrained value set
 * No. 599
 * Will change to closed – Austin already provided input
 * Add Length to agenda for next week

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"