Data+Segmentation+Pilot+Process

include component="page" wikiName="siframework" page="Data Segmentation HeaderPilots2"

Use this table to track DS Pilots in the Workgroup. Click on the pilot name in the "Organization" column below to navigate to the pilot brief. To update the table, click on the "EDIT" button in the upper right-hand corner, add a row to the table, and complete each field in the table. If you have any questions or need assistance, contact Joan DuHaime.

DS Pilot Projects

 * **Organization** || **Use Cases / Objectives** || **Stakeholders &**
 * Points of Contact** ||
 * VA/SAMHSA

//(Approved)// || ** PHASE 1 (Sept 2012) **

Section 7332 of Title 38 Push (Directed Exchange) / Share Partial
 * UC Scenario 1 : User Story 1.1A**


 * PHASE 2 (March 2013 HIMSS) **

Section 7332 of Title 38 Pull / Share all
 * UC Scenario 2 : User Story 1.1B**

Pull
 * UC Scenario 3 : User Story 1C**

Section 7332 of Title 38 Push (Directed Exchange) / Change Mind
 * UC Scenario 4 : User Story 1.1C**

Break the Glass || **SAMHSA** Richard Thoreson
 * UC Scenario 6 : User Story 3**

Mike Davis
 * VA**

Anne Kling
 * Mitre**

David Staggs
 * Jericho Systems**

Kel Callahan ||
 * HIPAAT**
 * SATVA

//(Approved)// || ** PHASE 1 (Pilot Release Sept 2012) **

42 CFR Part 2 Push (Directed Exchange) / Share All //Direct and XDS.b//
 * UC Scenario 1 : User Story 1**

Pull / Share All //42 CFR Part 2 Asynchronous Request / Response - Direct//
 * UC Scenario 2 : User Story 1B**


 * PHASE 2 (Production Release December 2012) **

42 CFR Part 2 Push (Directed Exchange) / Share All //Direct and XDS.b//
 * UC Scenario 1 : User Story 1**

Pull / Share All //42 CFR Part 2 Asynchronous Request / Response - Direct//
 * UC Scenario 2 : User Story 1B**

42 CFR Part 2 Pull //Internal Consent Repository//
 * UC Scenario 3 : User Story 1C**


 * PHASE 3 (Pilot Release February 2013) **

Break the Glass //Using Web Portal for Recording the Part 2 Break the Glass Event// || **SATVA** Michael Morris
 * UC Scenario 6 : User Story 3**

Michael Morris
 * Anasazi**

John Leipold
 * Valley Hope**

Arthur Khanlian
 * Defran Systems**

Margaret Cosentino
 * HEALTHeLINK**


 * Horizon Health Services**


 * Lakeshore Behavioral Health**


 * Spectrum Human Services**


 * Children and Adolescent Treatment Services**


 * Mid-Erie Counseling and Treatment Services**


 * The Resource Center** ||
 * Netsmart

//(Approved)// || ** PHASE 1 (Production - January 2013) **

42 CFR Part 2 Push / Share All / Partial
 * Scenario 1 - User Story 1**

42 CFR Part 2 Pull between providers / Share All / Partial
 * Scenario 2 - User Story 1B**


 * PHASE 2 (Pilot Release - January 2013) **

HIO Repository & Consent Repository
 * Scenario 3 - User Story 1C**


 * PHASE 3 (Production Release - February 2013) **

HIO Repository & Consent Repository || **Netsmart** Bill Connors Matthew Arnheiter
 * Scenario 3 - User Story 1C**

Laura McCrary, Ed.D || =Identifying Potential Pilot Partnerships= Please see Identifying Potential Pilot Partnerships for Organizations wishing to participate in the development of a Data Segmentation for Privacy Pilot. =Guidelines for a Pilot Project=
 * KHIN**

**Proposing a Pilot Project**

 * 1) Complete an entry in the "DS Pilot Projects" table, above and develop a pilot brief to summarize the expectations for the pilot. A template pilot brief is available in the reference material section on the Pilot Home.
 * 2) The DS RI/Pilots Workgroup ONC Support Team will then create a Pilot Brief Wiki page for your organization. The Pilot Brief page will be linked to in the "DS Pilot Projects" table above.
 * 3) Participate in pilot project discussion calls (workgroup meetings) to explain pilot proposal and answer community questions.
 * 4) After the Pilot Brief is complete, the Community accepts or rejects the proposed pilot based on criteria defined below. Accepted Pilots are indicated on the “DS Pilot Projects” table.

Criteria for acceptance as a DS Pilot Project

 * 1) Proposing organization should be registered as a committed member.
 * 2) Project should be distinct from other proposed pilots in terms of stakeholders, provider types, or goals.
 * 3) Project should include a set of measurable objectives that provides feedback on the DS Use Case, DS Implementation Guide, etc.
 * 4) Does the proposing organization commit adequate resources (people, infrastructure) to successfully complete the proposed scope?

Guidelines as an accepted DS Pilot Project

 * 1) Maintain your organization's Pilot Brief Wiki page.
 * 2) Name one or more individual(s) as the ‘pilot leader’ (who will represent the pilot on all workgroup calls).
 * 3) Use DS RI/Pilots WG wiki and communication tools to document status and operations of project.
 * 4) Participate in DS RI/Pilots Workgroup calls and provide regular status updates.
 * 5) Conform to DS RI/Pilots Initiative timeline.
 * 6) Provide pilot feedback to ONC management of lessons learned and intended next steps.
 * 7) It is recommended to complete a Configuration Guide for your Pilot to provide additional details. A template pilot configuration guide is available in the reference material section on the Pilot Home.

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