ToC+Clinical+Information+Model+WG+Meeting+10-6-2011

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

ToC CIM Vocab WG Meeting Minutes

 * Date:** 10-6-2011
 * Time:** 1:00-2:00pm EDT
 * Dial-in:** 1-408-600-3600 | **Passcode:** 660 213 377

Attendance
Robin Barnes, Nagesh Bashyam, Thompson Boyd, Susan Campbell, Lori Harrington, Emma Jones, Les Keeper, Anne Kling, Laura Heermann Langford, Meredith Lewis, Adrienne Pugh, Russell Leftwich, Holly Miller, Ashley Swain, Cyndalynn Tilley

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 10-6-2011 || The Harmonization team will connect with Bob Dolin to schedule discussion around the process for harmonizing code sets || Harmonization Team || Open ||  ||
 * 2 || 9-29-2011 || Continue development of the BCD data element sets || Volunteers || Open ||  ||
 * 3 || 10-6-2011 || Review the [|BC Data Element PowerPoint] and provide comments & revisions on [|discussion page] || Volunteers || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Review Classification of Data Elements (WG Leads)
 * 3) Review of BC Data elements (WG Leads)
 * 4) Next Steps (WG Leads, Meredith Lewis)

Meeting Notes

 * Data Element Overview
 * The WG's priority is to clarify the classification of the various priority levels from A,B,C.
 * The definitions and examples will continued to be revised.
 * "Goals" has been clarified by Laura Langford and the next step is identify specific data elements and populate the definitions, examples and guidance etc.
 * WG members can refer to the original TOC CIM Version 1.5 as a reference for how to build out the various B & C data elements from the data objects.
 * The WG has affirmed that the "Goals" section will be spearheaded by Laura Heermann and will be completed before the November time frame.
 * Susan Campbell has volunteered to support Laura's group.
 * B/C Data Element Review
 * Dev reviewed a presentation that contained the B/C data element groups, and supporting data elements, that were assigned to the Harmonization Team. The presentation is available on the BCD data elements wiki page, under works in progress.
 * To accomplish this task, Dev reviewed the Consolidated CDA sections that mapped to the data element groups identified in the previous phases of the work.
 * This required looking at the XML code and populating based on the technical capabilities of the Consolidated CDA.
 * In previous phases, WG members populated the data elements based on clinical requirements, not the technical requirements of the CDA.
 * In reviewing Admitting and Discharge Diagnoses, Laura Hermaan questioned the use of LOINC as the specific vocabulary used.
 * Susan Campbell pointed out that this is a CDA-specific vocabulary selection and tends to be faster to process than SNOMED.
 * The point was raised that Consolidated CDA leverages several different types of codesets including LOINC and SNOMED.
 * Some of the data elements may need to be segmented further depending on what is required and optional from a clinical perspective – this is at the discretion of the WG members.
 * Bob Yencha noted that conformance rules dictate what codes are used, which will indicate the preference.
 * Holly suggested that if we are moving towards interoperability, it would make sense to have a discussion regarding the codes.
 * Harmonization Team is taking the action of reaching out to Bob Dolin to get more information on the process for harmonizing codesets.
 * Amy Berk mentioned that the FACA Committee has been looking at identifying those minimal datasets including SNOMED and LOINC and also indicated that presentations are available on this [|website].
 * From a practical standpoint, the vendors on the call mentioned that they are using different codes. For example, Cyndalynn Tilley (GE Healthcare) is mapping ICD-9 and ICD-10 to LOINC and SNOMED CT and Emma Jones (All Scripts) is using MU as guidance for codes.
 * The discussion in the WG this afternoon was focused on the coded aspects of CDA, need to focus on the clinician perspective going forward. For example, the data elements that are currently populated for the Equipment Data Element Group are based on the coded aspects of CDA, not what is clinically necessary.


 * Next Steps**
 * Continue adherence to Roadmap and build out of B,C Data Elements

Next Meeting

 * Date:** 10-13-2011
 * Time:**1:00-2:00pm EDT

Reference Materials

 * 1) TOC Clinical Information Model
 * 2) TOC BCD Data Element Roadmap
 * 3) TOC Classification of Data Elements

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