Data Provenance Community Meeting

1. Data Provenance Community Meeting May 22nd, 2014

2. Meeting Etiquette Click on the “chat” bubble at the top of the meeting window to send a chat. • 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. • 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

4. General Announcements Next meetings: • Tuesday May 27th– Tiger Team (3:00-4:00 pm ET) • PLEASE NOTE THE MONDAY MAY 26TH TIGER TEAM MEETING IS CANCELED DUE TO THE MEMORIAL DAY HOLIDAY AND IS RESCHEDULED FOR TUESDAY MAY 27TH • Thursday May 29TH – All Hands meeting (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

5. S&I Framework Phases outlined for Data Provenance We are Here

6. Data Provenance Timeline for All Hands Meetings

7. Data Provenance Goals Improve the visibility of health information from creation to exchange, integration and use across multiple health information systems. Improve the confidence healthcare stakeholders have in the authenticity, reliability, and trustworthiness of shared data.

8. Data Provenance Tiger Team Bob Yencha – Subject Matter Expert Kathleen Conner – Subject Matter Expert Johnathan Coleman- Initiative Coordinator

9. Tiger Team Report – May 22, 2014 Reviewed timeline and key dates Reviewed use of wiki for comments and requirements capture; posting of documents for review Re-iterated call for relevant documents and requirements from community Began discussion of provenance support available in CDA in context of assembling documents from multiple sources

10. Aggregate CDA Documents • One document, auto-generated, from multiple organization and sub-organizations Primary identifier may be accompanied by secondary identifiers Document Record Target: Patient identifiers by organization Document Author Device: Aggregation Software Represented organization Document Informant: State HIE overrides Section Author Device: Software Represented organization Section Informant: Organization overrides Entry Informant: Sub-organization Represented organization Sub-organization of… Entry Author:Aggregation Software Assigning organization Entry Record:Org-specific patient id Secondary identifier may be redundant

11. Data Provenance Charter Review Jamie Parker – Project Manager

12. Project Charter Review • Background • Challenge Statement • Purpose and Goals • Scope Statement • Value Statement • Potential Standards for Consideration • Potential Risks and Challenges • Stakeholders • Timeline

13. Providing End to End Review Comments (Due May 27th) Data Provenance End to End Review Data Provenance End to End Review 5 NOTE: All End 2 End Review Comments are Due May 27th at 8:00 pm ET (after which time the comment form will be inactive) • Review the Project Charter • http://wiki.siframework.org/Data+Provenance+Charter • Fill out the comment form • http://wiki.siframework.org/Data+Provenance+Charter+and+Members#Comment • All fields are required • Select the “Submit” button to submit your comments • A message will display verifying that your comment was recorded • Refresh your browser to view your comment (comments display on the wiki page below the comment form)

14. Data Provenance –Discovery Phase Ahsin Azim– Use Case Lead Presha Patel – Use Case Lead Johnathan Coleman – Initiative Coordinator

15. ONC Standards and Interoperability (S&I) Framework Lifecycle • Our Missions • Promote a sustainable ecosystem that drives increasing interoperability and standards adoption • Create a collaborative, coordinated, incremental standards process that is led by the industry in solving real world problems • Leverage “government as a platform” – provide tools, coordination, and harmonization that will support interested parties as they develop solutions to interoperability and standards adoption. Pilot Demonstration Projects Standards Development Support Use Case Developmentand Functional Requirements Reference Implementation Harmonization ofCore Concepts Implementation Specifications Certificationand Testing Tools and Services Architecture Refinement and Management

16. S&I Framework Phases outlined for Data Provenance We Are Approaching

17. Use Case Development Objectives • Engage Stakeholders as Committed Members, Invite Experts, or Interested Parties in the creation of a Use Case  This is you all! • Identify Scenarios and User Stories that address real-world problems • Keep it simple • Focus on the business and functional requirements: Focus on “what” the requirements should be rather than “how” • Create a finalized Use Case that demonstrates value and supports the proposed goals and success criteria for the Initiative • Publish a finalized Use Case that contains necessary content, supported by artifacts, to enable Harmonization and subsequent S&I Framework efforts to occur

18. Use Case OutlineTailored for each Initiative • 6.0 Scenarios: Workflow • 6.1 User Story 1, 2, x, … • 6.2 Functional Requirements • 6.2.1 Information Interchange Requirements • 7.0 Dataset Requirements • 8.0 Risks, Issues and Obstacles • Appendices • Related Use Cases • Previous Work Efforts • References • 1.0 Preface and Introduction • 2.0 Initiative Overview • 2.1 Initiative Challenge Statement** • 3.0 Use Case Scope • 3.1 Background** • 3.2 In Scope • 3.2 Out of Scope • 3.3 Communities of Interest (Stakeholders)** • 4.0 Value Statement** • 5.0 Use Case Assumptions ** Leverage content from Charter

19. Data Provenance Next Meetings Week • May 27th, 2014 – Tiger Team (NOTE DATE CHANGE) • May 29th, 2014 – All Hands Community Meeting • Review End -2-End Comments with the Community • Kick off Charter Consensus • Review the Use Case Process

20. Next Steps – Provide End-2-End Comment Review • Based on our call today we will update and post the most updated Charter for comment • We will send an email to the community to let them know when it is ready for comment • End 2 End review will start COB May 22nd – COB May 27th (8 pm ET) • All End 2 End Review comments are due COB Tuesday May 27th at 8:00 pm ET • Charter and Comment form can be found here (by COB May 22nd): http://wiki.siframework.org/Data+Provenance+Charter

21. 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.com • OCPO Sponsor: Julie Chua: julie.chua@hhs.gov • OST Sponsor: Mera Choi: mera.choi@hhs.gov • Subject Matter Experts: Kathleen Conner: klc@securityrs.com and Bob Yencha: bobyencha@maine.rr.com • Support Team: • Project Management: Jamie Parker: jamie.parker@esacinc.com • Use Case Development: Presha Patel: presha.patel@accenture.comand Ahsin Azim: ahsin.azim@accenturefederal.com • Harmonization: Rita Torkzadeh:rtorkzadeh@jbsinternational.com • Standards Development Support: Amanda Nash: amanda.j.nash@accenturefederal.com • Support: Lynette Elliott:lynette.elliott@esacinc.com