ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-07-21

include component="page" wikiName="siframework" page="TOC Header"

ToC Architecture Implementation RQ WG Meeting Minutes

 * Date:** 07-21-2011
 * Time:** 2:00-3:00pm
 * Dial-in:**1-408-600-3600 | **Passcode**: 667 669 756
 * Meeting Agenda: Click here for the agenda!**

Attendance
Tom Boal, Steven Cason, Kelly Conlin, Bob DeAnna, Amram Ewoo, Lester Keepper, Russell Leftwich, Cynthia Levy, Teresa Mota, Mark Palen, Mayuri Patel, Adrienne Pugh, Erik Pupo, Andriy Selivonenko, David Tao, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 07-21-2011 || Review ToC Policy and Service Identification Sheet and sends comments through the Google spreadsheet linked from the TOC Arch/ IR Wiki page || All || Open ||  ||
 * 2 || 07-21-2011 || Send Erik comments on what implementation guide/profile will look like in order to provide guidance on privacy and security mechanisms || All || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Adrienne Pugh)
 * 2) Review feedback provided on Workflow Diagrams Consensus Page (Mayuri Patel and Cindy Levy)
 * 3) Review RI Architecture Overview
 * 4) Introduce Policy and Service Analysis (Erik Pupo, Mayuri Patel and Cindy Levy)

Meeting Notes
//__Architecture Workflow Diagrams__//


 * WG reviewed and provided comments on diagrams
 * Les suggested that each action on the diagram should have a corresponding actor listed
 * For every action, there should be an audit trail reflecting the members where the actions have taken place.
 * RI Architecture TOC Document Validation Workflow Example:
 * The question was raised if the audit trail for action should be placed in the schema
 * The green shapes in the diagram will have associated coding and blue shapes are the output from that coding.
 * RI code is not an auditable event since the responsibility for auditing is outside the realm of the RI HIE, however the request and query of documents, sending documents to be stored, requesting provider documents can be considered auditable events (per HIE concepts already in place).
 * Decision reached: the policies and guidance stage of work will encompass the audit process, not the RI stage.

//__Policy and Service Analysis__//


 * Policy and Service Analysis will provide guidance on putting system together and provide references to auditable events as well as provide service information for implementation for transport on privacy and security
 * No transport guidance currently exists. As a workgroup, we may want to consider the creation of implementation guidance.
 * There will be a need for information exchange at some point although the medium for that exchange has yet to be determined. Once it is determined, that exchange will be subject to policy, etc.
 * Meaningful Use in Stage 2 will have standards being developed for the exchange for potential transport areas (perhaps Direct or new modular specs). This implementation guidance for exchanging key TOC information points will be supportive and explanatory of TOC RI’s work.
 * Exchange Project does not currently have any TOC guidance to leverage; however that project may be eventually interested in work that our group can do in terms of guidance we can provide above and beyond a profile to include testing and tooling.

Next Meeting

 * Date:** 07-28-2011
 * Time:** 2:00-3:00pm

Reference Materials

 * 1) Workflow Diagrams Consensus Page
 * 2) Policy and Service Analysis

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