LOI+Vocabulary+WG+Meeting+Minutes+2012-08-07

**Meeting Agenda:**

 * **ID** || **Key Discussion Items** || **Duration** || **Presenter** ||
 * 1 || Finalize LOI Lab Test Order Codes Statement ([[file:siframework/DRAFT LOI Lab Test Order Code 2012-07-31.doc|DRAFT LOI Lab Test Order Code 2012-07-31.doc]] )
 * Review LOINC Order Codes Discussion Points document to verify all questions have been addressed || 30 Minutes || WG Members ||
 * 2 || Begin review of HL7 tables that correspond to the data elements identified in the LOI Use Case functional requirements spreadsheet
 * Initial review focused on tables pertaining to orders only
 * Follow-up review of tables also in LRI IG that were previously reviewed || 30 Minutes || WG Members ||

Attendance
Bill Ormerod, Bob Yencha, Cindy Johns, Freida Hall, Jonathan Tadese, Lester Keepper, Riki Merrick, Rob Hausam, Shalina Wadhwani, Virginia Sturmfels, Zeshan Rajput

Action Items

 * **#** || **Action** || **Owner** || **Status** || **Due Date** ||
 * 1 || Review LOI Lab Test Order Codes Statement for consensus next week || WG Members ||  ||   ||

Meeting Notes

 * LOI Lab Test Order Codes Statement**
 * Today the group would like to finalize the Lab Test Order Codes Statement
 * The LOINC Order Codes Discussion Points document states that the LOINC Common Order Value Set is not extensive enough to be useful and proposes the idea of enlarging the list in time for MU3
 * The Discussion Points document states “the Universal Service code received on an order may not be the same Universal Service code value returned on a Result transaction generated to fulfill the order service. One example is that an order for a creatinine clearance LOINC code 34555-3, could result in a result transaction containing multiple order observation groups with unique specimen types.”
 * he WG wants to include a statement to incorporate this issue into the draft statement and will send this to the LRI IG Analysis WG; do not need to include the example but more provide it as an umbrella statement
 * Also include recommendation to include verbiage which should be added to published errata for LRI IG
 * Implementers will have to be pointed to both places in the guide and leave it up to the larger group to figure out how to manage this
 * Bill Ormerod will draft a statement that we want to send to the LRI IG Analysis WG and a vote will be taken on the draft statement next week
 * “For some of the tests we need to ask at order entry questions to go along – they are also not addressed in the current list of LOINC order codes”
 * The WG will include a statement on if an AOE question has an appropriate LOINC code we will recommend that they consider using it