LRI+Vocabulary+WG+Meeting+Minutes+01-24-2012

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

Vocab WG Meeting Minutes
**Meeting: ** Tuesday 10:00AM-11:00AM EDT **WebEx: ** siframework2.webex.com **Dial-In:** 408-600-3600 **Passcode: ** 662 503 811

**Meeting Agenda:**

 * = **ID** ||= **Key Discussion Items** ||= **Duration** ||= **Presenter** ||
 * = 1 ||= Review Draft LOINC code storage statement ||= 30 Minutes ||= Cindy Johns ||
 * = 2 ||= Update on IG workgroup review of remaining HL7 tables for Pilots WG ||= 30 Minutes ||= Riki Merrick ||

Pam Banning, Ernest Grove, Freida Hall, Cindy Johns, Cynthia Levy, Natalie Menser, Riki Merrick, Rob Snelick, Virginia Sturnfels, Shalina Wadhwani
 * Attendance: **

Action Items

 * **#** || **Action** || **Owner** || **Status** || **Due Date** ||
 * 1 || Change agenda for IG Analysis WG Call on 01-24-2012 to include review of HL7 tables 100, 193, 701, 301 || Natalie Menser || Pending ||  ||

Meeting Notes

 * Will look at LOINC code storage statement
 * Even though Rob Snelick had some reservations regarding a conformance statement on the storage of LOINC in EHR, ome wanted to include a statement in the IG including a statement of why LOINC statements should be stored
 * Cindy Johns wrote a statement, with Riki Merrick and Virginia Johns providing edits

Section 4.2 LOINC
 * “LOINC Statement**
 * LRI Vocab WG Draft Proposal for EHR Storage of LOINC Codes**

The use of the Logical Observation Identifiers Names and Codes (LOINC) vocabulary is required. The LOINC terms transmitted by the sender in OBX.3 must be valid but it is not the intent of this guide to specify LOINC terms/codes for a given test.

While data storage requirements in the EHR will not be addressed in this guide, it is recommended that LOINC terms/codes be stored in the EHR for the following reasons:
 * 1) If the result is related to a reportable condition and the laboratory provides a LOINC code, Meaningful Use stage 1 requires the EHR to send the LOINC code to public healt
 * 2) If the LOINC code is the only code sent to the lab in OBX.3, then the EHR must store and retain that code as part of the CLIA report of records
 * 3) LOINC codes may be used for secondary data exchange purposes and other partner exchange agreements

Further information on LOINC and access to tools, please visit [|http://loinc.org]”


 * Add “or accessible by” after “LOINC terms/codes to be stored in” and before “the EHR for the following reasons”
 * Is LOINC codes an appropriate term?
 * Riki Merrick – LOINC concept may be an alternative, but LOINC uses “LOINC codes” in their own documentation
 * Terms indicates more written language
 * Cindy Johns – change “terms” to codes”
 * Natalie Menser – the original use case for LRI says second use of data is out of scope. Can this be reconciled with the third statement, which states that “LOINC codes may be used for secondary data exchange purposes:
 * Riki Merrick – this statement just shows why it’s a good idea to store the LOINC or have access to it
 * Cindy Johns – secondary data exchange is out of scope of the IG, but this points out another reason why should be include a LOINC conformance statement
 * Motion to accept the proposal as worded (Comment 936)
 * Frieda Hall moves; 0 against, 0 abstain, 5 for
 * Comment will now be sent to the IG WG for review


 * HL7 Tables**
 * Tables 100, 193, 701, 301 need to be reviewed by the IG group
 * Riki Merrick – tables were not reviewed last Thursday, so we have to put them on the agenda today
 * Last week Bob Yencha was going to reach out to Bob Dolin on body sites
 * Once analysis comes back from the IG WG, it will be sent to the Pilots for review, then posted to the Wiki
 * No more Vocab calls after this week

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