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

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

ToC Architecture Implementation RQ WG Meeting Minutes

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

Attendance
Calvin Beebe, Tom Boal, Allen Hobbs, Les Keepper, Meredith Lewis, Cindy Levy, Mark Palen, Adrienne Pugh, Zeshan Rajput, Andriy Selivonenko, Bob Yencha

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 08-18-2011 || Add anchors to Policy and Service Analysis page || Meredith Lewis || Open ||  ||
 * 2 || 08-18-2011 || Identify if any policies or regulations are currently missing from [title] table || Volunteers || On-going ||  ||
 * 4 || 08-18-2011 || Add definitions for policies, services and regulations on both Policy and Service Analysis wiki page and TOC Glossary of Terms || Cindy Levy || Open ||  ||
 * 5 || 08-18-2011 || Nominate individuals to participate in analysis with expertise in IHE, module specifications (exchange) and Direct Project through the discussion tab || Volunteers || Open ||  ||
 * 6 || 08-18-2011 || Review deployment model page in preparation for the next WG meeting || Volunteers || Open ||  ||
 * 7 || 08-18-2011 || Post NHIN policies to Policy and Service Analysis wiki page that address privacy and security || Calvin Beebe || Open ||  ||
 * 8 || 08-18-2011 || Created bulleted list of authorizations and services that Connect provided from a software perspective || Les Keepper || 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
Announcements


 * HITSC Meeting
 * Russell Leftwich & John Donnelly WG Leads for Standards Analysis and TOC CIM presented
 * Provided overview of decisions made with TOC initiatvies and several of initiatives under S&I framework presented
 * Majority of questions were directed toward Russell and John Donnelly centered learning more about policies
 * Increase transparency of decisions
 * Increase volunteer outreach to ensure correct people are supporting work group
 * Call recording should be posted by end of week

TOC Policy and Service Analysis

>>
 * Reference Materials
 * Policies, procedures and regulations change regularly – so there is a need to provide an extensive reference material that is up to date
 * Policy and Service Analysis
 * Modified table from a google doc into a table embedded into wiki
 * Provided a simplified key word for elements and included text below chart for reference
 * Incorporated reference material pointing to documents and websites that include policies and updates
 * Vision of the page is to be a "living document"- as policies change and regulations are passed, page should be updated
 * 5 major categories of policies and regulations
 * Any new policies or regulations can be added as additional sections on the page and should have relevant reference materials incorporated as well
 * Make a distinction between certain policies e.g. HIPAA (must be followed), DURSA (informative/business agreement) and other policies may serve as guidance as opposed to being required.
 * Compliance- Must comply with regulations (have to obey no matter what) however with policies (mechanisms for organizations to meet various goals and requirements) it can pertain to local agreements in accordance with a signed DURSA
 * Definition of services - what are the business and technical implementations that can be used to meet the needs
 * RI implementation for TOC can assist with meeting the meaningful use requirements
 * Will need to determine the granularity for services and agreements
 * NHIN connect is a solution and will need to determine what areas can help an organization looking at security, privacy policies and establishing network policies
 * DURSA can be viewed as a model without signing onto NHIN. If signing NHIN, organization must implement DURSA
 * May want to consider federal DURSA as a model to investigate availability, reporting etc.
 * NHIN has technical services being provided and other business agreements that need to be incorporated including patient consent
 * HIPPA covers patient breach notification and does not completely cover patient consent, HIPPA doesn't cover any technology
 * Connect had invested in RI of NHIN to ensure patient information couldn't be sent without patient's consent
 * Next Steps
 * Connect Reference Implementation to the Use Cases
 * Will need to start planning development with regards to deployment models
 * Need to determine what types of models could be used
 * Two models had been presented by Tom Caruso and Mayuri Patel- click here to view them
 * How complex of a model we need to present
 * Need to investigate how patient consent fits into the policy service analysis table

Next Meeting
Add definitions for policies, services and regulations on both Policy and Service Analysis wiki page and TOC Glossary of Terms
 * Date:** 08-25-2011
 * Time:** 2:00-3:00pm

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