LRI+CIM+&+Vocab+WG+Meeting+Minutes+2011-4-19

include component="page" wikiName="siframework" page="LRI Header" =LRI Clinical Information Model/Vocab SWG Meeting Minutes=
 * Date:** 04/19/2011
 * Time:** 10:00AM-11:00AM EDT
 * Dial in:** 1-888-998-2663 **Participant Code:** 2410512#
 * Meeting Agenda: [|LRI CIM & Vocabulary SWG 20110419.pdf]**

Attendance
Jitin Asnaani, Robin Barnes, Nagesh (Dragon) Bashyam, Kathryn Calderone, Freida Hall, Sergei Haramundanis, Cindy Johns, Austin Kreisler, Elonor Lijoi, Andrea Pitkus, Erik Pupo, Tim Reardon, Andriy Selivonenko, John Stinn, Virginia Sturmfels, Jonathan Tadese, Merideth Vida, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 04/20/2011 || Check email to Joyce re: IG Lab Interfacing || Erik Pupo || Open ||  ||
 * 2 || 04/20/2011 || Bring up issue of scope on this week’s Use Case call || Merideth Vida || Open ||  ||
 * 3 || 04/20/2011 || Clarify how ambulatory laboratory results are being distinguished from other laboratory results on this week’s Use Case call || Erik Pupo/Merideth Vida || Open ||  ||
 * 4 || 04/20/2011 || Clarify with Andrea Pitkus whether the CIM scope should be limited to laboratory information systems, not necessarily ambulatory || Erik Pupo || Open ||  ||
 * 5 || 04/20/2011 || Review the current CIM scope and see if it needs more clarity/detail || All || Open ||  ||
 * 6 || 04/20/2011 || Reach out to Glen Moy for the ELINKS specification model || Erik Pupo || Open ||  ||
 * 7 || 04/20/2011 || Ask the CIM team if the color-coding has significance || Erik Pupo || Open ||  ||

Agenda Items

 * 1) SWG Lead
 * 2) Wiki Structure & Next Steps
 * 3) FHIM Lab Presentation

SWG Lead
Cindy Johns from LabCorps is the SWG Lead for CIM/Vocab. She works in a laboratory setting as a medical technologist.

Wiki Structure & Next Steps
A reminder was sent out in the past week which provides an idea of the types of Clinical Information Models used in the reference material section. We do not want to create a new Clinical Information Model, but to reuse and re-leverage the existing CIMs (it would be out of scope for this initiative to create a new CIM). We would like to establish an initial CIM scope statement that is care-centric and limited to ambulatory laboratory systems and laboratory and pathology tests. The current scope statement is a starting point, and the group should ensure there is a developed and agreed-upon scope statement.

Austin Kreisler said that HL7 Version 3 Laboratory Results and Specimen Models are currently absent from the matrix. We also may want to consider IG Lab Interfacing. Under the current CIM scope, ambulatory was mentioned. The way that the scope is written seems to include any laboratory testing performed in a physician’s office, which may or may not be ambulatory. Should we include that in the scope based on the Use Case development, or is that a question for the Use Case group? Merideth Vida responded that the Use Case group has not yet resolved this question, so she will bring it up during this week’s call. When we are defining ambulatory laboratory results, how are we distinguishing these from the rest of laboratory results? Erik Pupo will follow up with Merideth Vida to get an answer and make sure it is clarified on the Use Case call.

The current CIM scope is also limited to laboratory information systems, not necessarily ambulatory. Erik Pupo will discuss a possible re-wording of this with Andrea Pitkus. There was some discussion on whether LOINC and SNOMED should be designated as Vocabulary more so than CIM, as they are not really a laboratory information model, but there are information models behind it. We may also want to include the ELINKS specification model, but we do not yet have access to it. The group should try to reach consensus on the scope over the next seven days.

To support in-scope test review, we have decided to create a structure on the wiki that would look at the most common in-scope tests. It is currently very detailed, so the group should try to focus on the most critical elements (the key and most common tests based on the Use Case) of it to work off of and review. If the list needs to be whittled down, it may not be the SWG’s job to do that. They are all pretty high-volume tests that are included on this list. Maybe we could look at the actual tests on the list and the example LOINC codes that were given and the format that would be required to report those results (narrative, short text, numeric, etc.). We should not necessarily pare down the list because the in-scope test group spent a lot of time making sure we had an appropriate list. Maybe we could look at the tests that are there and the vocabulary variances and see if we need to identify a format to accommodate LOINC codes. We need to have something a pilot ready within the June timeframe. At that point, we will need to know what the most critical vocabulary variances are and have some level of mitigation for each one. We need to make sure we cover several different types of tests to make sure that all the components are present to express what we need to convey in the pilot. A Google spreadsheet will be imbedded on the wiki to support this, and we can prepopulate it with the in-scope test list eight.

FHIM
If individuals are interested in accessing the FHIM Lab materials, there is a link on the front page of the CIM/Vocab SWG wiki to register for an account. Because some of the materials are difficult to find, we have worked with the FHIM team to make some of the more important materials available to us. Unfortunately representation from the FHIM team was unable to attend today’s call, but hopefully we will have more communication with them in the future.

Virtual Round
A request was made that we ask the CIM lab if the color-coding has significance.

Next Meeting

 * Date:** 5/3/2011
 * Time:** 10:00 AM - 11:00 AM EDT
 * Dial in:** 1-866-816-4209 **Passcode:** 3980879#

Reference Materials

 * 1) CIM Scope Statement

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