LRI+Validation+Suite+WG+2011-12-06

include component="page" wikiName="siframework" page="LRI Header" LRI Validation Suite WG Meeting

LRI Validation Suite WG Meeting December 6, 2011

Housekeeping/Updates CLIA, CAPP, COLA Test messages where there are questions
 * AGENDA**

Mr. Snelick began the meeting by advising the team in regard to a sense of a timeline. This WG has been meeting for a few months now and a lot has been accomplished. The type of messages as well as the scope has been identified. The team has been working on the mechanics behind all of this in building the artifacts and development as a test tool. Soon the team will be seeing a transition into reviewing of the tool and artifacts that will soon be produced. This is currently a rough prototype and based off the IG which is still going through changes.
 * HOUSEKEEPING/UPDATES**

To start the process in reviewing artifacts, test cases and the tool, the plan is to start to conduct demonstrations on December 20, 2011. The version at this point will not be for pilot use as it will continue to be in draft format. The goal is to be able to provide this tool to the pilots a few weeks before HIMSS. The team hopes to have a solid tool a few months after the reconciliation of ballot one has been completed. The IG group is still going through ballet comments. They have received 960 comments and are currently about 1/3 way through those comments.

Cheryl has put a list of all of the LOINC codes together as well as a categorization of those test messages. This list has been pretty solid for some time. A check list for a plan of attack has been put together in regards to which messages the team wants to do and where we were in obtaining those messages and mapping them to the current IG. There is a spreadsheet that will house the data for those messages that will be integrated into the tooling. The goal is to have this document integrated into the tool in two weeks.

Mr. Snelick advised that he delivered what the team thinks the value sets are and is waiting for the vocabulary team to review them so that they also can be integrated into the tool.

Mr. Snelick advised the team that identifying all of the conformance requirements is not a good use of time at this point. It would be best to wait for the next version of the IG as it is not stable enough.

In terms of how to handle the specs, Mr. Snelick states that he has a good idea on how to handle this but needs to formally document the intended process. As the team begins to demonstrate that in the tool and in practice use, there will be availability to refine the process.

Verifying test cases and processes has not been discussed with the team yet. Mr. Snelick advises that this group or another group of experts should review before it is published.

Wiki updates have been made to categorize all of the resource documents so that they can be reviewed and comments can be made. The test plan for EHR will be sent to the Lockheed Martin team so that it can be uploaded to the Wiki site also. Ms. Snelick requested that Tom Boal remove all of the test cases from the approved section as they have not yet received feedback.

Mrs. Sawchuck advised the team that she believes that most of the issues surrounding CLIA have been addressed. She requested to have her spreadsheet outlining the CLIA and other accrediting agencies added to the resource documents on the Wiki. She will first consult with her team to ensure that contact information be removed before providing a final version to be placed on the site. Mrs. Sawchuck further advised that she will continue to review the juror document to ensure that all of the required elements have been captured. Mr. Snelick advised that if there are missing data elements, ballot comments to the IG team would be the best approach in rectifying the situation.
 * CLIA, CAPP, COLA**

Various test messages are listed with time stamps which are required data elements. In previous messages, the team did not have the time stamps listed in a logical order. It is being requested that the team review these time stamps to ensure that the times are listed in a sensible fashion. The team agreed that the times seem to be logical.
 * Test messages and Interpretation**

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