1 / 11

Data Segmentation for Privacy Agenda All-Hands Workgroup Meeting

Data Segmentation for Privacy Agenda All-Hands Workgroup Meeting. July 25, 2012. 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

rhoda-odonnell
Download Presentation

Data Segmentation for Privacy Agenda All-Hands Workgroup Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Segmentation for PrivacyAgendaAll-Hands Workgroup Meeting July 25, 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 • IG Consensus Vote Status • Consensus is waiting on re-casted votes from several community members. If you received a re-cast voting request, please respond a.s.a.p. • Remember that our goal is to move forward on the RI/Pilots. • A YES vote does not necessarily mean that the deliverable is the ideal one from the perspective of the Initiative Member, but that it is better to move forward than to block the deliverable. • Remember that just as the RI/Pilots activities will likely result in future updates to the IG, there will also be additional future opportunities for the community to provide their feedback and input to the next version of the IG document. • Wiki Navigation Changes • We will be deprecating the blue and green navigation buttons on the DS4P wiki in the coming week. If you have questions or comments, please contact Jenny Brush (jennifer.brush@esacinc.com).

  5. Pilot Sub-WG Timeline

  6. DS4P RI/Pilot WG Activities I • Last Week’s Activities • VA/SAMHSA Pilot Team • - Presented Pilot ecosystem overview • - Completed Sprint-4 development activities • http://wiki.siframework.org/file/view/DS4PPilotWGSprint4Review.pptx • DS4P RI/Pilot Support Team • - Documented list of pilot showcase opportunities and pre-requisites • HL7 Annual Plenary and Work Group Meeting – Sep 09-14, 2012 – Baltimore, MD • HIMSS interoperability showcase – March 02-07, 2013 - New Orleans, LA • http://wiki.siframework.org/file/view/DS4P+-+Showcase+Venues.doc

  7. DS4P RI/Pilot WG Activities II • This Week’s Activities • VA/SAMSHA Pilot Team • - Presented project plan and technical overview of the Pilot ecosystem • http://wiki.siframework.org/SAMHSA-VA-Pilot • Started review of Pilot alignment with DS4P initiative requirements captured in Requirements • Traceability Matrix (RTM) • - Continuing Sprint-5 development activities • http://wiki.siframework.org/file/view/DS4PPilotWGSprint5In-ProgressReview.pptx • - Team researching opportunities to present at the HL7 Meeting Sep 09-14, 2012 • DS4P RI/Pilot Support Team • - Updating RTM to align with latest IG • - Updating RTM to reflect VA/SAMSHA specific requirements • - Preparing http://pilots.siframework.org website materials to summarize DS4P initiative • - Preparing logistics requirement document for VA/SAMSHA showcase at HL7 Meeting in Sep 09-14, 2012 – Baltimore, MD • DS4P Community • - Meeting with Valley Hope Association to explore the possibility for a DS4P Pilot

  8. Implementation Guide Status • Work Accomplished • Posted revised IG along with dispositions to the wiki on Friday, July 20th • Revised and indexed conformance criteria and recommendations • IG updates that reflect confirmed resolutions from WG referencing “deferred” comments • Next steps • Recast votes (Today) • Finishing up the XML Consent Directive samples and ebXML XD* metadata samples • Finishing up the IG RTM Conformance criteria updates, to list out reasoning and implementation for each conformance criteria requirements • Working on process on handling “out of band” comments • Finalize IG Executive Summary document

  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 • 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:

  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. Next Steps / Meeting Reminders • Next Steps • If you received a re-cast voting request for the IG, please respond a.s.a.p. • Please join us at the RI/Pilots meeting on Monday, continuing the working session to document VA/SAMHSA-specific RTM requirements. • Meeting Reminders • RI/ Pilots • Monday, July 30, 2012 @ 11:00 am Eastern • All Hands Work Group Meeting • Wednesday, August 1, 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

More Related