TOC+Architecture+Workflow+Diagrams+Consensus+Votes

include component="page" wikiName="siframework" page="TOC Header" Please enter your comments/endorsement of the ToC Architecture Workflow Diagrams in the table below. Please find your name below, and provide a yes or no vote. If your vote is no, please explain __**in detail**__ what your objections are and how you believe they can be resolved.

Please note, only committed WG members can participate in the consensus process.

Cynthia Levy - Diagrams and text changed to be consistent (ToC). Spelling for Schematron changed. || Cynthia Levy - per discussion, the Workflow diagrams which show the RI do not comprise of any auditable events. However, the systems do require auditable events. The Policies/Services will include guidance in this area. || Cynthia Levy - Addition of ToC Document Validation example to the page. ||
 * **Workgroup Member** || **Representing Organization** || **Endorsement (Yes/No)** || **If No, what can be done to make it Yes?** ||
 * Mayuri Patel || ICA || Yes ||  ||
 * Bob DeAnna || Recursion Software || Yes ||  ||
 * Chris Doucette || Deloitte ||  ||   ||
 * Tom Caruso || BITT™ || Yes ||  ||
 * Mark Bamberg || MEDfx ||  ||   ||
 * David Tao || Siemens || Yes, w. comment || TOC and ToC are both used as an abbreviation: need to settle on one abbreviation and use it consistently in this and all other pages. "Schema-tron" spelling needs to be fixed (remove hyphen) in the diagrams. I already fixed it in the text.
 * Jaime Estrada || Health Information Network of Arizona ||  ||   ||
 * John Moehrke || IHE ITI and GE Healthcare ||  ||   ||
 * Ken Pool || OZ Systems, Inc ||  ||   ||
 * Krishna Murali Brahmandam || Proheamon, Inc. ||  ||   ||
 * Steve Rushing || Georgia Tech || Yes ||  ||
 * Andrew Splitz || S&P Consultants, Inc ||  ||   ||
 * John Wandelt || Georgia Tech Research Institute (GTRI) ||  ||   ||
 * Lester Keepper || SHAPE HITECH || Yes, with following concern. || It is our position that all actions performed with the TOC documents need to recognize and include the identities of the actors. As such, this information __is__ “content” and should be considered as in scope for TOC RI Architecture, as well as seen as relevant to the future use of these RI Workflows.
 * Ernest Grove || SHAPE HITECH || Yes, please see above ||  ||
 * Vassil Peytchev || Epic ||  ||   ||
 * Mark Palen || System Admin Services, LLC || Yes ||  ||
 * David Cheng || IBM ||  ||   ||
 * Larry Sampson || MN HIE ||  ||   ||
 * Susan Nedza MD || HealthyCircles, LLC || Yes ||  ||
 * Robin Barnes || AHRQ/USHIK ||  ||   ||
 * Gary Dickinson || CentriHealth ||  ||   ||
 * Terri Skalabrin || CORHIO ||  ||   ||
 * Teresa Mota, BSN, RN || Quality Partners of RI || Yes || I agree that there should be an example of a "warning" with a valid document.
 * Susan Campbell || Care Management Professionals ||  ||   ||
 * Allen Hobbs || Kaiser Permanente ||  ||   ||

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