LRI+Pilots+WG+2011-08-08

include component="page" wikiName="siframework" page="LRI Header" =**LRI Pilots WG Meeting Minutes**=
 * Date:** 8/8/2011
 * Time:** 2:00-3:00 pm EDT

== **Meeting Agenda:** ==
 * Lessons Learned from ELINCS Pilot
 * Review reports from New/Perspective Pilots Workgroup committed members
 * Review new enrollees of Pilot participant
 * Review Community members interested in sponsoring pilot Wiki page
 * Next Steps
 * Q and A

==Attendance== Rob Allen,Dominique Andrews, Tom Boal, David Burgess,Kathryn Calderone, Steven Cason, Gokulkumar Chandran, David Colbert, Robert Coli, David Collins, John Jones, Cynthia Levy, Bob Lutolf, Cynthia Madison, Kishore Metla, Glen Moy, Anitha Rathinam, Scott Robertson, Rob Snelick, Bob Yencha


 * Note:** If you attended this meeting and are not listed above, please contact David Colbert (David.L.Colbert@lmco.com or 443-348-2828) to be added to the list.

== Action Items == LRI Pilots Workgroup. Indicate where you can help. || S&I Framework Members || Open ||  || == Meeting Purpose & Objectives == Monday status meeting for the Lab Results Interface Pilots (LRI Pilots) workgroup. This meeting will focus on Demos and Pilot activities. == Meeting Notes == >>> Despite the amount of time allocated to implement project interfaces, it took longer than anticipated. The time to install and configure the interface engine and mapping internal test codes to LOINC was also greater than expected. Some users lacked the resources to do it quickly. >>> CHCF provided significant support in the form of funding to cover modifying interfaces and to bring users' partners and stakeholders on board. Support also took the form of answering many detailed questions re: the IG.
 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1. || 08/01/2011 || Sign up for LRI Pilots Wiki and
 * 2. || 08/01/2011 || Review LRI Architecture WG Wiki || Workgroup Members || Open ||  ||
 * 3. || 08/01/2011 || Review LRI Implementation Guide WG Wiki || Workgroup Members || Open ||  ||
 * 4. || 08/01/2011 || Review LRI Vocabulary WG Wiki || Workgroup Members || Open ||  ||
 * 5. || 08/01/2011 || Review LRI Strategy and Consensus Statement page || Workgroup Members || Open ||  ||
 * 6. || 08/01/2011 || Post info sheet and email on the LRI Pilots Wiki. || Support Team || Closed || 08/01/2011 ||
 * 7. || 08/08/2011 || Contact the group that considered 100+ tests to determine the test set we will use. (Cindy has been working on this. Our contact in that group is on vacation.) || Cindy Levy || Open ||  ||
 * 8. || 08/08/2011 || Obtain and share a test plan that can be referenced in the coming testing. || Glen Moy || Open ||  ||
 * 9. || 08/08/2011 || Post LRI Pilot Guide on Wiki for review. Reviewers use Discussion tab to comment on DRAFT LRI Pilot Guide. || Rob Snelick; Workgroup Members || Open ||  ||
 * **Lessons Learned from ELINCS Pilot - Glen Moy, California Healthcare Foundation (CHCF)**
 * CHCF has done two sets of pilot implementations that use the ELINCS HL7 R1 specification. Glen shared these lessons learned:
 * **Issue - Scheduling.**One area for improvement is accurately calculating the time involved for each step of the plan.
 * **Support.**
 * The first pilots involved 5 grantees in California. These were large medical groups or community health centers. CHCF gave users approx. 1 year to implement (conclusion of pilots). The entire timeline is longer.
 * 1) Let an RFP for pilot sites.
 * allowed 6-8 weeks for response,
 * 1) Selected pilot sites followed by
 * 4 weeks
 * 1) Pilot implementation
 * 1 year
 * Provided technical assistance, developed testing tool.
 * First round of grantees was provider organizations.
 * Subsequently, CHCF has worked with POs and vendors.
 * Next round will be partnering with laboratories.
 * **Validation**
 * Validated CLIA compliance by ensuring the message is transmitted successfully with no problems and that the lab report is rendered correctly. This often entailed manually observing and/or capturing the screen display on the EHR.
 * Used test plans from clinical laboratory. Perhaps Quest can share some test plans.
 * **Pilot focus**
 * The focus of the pilots was on LOINC versus OIDs, UCUM, and others because of time and resource constraints.
 * Part of pilot organization selection criteria should be to //be a laboratory that has mapped your codes to LOINC//.
 * **Review artifacts from Pilots Workgroup committed members**
 * Reviewed and edited LRI Pilots Guide. Need also criteria for success and test data.
 * Review a core set of representative tests -- the 5-10 most important tests. For example, one firm has a list of the 25 most commonly requested tests.
 * Another group has pared a list of 500+ requested tests to a subset of 137 tests.
 * The number of tests must be manageable, because each test will have a valid and an invalid test case, and also variations. It is important to select a core set of tests that is representative of a sufficiently broad range of tests to be meaningful to the user community.
 * **Next Steps**
 * **Q and A**

== Next Meeting == ** WebEx link: [|siframework2.webex.com] ** ** Dial-in: 1-408-600-3600  | Passcode: (see LRI Pilots WG page. **
 * Date: Monday, 8/15/2011**
 * Time: 2:00 p.m. EDT**

Reference Materials See the Reference Materials section on the LRI Pilots WG page.

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