LRI+Validation+Suite+WG+2011-08-09

include component="page" wikiName="siframework" page="LRI Header" =**LRI Validation Suite Meeting Minutes **= **Time: ** 1:00-2:00 pm EDT
 * Date: ** 8/9/2011

Thompson Boyd, Kathryn Calderone, Gokulkumar Chandran, David Colbert, Robert Dieterle, Joan Duhaime, Cynthia Levy, James McCormack, Cynthia Madison, Anitha Rathinam, Rob Snelick, Dave Shevlin, Sheryl Taylor
 * Attendance **

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.

**Agenda **

 * Discussion on an overall work plan Test
 * Test Flow/Design/Plan for testing EHRs
 * Review CLIA Specification Requirements
 * Next Steps/Q and A

Discussion on an overall work plan test
Rob Snelick led participants through a slide deck describing: >>> (Kathryn Calderone took ownership of this action item. She will contact LRI Vocabulary group member Cindy Johns and will cc: other members. In a subsequent meeting, Robert Snelick mentioned he will also follow up on this request.).
 * Work plan for testing the LIS and EHR systems. The following discussion items were raised during presentation of this topic.
 * Topics in the Laboratory group included:
 * microbiology
 * cytology, and
 * cases in which LOINC codes used in Europe made no sense in the US.
 * **Q:** Although it is difficult to do 137 tests, would it not be good to do all of them?
 * **A:** Practically, we do not have the resources to do all 137, much as we'd like to. Tests can be data-driven. The plan is to have a way to manage the data and to pull together the information.
 * If the test harness can generate all 137 tests, it may be no more burdensome to do them than not.
 * If all the tests are available, then it is up to the certification body to determine which they will use.
 * **Action:** Request that the LRI Vocabulary group generate the test data.
 * **Q:** Are we validating that
 * all the test messages can be received by the EHR, or that
 * the test data within the HL7 v2 message can be received, parsed and validated ?
 * **A:**We will validate that the EHR has properly understood the data within the test message by comparing the displayed EHR data to a LIS-generated juror document.
 * One creative approach is to test using a patient profile that includes multiple tests.
 * A well-constrained implementation guide is an advantage to those implementing and to those seeking to complete implementation.
 * Eventually, certification -- possibly by CLIA -- may be required to be able to send results.
 * Proposed approach for testing the EHR system
 * EHR Validation test flows
 * Questions/Concerns (for testing the EHR)

Test Flow Design/Plan for Testing EHRs

 * Develop Specific Use Case Scenarios
 * Create Test Data
 * Create/Generate Message
 * Verify Message
 * <span style="color: #000000; font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Create Test Validation Artifacts
 * <span style="color: #000000; font-family: Arial,Helvetica,sans-serif; font-size: 12px;">Send Test Message to EHR SUT

Variability among EHR formats will be tough to manage and may be our biggest challenge. Test harness will be available and one can begin adding other aspects and variations to it.

<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Review CLIA Specification Requirements
No questions.

<span style="color: #000000; font-family: 'Arial','sans-serif'; font-size: 13px;">Next Steps/Q&A
Rob Snelick (NIST) and Sheryl Taylor from Booz Allen Hamilton (via NIST contract) will be working on beginning to create the skeleton of a test plan.

Next Meeting
** WebEx link: [|siframework2.webex.com] ** ** Dial-in: 1-408-600-3600 <span class="skype_pnh_print_container" style="background-color: #ffffff; color: #0000ff;"> | Passcode: (see LRI Validation Suite WG page. **
 * Date: Tuesday, 8/16/2011**
 * Time: 2:00 p.m. EDT**

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