Data Segmentation for Privacy Agenda All-Hands Workgroup Meeting August 8, 2012

Remember: If you are not speaking, please keep your phone on mute Do not put your phone on hold. If you need to take a call, hang up and dial in again when finished with your other call Hold = Elevator Music = frustrated speakers and participants This meeting is being recorded Another reason to keep your phone on mute when not speaking Use the “Chat” feature for questions, comments or items you would like the moderator or other participants to know. NOTE: This meeting is being recorded and will be posted on the Wiki. From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute Meeting Etiquette

Agenda TopicTime Allotted General Announcements10 Minutes Implementation Guide Status5 Minutes RI/Pilot Implementation - Status & Timeline - RI / Pilots Website & Wiki Changes - VA/SAMHSA RTM 20 Minutes S&I Core Matrix Exercise - Update10 Minutes Next Steps/Question5 Minutes

General Announcements Announcements

Implementation Guide Status Work Accomplished –Completed revised IG Updated XML Consent Directive samples and ebXML XD* metadata samples Updated resolution text to address all remaining “deferred” issues Updated dispositions log to provide rationale for the updates Updates include “out of cycle” comments (editorial updates) Next steps –Post IG and dispositions log to wiki for WG to review –Review/confirm IG updates and resolutions with WG (Wednesday, August 15 th )

Pilot Sub-WG Timeline 10/11/20116 Goal & Activities Week Number Tentative Dates Deliverables Kickoff /Establish Goals & Partnerships: - Review DS4P ONC Initiative Goals - Review Piloting Process & Resources - Define Value Statement - Define DS4P Pilot Goals & Success Metrics - Establish & Approve Pilot Ecosystems - Develop Pilot Briefs 1-2 (2wks) 5/22–6/3 -Wiki Capturing Pilot Deliverables -Established Partnerships -Documented Value Statements and Success Metrics -Documented Pilot Briefs Pilot Configuration: - Establish Pilot Test Environment & Resources - Establish Pilot Implementation & Testing Process - Develop & Review Pilot Configuration 3-4 (2 wks) 6/4–6/17 -Approved Pilot Briefs -Committed Pilot Resources -Documented & Reviewed Pilot Configuration Guide -Weekly Feedback on Use-Cases & IG Alignment Pilot Planning/Development : - Setup & Develop Pilot Prototypes - Review prototypes 5-10 (6 wks) 6/18-7/29 -Weekly Pilot Development Status Updates -Weekly Feedback on Use-Cases & IG Alignment -Updates to Pilot Configuration Guides Pilot Testing : - Complete Testing (2wks) 7/30–8/12-Weekly Pilot Testing Updates & KPIs Pilot Wrap-up : - Develop Lessons Learned and ONC Feedback - Review Initiative Goal Alignment - Establish Next-Steps - Capture Pilot Artifacts (2 wks) 8/13–8/27- Documented ONC Feedback - Next Steps Action Plan - Pilot Artifacts Pilot Showcase :September- Showcase pilot

Current Activities VA/SAMSHA Pilot Team - Participate in workgroup sessions to document UC Scenario 1 & 4 requirements - Participate in workgroup sessions to document UC Scenario 1 & 4 IG applicable conformances - Complete Sprint-6 development activities Sprint Review Meeting scheduled for Fri, August 10 - Research opportunities to present at the HL7 Meeting Sep 09-14, Collect approval for website materialshttp://pilots.siframework.org - Review HIPAAT potential pilot entry into VA/SAMHSA pilot ecosystem DS4P Community - Review Valley Hope and Anassazi Software potential pilot opportunity Other ONC Support - Analyze Implementation Guide conformances for UC Scenarios 2, 3, and 5 for future pilot use DS4P RI/Pilot WG Activities

DS4P RI/Pilot Materials Review S&I Framework Piloting Website Pilot Wiki Requirements Traceability Matrix VA/SAMHSA RTM DS4P RI/Pilot Materials

The S&I Simplification Team is reviewing the Data Segmentation for Privacy (DS4P) Use Case documents and need a consult regarding specification of various requirements. Two spreadsheets under consideration: 1.Simplification Core Matrix, v1.51, including DS4P Use Case Scenarios (this slide) 2.Core Requirements Analysis, including DS4P Requirements as specified (next slide) Goals Identify "Components" in common across Use Cases Current analysis Components include: Requirements, Scenario Events and Actions, Actors (now likely to include Roles and Participations), Data Objects and Elements Components are specified when we find evidence of common (current or potential) use across Use Case Initiatives and Scenarios Core Matrix The six DS4P Scenarios are in the Core Matrix Scenarios Tab with light blue background A few rows (white background) to show how the DS4P UC might be adapted or supplemented based on implementation requirements A set of example columns to show Sample Actions at each Event Step - in part to emphasize repetition patterns Outcome: identify specific Components from the DS4P Use Case that should be captured in the Core Matrix and thus become candidate for re-use in new Use Case Initiatives and Scenarios going forward Double-click to view file: Double-click to view file: S&I Simplification – Core Matrix Exercise

Double-click to view file: Double-click to view file: S&I Simplification – Core Requirements Analysis The Core Requirements Analysis spreadsheet, Raw Requirements Tab includes items enumerated in DS4P Use Case Requirements. See Rows Specify four things for each stated requirement: 1.Is this requirement a duplicate (of a requirement previously specified in another Use Case)? If so, insert notation in Column B 2.If not a duplicate, should we consider this requirement candidate as a Core Matrix Component, i.e., is it likely to be re-used in subsequent Initiatives? If so (in a later stage of analysis), we will assign an Rxxx ID and move it to Derived Common Requirements Tab (in Common Requirements spreadsheet) and ultimately incorporate in Core Matrix, Common Requirements Tab, and on consensus approval, in USHIK 3.Specify Requirement Type, Column D 4.Specify When requirement is fulfilled, Pre, During or Post Use Case Scenario, Column E 10

S&I Simplification – Work in Progress Expert Team meets Fridays Reviewing DS4P Requirements From Assumptions, Pre/Post Conditions, System Functional Requirements Which are Core candidates (likely to be re-used)? When is requirement fulfilled: Pre, During, Post? Next – Review DS4P Related Common Actions A.PERMIT – Set Access Permissions A.ACCESS.1 – Check Access Permissions A.ACCESS.2 – View/Access Record Entries 11

Next Steps –Please join us Friday, August 10 th to continue the working session to complete the S&I Core Matrix Simplification. All community members are welcome. Meeting information is on the wiki: formation formation Meeting Reminders –RI/ Pilots Monday, August 13, 11:00 am Eastern –All Hands Work Group Meeting Wednesday, August 15, 11:00 am Eastern For questions, please contact your support leads: –Johnathan Coleman (Initiative Coordinator) –Jenny Brush (Project Manager) –Horace Leslie (Harmonization Project Manager) –Joan DuHaime (RI/Pilots Project Manager) Next Steps / Meeting Reminders