ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-9-8

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

ToC Architecture Implementation RQ WG Meeting Minutes

 * Date:** 09-8-2011
 * Time:** 2:00-3:00pm
 * Dial-in:**1-408-600-3600 | **Passcode**: 667 669 756

Attendance
Mark Bamberg, Kathryn Calderone, Susan Campbell, Steve Cason, Cindy Levy, Mayuri Patel, Erik Pupo, Zeshan Rajput, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 09-8-2011 || Verify the appropriate people are identified to help moving forward with TOC Profiles || Volunteers || Open ||  ||
 * 2 || 09-8-2011 || Create discussion flows for possible inclusion in the deployment diagram || Mark Bamberg || Open ||  ||
 * 3 || 09-8-2011 || Add in/out of scope section for Deployment model introduction || Cindy Levy || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Policy and Service Analysis (Erik Pupo, Mayuri Patel and Cindy Levy)
 * 3) Deployment Models (Mayuri Patel, Cindy Levy)
 * 4) Discuss Next Steps (Meredith Lewis, Mayuri Patel)

Meeting Notes

 * Announcements**
 * Meredith communicated to Lockheed Martin that Architecture/IR WG would not meet at F2F in October


 * Policy and Service Analysis**
 * Erik Pupo added content to the Direct and Exchange profiles and provided an overview of the content to the WG
 * At a high-level, Direct is more informative guidance and less prescriptive to help implementers create the key workflow documents. To learn more about the specific details associated with the Direct profile, please see the Transitions of Care Direct Profile wiki page.
 * The Profile Use Case supports current user stories in the Use Case with actor names, roles and actor types framed out
 * WG will need to clarify what potential roles might be and authorize providers to send an EHR and include a patient content service mechanisms
 * Beyond services, the next step is to clarify which transactions are available more specifically where a TOC document could be sent to
 * Alternative projects is intended to support alternative communities including Beacon to support their efforts in implementation guides and incorporating policies
 * Trust Model defines trust and security requirements surrounding exchange and participants with respect to transactions


 * TOC Deployment Table**
 * Cindy Levy made changes to the introductory paragraph and key considerations for participating in a HIE to provide further context
 * Potentially could include a reference section for other groups in terms of HIE participation
 * Testing and certification should be included to cover situations for example when providing a software and service to providers in different areas
 * HIE ability to support aggregate reporting and participate in exchanges for example state warehouse Massachusetts
 * Page is focused on TOC and the reason for an HIE is beyond the scope of a TOC
 * Mayuri suggested adding an in and out of scope section, similar to what was included in previous wiki pages, to clearly define content
 * Consider using more graphic representation of the deployment chart in order to provide a sense of interoperability based of network participation

Next Meeting

 * Date:** 09-15-2011
 * Time:** 2:00-3:00pm

Reference Materials

 * 1) Policy and Service Analysis
 * 2) Deployment Models
 * 3) TOC Direct Profile (Used by Direct Project participants)
 * 4) TOC Modular Specification Profile (Used by Exchange participants)

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