data provenance community meeting
DESCRIPTION
Data Provenance Community Meeting. May 22 nd , 2014. 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. - PowerPoint PPT PresentationTRANSCRIPT
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
Topic Time Allotted
General Announcements & Introductions 10 minutesTiger Team report out 5 minutesReview of Project Charter 15 minutesOverview of Discovery Phase of the Initiative 25 minutesNext Steps/Questions 5 minutes
4
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
General Announcements
5
S&I Framework Phases outlined for Data Provenance
Phase Planned 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 toolsEvaluation 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
6
Data Provenance Timeline for All Hands MeetingsDate Meeting April 24th • Kick Off
• Review of Project Charter: Background, Challenge
May 1st • Tiger Team Report Out• Review Submitted Charter Comments• Continue Review of Project Charter:
• Purpose and Goals, Scope, Potential Standards for ConsiderationMay 8th • CANCELED DUE TO HL7 (Tiger Team Canceled as well)
• Tiger Team will present work to HL7 Weds May 7th Q3
May 15th • Review of Project Charter• Value Statement, Potential Standards for Consideration, Potential Risks, Stakeholders
May 22nd • Final Review of Charter• Begin Charter End to End Review
May 29th • Dispose End to End Review Comments• Start Charter Consensus• Kick off Use Case
June 5th • Charter Consensus• Use Case Review
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 TeamBob Yencha – Subject Matter Expert
Kathleen Conner – Subject Matter Expert
Johnathan Coleman- Initiative Coordinator
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
Document Informant: State HIE
Section Informant: Organization
overrides
Entry Informant: Sub-organization
overrides
Sub-organization of…
Document Author Device: Aggregation SoftwareRepresented 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 ReviewJamie 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)
1. Review the Project Charter– http://wiki.siframework.org/Da
ta+Provenance+Charter2. Fill out the comment form
– http://wiki.siframework.org/Data+Provenance+Charter+and+Members#Comment
– All fields are required 3. Select the “Submit” button to
submit your comments4. 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
Data Provenance End to End Review
Data Provenance End to End Review
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)
14
Data Provenance –Discovery PhaseAhsin Azim– Use Case Lead
Presha Patel – Use Case Lead
Johnathan Coleman – Initiative Coordinator
ONC Standards and Interoperability (S&I) Framework LifecycleOur 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 DevelopmentSupport
Certificationand Testing
Harmonization ofCore Concepts
Implementation Specifications
Pilot Demonstration Projects
Reference Implementation
Architecture Refinement and Management 15
16
S&I Framework Phases outlined for Data Provenance
Phase Planned 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 toolsEvaluation 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 Approaching
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
•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 OutlineTailored for each Initiative
•6.0 Scenarios: Workflow– 6.1 User Story 1, 2, x, … – 6.2 Functional Requirements
o6.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
• 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 QuestionsPlease feel free to reach out to any member of the Data Provenance
Support Team:• Initiative Coordinator: Johnathan Coleman: [email protected] • OCPO Sponsor: Julie Chua: [email protected] • OST Sponsor: Mera Choi: [email protected]• Subject Matter Experts: Kathleen Conner: [email protected] and Bob
Yencha: [email protected] • Support Team:
– Project Management: Jamie Parker: [email protected] – Use Case Development: Presha Patel: [email protected]
and Ahsin Azim: [email protected] – Harmonization: Rita Torkzadeh: [email protected] – Standards Development Support: Amanda Nash:
[email protected] – Support: Lynette Elliott: [email protected]