ToC+Standards+Analysis+Meeting+Minutes+2011-10-12

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

Standards Analysis Meeting Minutes

 * Date:** 10-12-2011
 * Time:** 1:00-2:00pm EDT
 * Dial-in:** 1-408-600-3600 | **Passcode**: 660 231 991

Attendance
Calvin Beebe, Susan Campbell, John Donnelly, Laura Heerman Langford, Meredith Lewis, Zeshan Rajput, Jennifer Sisto, Ashley Swain, Bob Yencha, Lauren Wood

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 10-12-2011 || Make the revisions to the CMI as described below || Harm Team || Open ||  ||
 * 2 || 10-12-2011 || Review the CMI for areas of gaps and concerns with regard to CIM/CDA || Harm Team || Open ||  ||
 * 3 || 10-12-2011 || Continue to review greenCDA approach and engage over the discussion tab || Volunteers || Open ||  ||
 * 4 || 10-12-2011 || Harm team to connect with the CIM/Vocab WG to review the identified CMI DES || Harm Team; || Open ||  ||

Agenda Items

 * 1) Welcome & Announcements (Meredith Lewis)
 * 2) Review Content Module Index Mapping (John Donnelly, Meredith Lewis)
 * 3) Review Path-Forward for greenCDA (John Donnelly, Meredith Lewis)
 * 4) Next Steps (Meredith Lewis, John Donnelly)

Meeting Notes

 * Announcements**
 * This is another reminder that the Harmonization Team created a new wiki page, TOC Path-Foward for GreenCDA, to capture discussion on the role of the Standards Analysis in defining the approach for greenCDA. The page includes a high-level summary of greenCDA, and the role of the Standards Analysis WG,
 * It was noted that today's Standards Analysis WG meeting overlapped with the Data Segmentation WG meeting again and this could pose a future risk moving forward.


 * Content Module Index**
 * The suggestion was made that the CIM Vocab WG review the CMI for any gaps in content and standards.
 * Meredith highlighted that data set names and CIM data elements do not match cleanly.
 * The point was made that if the WG defines a term such as "Chief Complaint" it might not be in the CIM but it could be in the CDA.
 * The WG needs to escalate the terms that are not in CIM but are in CDA.
 * "Pregnancy did not have a mapping to CIM but was brought up due to the Use Case Requirements.
 * It can be communicated in CDA through specific templates for example following under Social History and entering a Pregnancy Observation
 * The CDA IG has supplanted the use of a pregnancy table with a Social History template
 * Moving forward, the WG needs to incorporate a definition of the Section/Element needs surrounding terms such as Pregnancy that are included in CIM/CDA for the intent of validating what is exchanged
 * If there is no way to express a data element in an exchange, then the guidance should include a definition standpoint from an operational use case perspective
 * The key takeaways from C-154 are essentially business names and implementation guidance since the Consolidated CDA has supplanted the data dictionary in terms of references and overall templates
 * The point was made that there was need to define "Hospital Course" to determine if coding is required or a suggestion to the CDA group is need to make another construct
 * //**Overall CMI Edits/(Action Items)**//
 * DES2 should be relabeled "Support Contact"
 * DES1 should be relabeled "Patient Contact Information"
 * "Physical Activity"
 * "Plan of Care" & "Encounters" needed to be recommended as CIM Objects
 * "Complications Section" need to determine how or where this narrative is expressed- Could be a question for CIM/Vocab WG
 * Define a clearer definition for "Hospital Course" from the Use Case and make a recommendation on the CDA/Templates/sections in aggregate form or narrative
 * greenCDA**
 * The approach is initially limited to the scope of identifying "business names" to be applied to shortlisted data elements
 * There is a risk of restructuring the Workgroup due to low attendance and lack of volunteer participation with regards to greenCDA
 * John Donnelly made that point that greenCDA is an implementation option and if the WG wants to promote the implementation, the WG might want to connect with the Reference Implementation WG to make a pilot incorporate greenCDA
 * The point was made that greenCDA transforms can be used to deploy an exchange document "Discharge Summary"
 * The next steps are to choose what data elements need to be in the green version of the "Discharge Summary" and subsequently what business names can be applied to the shortlisted data elements.
 * A risk was highlighted that if the RI team would launch greenCDA, then they would also have to build out the greenCDA transforms themselves
 * A proposal was made to discuss the greenCDA approach further at the F2F

Next Meeting

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

Reference Materials

 * 1) Content Module Index
 * 2) [|greenCDA Presentation]
 * 3) TOC Path-Foward for GreenCDA

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