1. Data Provenance –Use Case (Discovery) Ahsin Azim Nisha Maharaja Presha Patel 1

2. 2 Week Target Date (2014) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page due following Tuesday by 8 P.M. Eastern 108/21 Review: Scenario #1 and #2 Functional Requirements and Sequence Diagrams Introduce: Scenario #3 Functional Requirements and Sequence Diagrams Review Scenario #3 Functional Requirements and Sequence Diagrams 118/28 Review :Scenario #3 Functional Requirements and Sequence Diagrams Introduce: Dataset Requirements Review Dataset Requirements 129/4Review Dataset Requirements and Risks/Issues Review Data Set Requirements and Risks And Issues 139/18 Finalize Data Set Requirements and Risks/Issues Begin End to End Review Review Risks/Issues 149/25End-to-End Comments Review & dispositionEnd-to-End Review ends 1510/2 Finalize End-to-End Review Comments & Begin Consensus Begin casting consensus vote Proposed Use Case & Functional Requirements Development Timeline

3. Agenda Topic Time Allotted General Announcements2 minutes Use Case Discussion Discuss Timeline/Progress to Date2 minutes Comments and Dispositions15 minutes Review Scenario #1 & #2 Sections (Functional Requirements and Sequence Diagram) 5 minutes Review Scenario #3 Sections (Functional Requirements and Sequence Diagram) 25 minutes Introduce Data Set Requirements10 minutes Next Steps1 minutes 3

4. 4 Progress to Date Use Case SectionsStatus In Scope Out of Scope Assumptions Context Diagram User Stories Pre Conditions Post Conditions Actors & Roles Activity Diagrams Base Flows Functional Requirements Sequence Diagrams Dataset Requirements = section developed = section under development(% completed) = indicates there are 3 sections for development (1 for each of the scenarios identified)

5. Sections for Review 5 Today we will be reviewing: 1.Review Functional Requirements and Sequence Diagram(s) for Scenarios 1, 2, and 3 2.Introduce Dataset Requirements Double click the icon to open up the Word Document with the sections for review

6. Dataset Requirements Discussion 6 For the purposes of this Use Case, the Dataset Requirements will focus on the data elements pertaining to provenance for the clinical data, including the handling of that data, recognizing that it may contain data from multiple sources – Who, When, Where, Type, Routing Information, Integrity/Authenticity, Sources In order to capture the provenance data elements, we propose that we discuss the data elements within these categories: Data Source, Transmitter, Assembler, and Composer. We recognize there may be overlap across these categories. As a reminder: – The Dataset Requirements define data from a functional standpoint, not from a technical perspective – We will use this section to figure out to what extent the standards can adhere to the requirements (not specifications) – The Dataset Requirements for the Use Case are standards agnostic The following slides serve as a starter set to begin the discussion and brainstorming of Dataset Requirements; this will eventually be put into a structured format in the Use Case document

7. Dataset Requirements - Source 7 Who – Sending System; Sending System Organization; Author; Custodian; Attester; Role; etc. When – Create Date; Create Time; etc. Where – Address; State; Zip; etc. Type – Software; Device; etc. Question for Community: What are the important attributes of provenance that the dataset must contain?

8. Dataset Requirements - Transmitter 8 Who – Transmitter; Transmitter Organization; etc. When – Transmittal Date; Transmittal Time; etc. Where – Address; State; Zip; etc. Type – Software; Device; etc. Routing Information – Information sent to/from Integrity/Authenticity – In order to trust the data, do you need to know about how it was handled/who handled it/has it been altered since it was created????

9. Dataset Requirements - Assembler 9 Who – Assembler System; Assembler Organization; etc. When – Assembly Date, Assembly Time, etc. Where – Address; State; Zip; etc. Type – Software; Device; etc. Integrity/Authenticity – In order to trust the data, do you need to know about how it was handled/who handled it/has it been altered since it was created???? Sources – What is the provenance of the information that was assembled????

10. Dataset Requirements - Composer 10 Who – Composer; Composer Organization; etc. When – Composition Date; Composition Time; etc. Where – Address; State; Zip; etc. Type – Software; Device; etc. Integrity/Authenticity – In order to trust the data, do you need to know about how it was handled/who handled it/has it been altered since it was created???? Sources – What is the provenance of the information that was assembled????

11. A look ahead: Data Provenance Next Week 11 September 4 th, 2014 – All Hands Community Meeting (2:30-3:30) – Review Dataset Requirements 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

12. 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.dharia@esacinc.comlynette.elliott@esacinc.comapurva.dharia@esacinc.com 12