ToC+Standards+Analysis+WG+Meeting+2011-07-20

include component="page" wikiName="siframework" page="TOC Header" =Standards Analysis Meeting Minutes=
 * Date:** 07-20-2011
 * Time:** 1:00-2:00pm EDT
 * Dial-in:** 1-408-600-3600 | **Passcode**: 667 204 991
 * Meeting Agenda:** 7/20 Meeting Agenda

Attendance
Amy Berk, John Donnelly, Amram Ewoo, Ollie Gray, Allen Hobbs, Hal Jiang, John King, Russell Leftwich, Teresa Mota, Vassil Peytchev, Adrienne Pugh, Erik Pupo, Andriy Selivonenko, Bob Yencha

Action Items
coverage of the elements from the CIM as required for exchanges || Erik Pupo || OPEN ||  ||
 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 07-20-2011 || Build the ToC Data Element Groups Document for the WG to review on 8/3 || Erik Pupo || OPEN ||  ||
 * 2 || 07-20-2011 || Announce Ecosystem Consensus to WG || Adrienne Pugh/ || OPEN ||  ||
 * 3 || 07-20-2011 || Conduct a gap analysis in the Content Module Index at data element level to verify

Agenda Items

 * 1) Welcome and Announcements (Adrienne Pugh)
 * 2) Review Comments on Ecosystem Consensus Statement (Team)
 * 3) Update on Content Module Index (John Donnelly)
 * 4) Next Steps (John Donnelly and Adrienne Pugh)

Meeting Notes
//**Ecosystem Consensus Statement**//
 * WG reviewed and voted on consensus statement ( Affirmative: 7 | Negative: 0)
 * Voting page has been updated with details on vote tallies
 * There were no negative endorsements during the call or the consensus period; the ToC Ecosystem has been accepted as proposed.

//**Next Steps**//
 * The consensus statement results will be announced to the full WG membership
 * Ecosystem conclusions will be used as input to Reference and Implementation workgroup, Health IT Standards Committee, and can be incorporated for the Implementation Guide and consolidated CDA guide
 * Future Work Item: Design of CCR-CCD Transformation service that will start in the Architecture workgroup (allows defined transition path for those providers who will need to move to a CDA-based approach for care transitions)

//**Content Module Index**//
 * Misalignment between columns A and B in the previous version (7-8-11); the current spreadsheet is synchronized and accurate
 * Ballot document will be sent to HL7 on Aug 5th and will be most likely be posted online after 24 hours
 * ToC CIM Detailed Report
 * The Data Elements will eventually be CIM objects
 * Data element groups are closely aligned to data element sets
 * Used content module index spreadsheet (July 8th) for the template IDs
 * Add column to reflect entry level templates
 * Align CIM objects to template IDs at entry level
 * The CIM provides a neutral representation of the clinical data model, which will be transferrable to a structure in CDA. CDA relies on architecture and coding elements and there will need to be a mapping to convert the CIM to something in CDA.

//**Next Steps**//
 * Continue with Content Module Index by reviewing the ToC CIM Detailed Report
 * Review on the TemplateID level to identify gaps because this is clinically driven. For those without templates, there is a gap. For those with multiple templates, need to establish guidance. Templates are developed from a clinical perspective and data elements within CIM objects will be aligned with the template id
 * Need to also incorporate DES Number for the ToC data elements
 * Conduct gap analysis review on the next workgroup call

Next Meeting

 * Date:** 07-27-2011
 * Time:** 1:00-2:00pm EDT

Reference Materials
Content Module Index Ecosystem Consensus Statement Conduct a gap analysis in the Content Module Index at data element level to verify coverage of the elements from the CIM as required for exchanges

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