Data Provenance All Hands Community Meeting February 26, 2015

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

Agenda TopicTime Allotted Announcements5 minutes System Requirements SWG Introduction25 minutes EHR Transactions Task Force Recommendation and Data Elements Discussion 25 minutes

Announcements System Requirements SWG launching tomorrow Friday February 27 th ! – 12:00 pm – 1:00 pm ET – Details can be found on our wiki page: Information Interchange SWG will launch next Wednesday March 4 th – 2:00 pm – 3:00 pm ET – Details for this SWG meeting can also be found on our wiki: 4

System Requirements Sub-Work Group 5

Scope Address System Requirements for provenance (including “source provenance”) by looking at provenance data at time of import, creation, maintenance, and export. – Note: Agnostic of transport technologies – Consider FDA Project, Guidance and Regulations - There are 12 requirements and use cases for the use of EHRs and eSource applications (e.g. patient reported information/eDiaries) requiring provenance described in an eSource Data Interchange Document, FDA Guidance, which includes a definition for “the source” and regulation for Electronic Records. 6

Framing Question For information within an EHR, can I trust it, and has it been changed? Consider that, for clinical care, if trending the data, one may need to know the degree to which the information can be trusted. 7

System Requirements SWG Goals 8 Goal # GoalArtifact and Description 1 Define a set of basic/core EHR system requirements for provenance for: (NOTE: Build upon Data Elements as defined by the current Use Case) Import Create Maintain Export (note this is the minimum set of areas of focus based on the task force recommendations) Minimum set of provenance requirements – Document (may include transaction tables/UML diagrams, DE mapping etc.) 2 Identify Candidate Standards to meet the requirements of Goal 1 using existing candidate standards list (To be supplied) Short list of the proposed candidate standards that can achieve requirements of the first goal 3 Choose a definition of “change” to data (for example, transformation with no intent to change the meaning of the data such as content format, terminology, or feature extraction versus substantive changes such as amend, update, append, etc.) and the implications for provenance. If the content changes, the change should be considered a “provenance event”. Provide a definition of “Change” to data 4 Consider the implications of security aspects related to information interchange – Traceability, audit, etc. – what is the impact on the trust decision? List or document of the implications of security aspects 5 If applicable, capture policy considerations related to system behavior and request further guidance from the HITPC. List of questions for HITPC

System Requirements SWG Week of2/233/23/93/163/233/30 Launch SWG: Prepare, organize, plan, review existing materials Define a core set of provenance requirements Identify Candidate Standards to meet the need of requirements Define “change” and the implications for provenance Consider implications of security aspects Capture policy considerations and request further guidance ** Report out on weekly progress during the Thursday All Hands Call** Legend: Not Started; In progress; Ready

EHR Transactions Task Force Recommendation To address the priority areas recommended by the Task Force, the HITSC recommends: – The Initiative should begin its focus from the perspective of an EHR, including provenance for information created in the EHR (“source provenance”) and when it is exchanged between two parties. Provenance of the intermediaries is only important if the source data is changed. The notion of “who viewed/used/conveyed without modification along the way” is not important for provenance, as long as the information was not changed. 10

Data Elements Review Based on Task Force Recommendations of examining provenance within an EHR system: – Our current Use Case categorized Data Elements in the following roles: Start Point Transmitter Originator Assembler Composer – We will now review these roles and the Data elements to eliminate any of those that do not fall within the focus of the project based on the task force recommendations 11

Next Steps Join us for the System Requirements SWG – Friday February 27 th from 12:00-1:00 pm ET – Join us for the Information Interchange SWG – Wednesday March 4 th from 2:00-3:00 pm ET – Next All Hands meeting – Thursday, March 5, 2015 from 2:30 -3:30 pm ET –

Support Team and Questions Please feel free to reach out to any member of the Data Provenance Support Team: Initiative Coordinator: Johnathan Coleman: OCPO Sponsor: Julie Chua: OST Sponsor: Mera Choi: Subject Matter Experts: Kathleen Connor: and Bob Yencha: Support Team: – Project Management: Jamie Parker: – Standards Development Support: Perri Smith: and Atanu Sen: – Support: Apurva Dharia: Rebecca Angeles: and Zach May: 13