ToC+Full+Initiative+F2F+Meeting+Minutes+2011-06-15

include component="page" wikiName="siframework" page="TOC Header" =ToC Full Initiative F2F Meeting Minutes=
 * Date:** 06-15-2011
 * Time:** 1:30-2:00pm EDT

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 06-15-2011 || Joint call will LRI/TOC and ONC || Bob Yencha || Open ||  ||
 * 2 || 06-15-2011 || Achieve consensus on TOC Architecture IR Scope and goals || Arch/IR RI WG || Open ||  ||
 * 3 || 06-15-2011 || Standard Analysis WG consensus planning || Standard Analysis WG || Open ||  ||
 * 4 || 06-15-2011 || Review D,E classifications || CIM/Vocab WG || Open ||  ||
 * 5 || 06-15-2011 || Documenting transition strategy || CDA Consolidation WG || Open ||  ||
 * 6 || 06-15-2011 || Revise TOC Timeline || Arch/IR and Erik Pupo || Open ||  ||
 * 7 || 06-15-2011 || Create working pilots as showcases for LRI/ToC to display what is in production || TOC and LRI || Open ||  ||
 * 8 || 06-15-2011 || Work backwards from pilot Timeline || Holly Miller and David Tao || Open ||  ||
 * 9 || 06-15-2011 || Start identifying providers and vendors who can assist with the piloting || All || Open ||  ||
 * 10 || 06-15-2011 || Strategy and IR guide should be cemented by standard and rolled out by the end of the comment period (December) || All || Open ||  ||

Agenda Items
>
 * 1) Introductory Comments from Arien Malec
 * 2) WG Updates from Leads
 * 3) Revised Agenda for Afternoon

Meeting Notes
Currently developing a road map for the progression of how the data elements fit together. The following are highlights from the discussion.
 * Care Planning WG**
 * Data Elements A: Elements that must be available for any level of ToC
 * Data Elements B: Elements that are available for selection by the physician
 * Data Elements C: Elements that are desirable but not captured in EHR system
 * There will be a minor rewrite (available on the Wiki on June 16th)
 * Determine B data (which is defined data that is selected by the clinician at the time of creation the ToC document) and C data
 * Care Planning/CIM Vocab WG reviewed the different items that make up a care plan, identified the meta-data that should be included and reached consensus on B & C data elements.
 * In the proposed Meaningful Use (MU) Stage 2, the policy committee care plan specifications will include goals and care plan instructions.


 * CIM/Vocab WG**
 * In addition to looking at the core data elements during the CIM/Vocab meeting, the WG discussed the importance of translating the data elements between clinicians and developers.
 * The WG also discussed the importance of making the clinical data set comprehensible for developers so that the Reference Implementation & Pilots WG can ultimately produce an implementation document.
 * Consensus was achieved for several core data element groups including Demographics, Active Medication List, and Allergies including Intolerances. The WG has requested that further time be allotted for discussion on the Active Problem List.

>
 * WG Collaboration Points**
 * The Reference Implementation & Pilots WG needs participants from the Architecture/Implementation RQ WG to ensure success. Specifically, the WG needs modelers, who have experience with plug-ins other than JAVA.
 * The ToC Initiative needs to be cross-pollinating as much as possible, particularly as ToC gets closer to building the CIM.
 * Next Steps for CIM/Vocab WG**
 * Define the B and C data elements. The B category elements are those that are not required, but could be selected by clinicians.
 * Larger group nominated a subset of developers who will take the core data elements and start modeling it into the CIM. The group will complete their work in the next two weeks under the direction of Bob Yencha, ONC Contractor.


 * Architecture/Implementation RQ and Reference Implementation** **WGs**
 * RI Architecture Scope has to be re-written due to a copy and paste error in the main pages.
 * WG has identified what needs to be changeed in the scope, and have created a timeline for the project documenting work expected in the coming months
 * WG has also developed a revised draft of the ToC goals but requires further input from the larger ToC community.


 * Next Steps for Architecture/Implementation RQ and Reference Implementation WGs**
 * Primary goal is to take the CIM documents and turn them into outputs (CIM Model Objects)
 * WG will vote on the RI Architecture Scope
 * Architecture team plans to develop a data flow diagram and generate functional/technical requirements
 * Architecture block diagram is in good shape and can be used as a solid foundation


 * Standard and Analysis WG**
 * WG will be the horizontal layer, which looks at the data needs and provides guidance to the data elements WG. WG is primarily using C83 templates.
 * Standard Analysis WG has not flushed out exactly what the artifact will look like but are associating the CIM input with the C83
 * Reviewing requirements around the core data elements to create a good guidance around that CIM input while still reflecting the template that exists
 * Data elements sets are a way to speak back to the use case documents so that an upstream and downstream flow from data definitions exists
 * Standards Analysis and Arch/ RI will begin working in synch going forward – working vertically instead of horizontally to begin generating work


 * WG Collaboration Points**
 * CDA Consolidation work could be ongoing through the ballot process, also CIM/ Vocab work will continue for the next few weeks
 * Reference Implementation should not wait until work is finalized from CIM and Standards Analysis to begin their work. Arch/IR must work off of existing artifacts but be cognizant of change management and version control


 * ONC and Leads Feedback**
 * Comments from Arien Malec: The CIM model by design is not an interoperability model; we need to look further at what the Standards Analysis team chooses as a standard for ToC that describes the interoperability. The CIM is not an implementation model either. Suggestions: the library of templates that will be developed as a result of CDA Consolidation could be used here as an input. Our use of “Implementation Guide” really means what is required and what is not; we will make use of already existing templates as we move forward.
 * Comments from Keith Boone: In terms of Standards Analysis, it is still under development. We are trying to figure out how to supply all information to the CIM and transform it into an end result through some sort of mapping. The process in which this will occur is still being determined.

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