1. Data Provenance Community Meeting July 17 th, 2014

2. Meeting Etiquette Click on the “chat” bubble at the top of the meeting window to send a chat. 2 Please mute your phone when you are not speaking to prevent background noise. – All meetings are recorded. Please do not put your phone on hold. – Hang up and dial back in to prevent hold music. Please announce your name before speaking Use the “Chat” feature to ask questions or share comments. – Send chats to “All Participants” so they can be addressed publicly in the chat, or discussed in the meeting (as appropriate).

3. Agenda Topic Time Allotted General Announcements5 minutes Use Case Discussion35 minutes Tiger Team Report Out5 minutes EHR Record Lifecycle Events Presentation10 minutes Next Steps/Questions5 minutes 3

4. Next meetings: HL7 DProv Joint Working Session: Monday July 21 st, 2014 3:00- 4:00pm ET – New meeting information on wiki All Hands: Thursday July 24 th, 2014 – 2:30-3:30 pm ET http://wiki.siframework.org/Data+Provenance+Initiative All meeting materials (including this presentation) can be found on the Past Meetings page: http://wiki.siframework.org/Data+Provenance+Past+Meetings General Announcements 4

5. S&I Framework Phases outlined for Data Provenance PhasePlanned Activities Pre-Discovery  Development of Initiative Synopsis  Development of Initiative Charter  Definition of Goals & Initiative Outcomes Discovery  Creation/Validation of Use Cases, User Stories & Functional Requirements  Identification of interoperability gaps, barriers, obstacles and costs  Review of Candidate Standards Implementation  Creation of aligned specification  Documentation of relevant specifications and reference implementations such as guides, design documents, etc.  Development of testing tools and reference implementation tools Pilot  Validation of aligned specifications, testing tools, and reference implementation tools  Revision of documentation and tools Evaluation  Measurement of initiative success against goals and outcomes  Identification of best practices and lessons learned from pilots for wider scale deployment  Identification of hard and soft policy tools that could be considered for wider scale deployments We are Here 5

6. Data Provenance –Use Case (Discovery) Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead 6

7. Proposed Use Case & Functional Requirements Development Timeline 7 Week Target Date (2014) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page due following Tuesday by 8 P.M. Eastern 16/12 Use Case Kick-Off & UC Process Overview Introduce: In/Out of Scope & Assumptions Review: In/Out of Scope & Assumptions 26/19 Review: In/Out of Scope & Assumptions Introduce: Context Diagram & User Stories Review: Context Diagram & User Stories 36/26Review: Context Diagram & User StoriesReview: Continue Review of User Stories 47/3 Review: Finalize User Stories Introduce: Pre/Post Conditions Review: Pre/Post Conditions 57/10 Review: Finalize User Stories Introduce: Pre/Post Conditions Review: Pre/Post Conditions 67/17 Review: Pre/Post Conditions Introduce: Actors & Roles, and Activity Diagram/Base Flow Review: Actors & Roles and Activity Diagram/Base Flow 77/24 Review: Actors & Roles, and Activity Diagram/Base Flow Introduce: Functional Requirements & Sequence Diagram Data Requirements Review: Functional Requirements & Sequence Diagram, and Data Requirements 87/31 Review: Functional Requirements, Sequence Diagram and Data Requirements Introduce: Risks & Issues Review: Risks & Issues 98/7 Review: Risks and Issues Begin End-to-End Review End-to-End Review by community 108/14End-to-End Comments Review & dispositionEnd-to-End Review ends 118/21Finalize End-to-End Review Comments & Begin ConsensusBegin casting consensus vote 128/28Consensus Vote*Conclude consensus voting

8. Sections for Review 8 Today we will be reviewing: 1.Pre/Post Conditions Introduce: 1.Actors & Roles 2.Activity Diagrams 3.Base Flows Double click the icon to open up the Word Document with the sections for review

9. Preconditions Where it exists, the assembling software, is integrated into systems such as EHRs, PHRs, and HIEs – indicating the type of information for a receiver to use as provenance for calculating reliability, and the organization or person responsible for deploying it There exists an Access Control System that allow the assembler to perform necessary tasks for predecessor artifacts and newly assembled artifacts All systems generating or consuming any artifact are capable of persisting the security labels received and data segmentation based the security labels assigned by the artifact generator, which may be an assembler 9 Post Conditions Receiving system has incorporated provenance information into its system and association of the provenance information to the source data is persisted Sending and receiving systems have recorded the transactions in their security audit records Pre/Post Conditions

10. HL7 DProv Joint Working Session Bob Yencha – Subject Matter Expert Kathleen Connor – Subject Matter Expert Ioana Singureanu – Subject Matter Expert Neelima Chennamaraja – Subject Matter Expert Johnathan Coleman- Initiative Coordinator 10

11. Tiger Team Report Continued discussion on author types and distinctions, requirements for each type Working through Scenario B and identifying constraints and considerations Will be focusing on critical questions required to complete the ballot on Monday (7/21)

12. Record Lifecycle Events and Data Provenance Across S&I Initiatives Gary Dickinson – Subject Matter Expert Presentation Available Here: http://wiki.siframework.org/file/view/ONC-SI-Provenance- Record%20Lifecycle%20Events%20Across%20SI%20Initiatives-20140701.pdf/516279494/ONC-SI- Provenance-Record%20Lifecycle%20Events%20Across%20SI%20Initiatives-20140701.pdf 12

13. A look ahead: Data Provenance Next Week 13 July 24 th, 2014 – All Hands Community Meeting (2:30-3:30) – Review Actors & Roles, Activity Diagrams and Base Flows Provide your comments on the bottom of this page http://wiki.siframework.org/Data+Provenance+Use+Cases http://wiki.siframework.org/Data+Provenance+Use+Cases

14. Support Team and Questions Please feel free to reach out to any member of the Data Provenance Support Team: Initiative Coordinator: Johnathan Coleman: jc@securityrs.comjc@securityrs.com OCPO Sponsor: Julie Chua: julie.chua@hhs.govjulie.chua@hhs.gov OST Sponsor: Mera Choi: mera.choi@hhs.govmera.choi@hhs.gov Subject Matter Experts: Kathleen Conner: klc@securityrs.com and Bob Yencha: bobyencha@maine.rr.comklc@securityrs.combobyencha@maine.rr.com Support Team: – Project Management: Jamie Parker: jamie.parker@esacinc.comjamie.parker@esacinc.com – Use Case Development: Presha Patel: presha.patel@accenture.com and Ahsin Azim: ahsin.azim@accenturefederal.compresha.patel@accenture.comahsin.azim@accenturefederal.com – Harmonization: Rita Torkzadeh: rtorkzadeh@jbsinternational.comrtorkzadeh@jbsinternational.com – Standards Development Support: Amanda Nash: amanda.j.nash@accenturefederal.com amanda.j.nash@accenturefederal.com – Support: Lynette Elliott: lynette.elliott@esacinc.com and Apurva Dharia: apurva.dahria@esacinc.comlynette.elliott@esacinc.comapurva.dahria@esacinc.com 14