ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-06-02

include component="page" wikiName="siframework" page="TOC Header" =ToC Architecture Implementation RQ WG Meeting Minutes=
 * Date:** 06-02-2011
 * Time:** 2:00-3:00pm EDT
 * Dial-in:** 1-408-600-3600 | **Passcode**: 666 821 000
 * Meeting Agenda: Click here for meeting agenda!**

Attendance
Mark Bamberg, Robin Barnes, Tom Boal, Amy Brantley, Susan Campbell, Tom Caruso, Steven Cason,Bob DeAnna, Ernest Grove, Allen Hobbs, Lester Keepper, Ed Larsen, Cynthia Levy, Cheryl Liu,Vassil Peytchev, Erik Pupo, Tim Reardon, Steve Rushing, Andriy Selivonenko, Terri Skalabrin, Corey Spears, David Tao, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 06-02-2011 || Register for Face to Face Meeting scheduled for June 14-15 by June 7th in Washington, DC || All || Open ||  ||
 * 2 || 05-19-2011 || Complete revisions to the RI Arch Overview from WG discussion on 06/02, If you are interested in supporting this effort, please reach out to Cindy Levy. || Need Volunteers || Open ||  ||
 * 3 || 05-12-2011 || Provide feedback on the RI Architecture Scope Statement through the RI Architecture Consensus Page || All || Open ||  ||
 * 4 || 06-02-2011 || Review Arch RI workflow diagram page and provide feedback || All || Open ||  ||

Agenda Items

 * 1) Welcome & Announcements
 * 2) Review feedback provided on RI Architecture Overview
 * 3) Review feedback on the RI Architecture Scope Statement
 * 4) Review updated RI Arch workflow diagrams

Meeting Notes

 * RI Architecture Overview reviewed by (Cindy Levy)**


 * ToC RI Architecture Overview Comments Page**

1.**Comment -** “Isomorphic representation?" Is there an easier-to-understand way to say it? I know it means something about being the same, but I don't really understand the intent of this statement. "Domain-specific services? " What are those? What are the domains? Suggest giving some examples.
 * David Tao Comment**


 * Resolution**
 * Cindy Levy will work on terminology and provide definitions

2.**Comment-** the Data Elements Layer" and "Data Elements Services Layer" sound too similar, and could be hard for someone to distinguish. Could the first be called the "Data Element Definition Layer" since it doesn't sound like it does any actions on the data, other than represent the CIM. Then the "Data Elements Services Layer" would be easier to understand as "doing things" to the data.


 * Resolution**
 * Change name to Data Elements Layer

3.**Comment -**The TOC RI Layers Diagram doesn't seem useful, and just takes us space that delays the reader getting to the next diagram. I suggest removing it. The TOC RI Component Diagram is much more descriptive and useful. There's not enough to justify having three levels of the same diagram. Alternatively, you could keep the RI Layers Diagram and the TOC RI Components and Services Diagram, and lose the middle diagram. Two diagrams would be plenty. Only work with most detailed diagram like the 3rd diagram


 * Resolution**
 * Bold titles in each box to highlights sections, delete first and second diagram and will rework 3rd diagram

1.**Comment -** Please label the diagrams so that there is a reference point
 * Mayuri Patel Comment**


 * Resolution**
 * Reference point not needed to label diagrams will use only 3rd diagram going forward

2.**Comment -** Identify "In Scope" services that will be provided as part of the RI - A statement should also be added about the other services and each service be identified as necessary services for ToC RI but out of scope for this Initiative.


 * Resolution/Concerns**
 * Provide descriptive services
 * Rename to Data Element Groups
 * Diagram has more detail with text but not enough to understand
 * Does this relate to Use Case 1 and 2 only?
 * Need to keep flow of content put in thumbnail to indicate each layer and an introduction to content included in each layer
 * Possibly discuss at F2F meeting


 * Lester Keepper Comment**

1.**Comment -** the RI Baseline Goals state: “ToC Information Package Validation Tools…will validate that a ToC Information Package is complete and correct.” Also, the Scope Statement and the RI Baseline Goals say: “These tools will validate that a ToC Information Package is complete and correct.” The HL7/CCD code also takes into account the S&I present and future “privacy and security” goals of healthcare. To complete this, user identification should be attached to every user action. This provides auditable tracking that will increase communication, increase compliance efficiently, and lessen fraud.


 * Resolution/Concerns**
 * Different groups for security and requirements are critical
 * Use mechanisms different from auditing requirements
 * Add verbiage notating top layer is where responsibility lies
 * Possibly show a series of sets

Next Meeting

 * Date:** 06-09-2011
 * Time:** 2:00-3:00pm EDT
 * Dial-in:**1-408-600-3600 | **Passcode**: 661 241 577

Reference Materials

 * 1) ToC RI Arch Overview
 * 2) ToC RI Arch Scope
 * 3) ToC RI Architecture Overview Consensus Page
 * 4) ToC RI Arch Workflow

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