Presentation is loading. Please wait.

Presentation is loading. Please wait.

Data Provenance Community Meeting May 22 nd, 2014.

Similar presentations


Presentation on theme: "Data Provenance Community Meeting May 22 nd, 2014."— Presentation transcript:

1 Data Provenance Community Meeting May 22 nd, 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. 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 Announcements & Introductions10 minutes Tiger Team report out5 minutes Review of Project Charter15 minutes Overview of Discovery Phase of the Initiative25 minutes Next Steps/Questions5 minutes 3

4 Next meetings: Tuesday May 27 th – Tiger Team (3:00-4:00 pm ET) – PLEASE NOTE THE MONDAY MAY 26 TH TIGER TEAM MEETING IS CANCELED DUE TO THE MEMORIAL DAY HOLIDAY AND IS RESCHEDULED FOR TUESDAY MAY 27 TH Thursday May 29 TH – 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 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 Timeline for All Hands Meetings DateMeeting April 24 th Kick Off Review of Project Charter: Background, Challenge May 1 st Tiger Team Report Out Review Submitted Charter Comments Continue Review of Project Charter: Purpose and Goals, Scope, Potential Standards for Consideration May 8 th CANCELED DUE TO HL7 (Tiger Team Canceled as well) Tiger Team will present work to HL7 Weds May 7 th Q3 May 15 th Review of Project Charter Value Statement, Potential Standards for Consideration, Potential Risks, Stakeholders May 22 nd Final Review of Charter Begin Charter End to End Review May 29 th Dispose End to End Review Comments Start Charter Consensus Kick off Use Case June 5 th Charter Consensus Use Case Review 6

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

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

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

11 Data Provenance Charter Review Jamie Parker – Project Manager 11

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

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

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

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. Tools and Services Use Case Development and Functional Requirements Standards Development Support Standards Development Support Certification and Testing Harmonization of Core Concepts Implementation Specifications Pilot Demonstration Projects Reference Implementation Architecture Refinement and Management 15

16 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 16 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 17

18 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 Use Case Outline Tailored for each Initiative 6.0 Scenarios: Workflow – 6.1 User Story 1, 2, x, … – 6.2 Functional Requirements o 6.2.1 Information Interchange Requirements 7.0 Dataset Requirements 8.0 Risks, Issues and Obstacles Appendices – Related Use Cases – Previous Work Efforts – References ** Leverage content from Charter 18

19 Data Provenance Next Meetings Week 19 May 27 th, 2014 – Tiger Team (NOTE DATE CHANGE) May 29 th, 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 22 nd – COB May 27 th (8 pm ET) All End 2 End Review comments are due COB Tuesday May 27 th at 8:00 pm ET Charter and Comment form can be found here (by COB May 22 nd ): http://wiki.siframework.org/Data+Provenance+Charterhttp://wiki.siframework.org/Data+Provenance+Charter 20

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.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.comlynette.elliott@esacinc.com 21


Download ppt "Data Provenance Community Meeting May 22 nd, 2014."

Similar presentations


Ads by Google