LRI+Pilots+Face-to-Face

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

Author: Bob Lutolf
Throughout the two days we discussed how various S&I Framework documents included provisions that would hinder Piloting and real world implementations. I assigned myself an action item to develop proposed revised content the workgroup would review and then pass on to the appropriate S&I Framework group. The following are the general concerns. 1.	Some diagrams and text required a Certified LIS and certified EHR. 2.	The message sent by the LIS was required to conform to the Implementation Guide being developed by the S&I Framework. 3.	Application and architectures such as Integration engines, HIEs, EMRs were not allowed between the LIS and the EHR. Jitin addressed these on Wednesday.

I reviewed
1.	The S&I Framework LRI Use Case 2.	The S&I Framework Strategy and Consensus Statement 3.	The S&I Framework LRI Implementation Guide 4.	The S&I Framework LRI Pilots Guide.

My Summary
1.	I found no requirement for a certified LIS. There is a requirement for certified EHR in the Use Case and Implementation Guide. This is appropriate. There was no requirement for a certified EHR in any Pilot. 2.	I found no requirement that the message sent by the LIS conform to the S&I Framework LRI Implementation Guide. This is certainly the intent, for the future. However, the Guide only requires that if you use the Sender Profile, it must conform to the Guide. We also discussed this on today’s HL7 Orders & Observations group call. That is the group sponsoring the S&I LRI Framework Implementation Guide through HL7. The two S&I Framework IG Analysis co-leads are also the HL7 OO workgroup leads. 3.	I found no one explicit statement the said there could be Integration Engines, HIEs or EMRs between the Sender LIS and Receiver EHR. I found no explicit or implicit prohibition to having Integration Engines, HIEs or EMRs between the Lab Sender and the EHR Receiver. The Use Case mentions HIEs as a Community of Interest. The Use Case also includes “enable consistent, appropriate, and accurate information exchange across provider systems, data repositories and locator services.”

So if anyone thinks that there are problems, I need specific instances that I can address.

The Pilot process starts with a short proposal. Proposals will be reviewed and discussed. This is probably a better place to get any specific concerns addressed.

Homework for F2F

 * Review the LRI Pilots Guide
 * Review the [|LRI IG ( v 0.6 submitted to HL7)]
 * Review the LRI IG Conformance Statements
 * Review the List of In-Scope Lab Tests
 * Review the LRI Strategy and Consensus Statement
 * Review the latest [|Powerpoint presentation]from the LRI Validation Suite Workgroup

October S&I Face-to-Face Meeting
(Attendees Sign-in for F2F Conference Badges ) || Keynote Addresses Full S&I Discussion || ( Attendees Sign-in for F2F Conference Badges ) ||
 * **Tuesday, October 18, 2011 – LRI Pilots (Draft) Agenda** ||  ||
 * 7:00 am to 5:00 pm || Registration
 * 8:00 am to 9:00 am || Opening Ceremonies
 * 9:00 am to 10:10 am || Review Pilot Guide and Schedule ||
 * 10:10 am to 10:15 am || Break ||
 * 10:15 am to 12:00 pm || Review Pilot Guide and Schedule ||
 * 12:00 pm to 1:30 pm || Lunch ||
 * 1:30 pm to 3:00 pm || Discuss/Develop Test Strategy
 * Validation Suite – Rob Snelick
 * LOINC approach ||
 * 3:00 pm to 3:15 pm || Break ||
 * 3:15 pm to 4:45 pm || Discuss/Develop Test Strategy ||
 * **Wednesday, October 19, 2011 – LRI Pilots (Draft) Agenda** ||  ||
 * 7:00 am to 5:00 pm || Registration
 * 7:00 am to 5:00 pm || Registration
 * 9:00 am to 10:00 am || Discussion with Jitin Asnaani ||
 * 10:00 am to 10:15 am || Break ||
 * 10:15 am to 12:00 pm || Ask questions of Implementation Guide Group ||
 * 12:00 pm to 1:30 pm || Lunch ||
 * 1:30 pm to 4:45 pm || Pilot preparation ||

LRI Pilot Teams Ecosystem dashboard is here

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