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

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

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

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 12-9-2011 || Provide an example of table/visual of data guidance || Erik Pupo || Open ||  ||
 * 2 || 12-16-2011 || Provide comments to the visual example provided by Erik || Volunteers || Open ||  ||

Agenda Items

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

Meeting Notes

 * Using the Consolidated CDA as a starting point, the SWG needs to define the constraints for care transitions, and work into underlying standards. If the SWG is too inclusive, then the guidance could be viewed as optional.
 * In order to maximize interoperability from the particular use cases and the delay of MU Stage 2 and final-rule-making, the SWG needs to determine at what level does the legislation define implementation cases and what tasks can be identified within a care transition.
 * There is a risk that an NPRM decision could impact our underlying standards. For example, the actual regulation of CDC ethnicity codes could be placed into a bucket of various levels but there would be a difficulty with the ballot process.
 * Moving forward it will be crucial for SWG to provide clear distinction between specific exchange scenario versus a care transition, and also a reference to a host of documents that could be available for support.
 * The SWG's overall aim is to develop reasonable implementation guidance by providing a clear definition of what a care transition is.
 * The question was raised if there should be guidelines around introducing other document types outside of the four care transition documents defined in the Transitions of Care Initiative, as well as requirements that could be the supporting basis for defining the constraints. Moreover, outside of harmonization what else can the SWG determine on what implementers need to know?
 * There is a underlying focus in ONC to validate the best practices and outline relevant implementation advice.
 * An action item for the SWG is to create a list of functional examples and select one to start with as an example. In other words, provide a sample/annotative example and the first iteration of what it might look like would and a graphic visual of what example guidance should look like.
 * Vital Signs could be a great starting point to determine a set of data elements that are particularly transmitted.
 * It includes 5-6 places and require a short list in terms of MU stage 1
 * Additionally on a side note, all other 'A' data elements can serve as a the paradigm examples to provide implementers with the best examples to follow
 * This approach is essentially picking one data element group and prototyping it and building a example for implementers.
 * Erik will send an example of a section to start with, and the group will reviewing during the next WG meeting.

Next Meeting

 * Date:** 12-16-2011
 * Time:** 3:00-4:00pm EDT

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