TOC+Implementation+Guidance+SWG+Meeting+Minutes+12-2-2011

include component="page" wikiName="siframework" page="TOC Header" =ToC Implementation Guidance SWG Meeting Minutes=
 * Date:** 12-2-2011
 * Time:** 3:00-4:00pm EDT

Attendance
Emma Jones, Russell Leftwich, Meredith Lewis, Erik Pupo, David Tao, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 12-2-2011 ||  || Volunteers || Open ||   ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Implementation Guidance Discussion (Volunteers)
 * 3) Next Steps

Meeting Notes

 * The purpose of the SWG is to align efforts and reduce redundancies across the Transitions of Care Initiative.
 * The SWG should focus on functionality specific guidance, or usability. In other words, focus on how data elements should be coded and what data elements should be implemented (required vs. optional). This guidance is motivated by the desire to reduce ambiguity on demographics and other language elements.
 * Ultimately, the SWG needs to include a directive on what should be included, and not included, in care transition documentation.
 * Another role of the SWG is to inform ONC of how to properly motivate vendors to adopt our guidelines through clear and concise implementation guidance, as well as align to Meaningful Use. Conformance criteria could be a use measurement to consider.
 * Holly Miller, Russell Leftwich and Bob Yencha are reviewing the constraints outlined in the Consolidated CDA, and recording the gaps. They are considering bringing their recommendations to HL7, in later phases of the work.
 * S&I Framework operates like a "user group arm" that provides practical user guidance to the growing catalog of interoperability challenges.
 * A key question that should be considered and addressed by this group, "what do you reject if you get more information than you need?"
 * Rich Kernan proposed that the SWG create functional examples, or common scenarios, to illustrate key care transition challenges for a specific patient.
 * Need to develop a repeatable mechanism for key aspects that need to be resolved for clinical examples.
 * HITSC, and others, see major implementation barriers to Consolidated CDA. GreenCDA is a tool that makes it easier to implement.
 * Still need to determine how "informal" we need to be in selecting a prototype section to "green."
 * There is a need to ascertain what other constraint levels/variances need to be included in our documentation to convey clinical information.

Next Meeting

 * Date:** 12-9-2011
 * Time:**1:00-2:00pm EDT

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