Data Segmentation for Privacy Agenda All-Hands Workgroup Meeting

1. Data Segmentation for PrivacyAgendaAll-Hands Workgroup Meeting August 8, 2012

2. Meeting Etiquette • 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, commentsor items you would like the moderator or other participants to know. From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute  NOTE: This meeting is being recorded and will be posted on the Wiki.

3. Agenda

4. Announcements • General Announcements

5. 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 15th)

6. Pilot Sub-WG Timeline

7. DS4P RI/Pilot WG Activities • 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, 2012 • - Collect approval for http://pilots.siframework.org website materials • - 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

8. DS4P RI/Pilot Materials • DS4P RI/Pilot Materials Review • S&I Framework Piloting Website • http://pilots.siframework.org • Pilot Wiki • http://wiki.siframework.org/Data+Segmentation+for+Privacy+RI+and+Pilots+Sub-Workgroup • Requirements Traceability Matrix • VA/SAMHSA RTM • http://wiki.siframework.org/file/view/DS4P_RTM_VASAMHSA_0806a.xlsx

9. S&I Simplification – Core Matrix Exercise • 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: • Simplification Core Matrix, v1.51, including DS4P Use Case Scenarios (this slide) • 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 • Afew rows (white background) to show how the DS4P UC might be adapted or supplemented based on implementation requirements • Aset 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:

10. S&I Simplification – Core Requirements Analysis • The Core Requirements Analysis spreadsheet, Raw Requirements Tab includes items enumerated in DS4P Use Case Requirements.  See Rows 286-321 • Specify four things for each stated requirement: • Is this requirement a duplicate (of a requirement previously specified in another Use Case)?  If so, insert notation in Column B • 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 • Specify Requirement Type, Column D • Specify When requirement is fulfilled, Pre, During or Post Use Case Scenario, Column E Double-click to view file:

11. 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

12. Next Steps / Meeting Reminders • Next Steps • Please join us Friday, August 10th to continue the working session to complete the S&I Core Matrix Simplification. All community members are welcome. Meeting information is on the wiki: http://wiki.siframework.org/Data+Segmentation+for+Privacy+Meeting+Information • Meeting Reminders • RI/ Pilots • Monday, August 13, 2012 @ 11:00 am Eastern • All Hands Work Group Meeting • Wednesday, August 15, 2012 @ 11:00 am Eastern • For questions, please contact your support leads: • Johnathan Coleman (Initiative Coordinator) jc@securityrs.com • Jenny Brush (Project Manager) jennifer.brush@esacinc.com • Horace Leslie (Harmonization Project Manager) hleslie@deloitte.com • Joan DuHaime (RI/Pilots Project Manager) joan.e.duhaime@lmco.com