ToC+Architecture+Impl+RQ+WG+Meeting+Minutes+2011-08-25

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

ToC Architecture Implementation RQ WG Meeting Minutes

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

Attendance
Mark Bamberg, Tom Caruso, Amram Ewoo, Allen Hobbs, Les Keepper, Meredith Lewis, Cindy Levy, Susan Nedza, Mayuri Patel, Erik Pupo, Sandy Stuart, Andriy Selivonenko, Ashley Swain, David Tao, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 08-25-2011 || Incorporate formatting changes for Policy and Service Analysis || Meredith Lewis || Open ||  ||
 * 2 || 08-25-2011 || Get official verification on NHIN vs NwHIN || Meredith Lewis || Open ||  ||
 * 3 || 08-25-2011 || Determine relevant elements from NwHIN to be included in table and incorporate inventory of tools || Cindy Levy || Open ||  ||

Agenda Items

 * 1) Welcome and Announcements (Meredith Lewis)
 * 2) Review Policy and Service Analysis (Mayuri Patel and Cindy Levy)
 * 3) Discuss Next Steps (Meredith Lewis)

Meeting Notes
TOC Policy and Service Analysis
 * Updates
 * No major changes to wiki page since C.Levy has been working offline w/ C. Beebe
 * Tom Caruso has provided comments around language & formatting as well as labeling of TOC Use Case into discussion page
 * Policy and Service Analysis wiki page
 * Started to incorporate NwHIN services that could be applicable to Direct
 * Discussed services to make use of to ensure implementers had guidelines and regulations they need to be aware of
 * ONC webpage has a list of on-going programs, one program provides an inventory of tools they provided under privacy, security and trust
 * Authorization framework, consent policies could be applicable to services when providing a TOC solution
 * However, we wouldn't want implementers to "cherry-pick" specs since the HITSP guide and HITSC IG package the information that is require
 * Need to provide an introduction or profile table that could be an exchange solution but is simplified enough to represent user stories that fit with Direct
 * Might need to consider different user stories and language for NwHIN Exchange since Direct doesn't require DURSA
 * Could propose separate tables the apply to Direct vs NwHIN Exchange to provide additional details on resolving issues
 * Incorporate introductory statement above in that the table represents feedback, reference implementation being developed with user stories and this is the information that can be provided for the scope. HIE and Exchange user stories can be incorporated in the coming year.
 * User stories need to be qualified and it could open up possibilities on how they implement them
 * This document will specify optional services - and should be explicit documentation
 * Need to be consistent with use cases that are approved in order to ensure proper guidance
 * Contact ONC on NwHIN vs NHIN and verify the correct term
 * DURSA applies to security policies
 * Level of detail on wiki page should be a redirection to the real specs. however we need to balance the level of information by providing sufficient details
 * Need to incorporate pointers to the specifications and relevant ONC pages as well as the on-boarding process

Next Meeting

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

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