RI+Validation+Suite+WG+2011-11-22


 * LRI Validation Suite Meeting Minutes**

**Meeting Agenda:**
Next Steps ||  ||
 * **Topic** ||  ||
 * Discuss Validation Suite

Attendance
Robert Allen, Neeli Bajaj, Tom Boal, Joan DuHaime, Freida Hall, Cynthia Levy, James Littlejohn, Scott Robertson, Rob Snelick, Virginia Sturmfels, Scott Robinson, Sheryl Taylor, Megan Sawchuck, Marybeth Gagnon, Bob Coli

Meeting Notes
Mr. Rob Snelick presented the team with the EHR Pre Test. This is a model for the test flow for testing EHR systems. It is known that as the team continues to build, changes would need to be made. A question that needs to be raised prior to beginning is: what does the EHR need to configure and what can they use with this data? Based on the information that EHR provides, a panel will need to be provided so that the providers can modify the information and dynamically modify the test message that will be provided for evaluation. The team should start nailing down what info should be anticipated that the EHR would have to have specific information for.

Mr. Snelick shared with the team with a color coded document representing sample messages. The red highlights represent the questions of what information do we need them to allow configuring so that when we send the message, they will be able to do what they need to do. Another question to consider is looking at building panel now, what are the elements that we need to respond to? Frieda Hall advised the team that most EHR systems will have user defined rules based on constituency. Normally there are some type of matching algorithms that can be set up so that when the results are in with the patient Id, it echoes with the EHR system.

Another question raised by the team is if it typical before the EHR can receive a lab result, would they have to have an order in their system? Megan Sawchuck advised that is typical. Mr. Deiterle advised the team that EHRs can do many of several things. They can go all the way to creating the patient and the record that it ties to It. He continued by advising the team that the vast majority of EHR today will get their results either through a VPN with HL7 transaction or through a soap transaction to push transactions set with an xml wrapper.

Mr. Snelick advised the team that testing will be conducted on all of the required fields that makes sense to test. Question on the OBR 4, observation requests. For all of the test messages, we envision sending a LOINC code that represents the lab results. It is recognized that this is not a requirement in the IG but the EHR should be capable to receiving both triplets here. For a particular, they may specify local code for this request. The use case could be a paper or electronic order to the lab. For all of our test messages, we will send LOINC. Another part of the configuration would be to map to local codes. Is this necessary to be able to consume that message or will they care? Response from the teamYES

The next question is in regards to OBX 3 – Observation results. Here is where we are sending out the results. For the messages that we create we are going to include LOINC code, do we allow them to configure the local lab code here. Miss Johns states that she believes that this will need to be used. Sometimes a LOINC code will not be available. Mr. Snelick advised that he wants to put wrapper around the scope for testing the first scope that states that we will only support the 144 in scope test list. In that case, they will always have a LOINC code so the question is do we need to provide the capability to map to the local code? Response from that team is that it should.

The next question is on unit of measure. It is not a requirement and the pilots will not get to this topic for the next 12-24 month period. This question is in regards to including the UCOM. Question is if the team needs to provide another panel for the UCOM code for what is used locally. I think that the answer is yes but, not sure. Miss. Johns advised that there is a lot of liability with this topic. The team will have to finish conversations on this topic in the next meeting.


 * Next Meeting **
 * Date: **Tuesday, 11/015/2011
 * Time: **1:00 p.m. EDT
 * Dial in: ****WebEx link: **[|**siframework2.webex.com**] **Dial-in: 1-408-600-3600 Passcode: 664 208 0504 **