1. Electronic Submission of Medical Documentation (esMD) eDoC eClinical Templates on FHIR using Structured Data Capture Use Case May 27, 2015

2. Meeting Etiquette Please announce your name each time prior to making comments or suggestions during the call Remember: If you are not speaking keep your phone on mute Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call –Hold = Elevator Music = very frustrated speakers and participants This meeting, like all of our meetings, is being recorded –Another reason to keep your phone on mute when not speaking! Feel free to use the “Chat” or “Q&A” feature for questions or comments NOTE: This meeting is being recorded and will be posted on the esMD Wiki page after the meeting From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute 2

3. Agenda 3 TopicPresenter AnnouncementsSweta Ladwa eDoC Templates on FHIR using Structured Data Capture -Use Case -Use Case Assumptions -Pre-Conditions -Post-Conditions -Actors and Roles -Use Case Context Diagram Sweta Ladwa

4. Schedule- This Week Wednesday, 2-3 PM ET - CANCELLED -HL7 CDP 1 IG Ballot Reconciliation Meeting Friday, 2-3 PM ET -HL7 CDP 1 IG Ballot Reconciliation Discussion

5. eDoC eClinical Templates on FHIR Use Case Timeline Wk Target Date (2015) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page due following Monday by 8 P.M. Eastern 15/6 Use Case Kick-Off & UC Process Overview Introduce: Preface, Introduction, Initiative Overview Review Preface, Introduction, Initiative Overview, Initiative Challenge Statement 25/13 Finalize: Preface, Introduction, Initiative Overview Introduce: Initiative Challenge Statement, Use Case Scope (Background, In Scope, Out of Scope, Communities of Interest), Value Statement Review: Use Case Scope (Background, In Scope, Out of Scope, Communities of Interest), Value Statement 35/20 Finalize: Use Case Scope (Background, In Scope) Introduce: Use Case Scope (Out of Scope, Communities of Interest), Value Statement, Use Case Assumptions, Pre-Conditions, Post- Conditions Review: Use Case Assumptions, Pre-Conditions, Post- Conditions, Actors and Roles 45/27 Finalize: Use Case Scope (Out of Scope, Communities of Interest), Value Statement Introduce: Use Case Assumptions, Pre-Conditions, Post- Conditions,Actors and Roles, Use Case Context Diagram Review: Use Case Assumptions, Pre-Conditions, Post- Conditions,Actors and Roles, Use Case Context Diagram 56/3 Finalize: Use Case Assumptions, Pre-Conditions, Post-Conditions, Actors and Roles, Use Case Context Diagram Introduce: Use Case Diagram, Scenario, User Story, Activity Diagram, Base Flow Review: Use Case Diagram, Scenario, User Story, Activity Diagram, Base Flow 66/10 Finalize: Use Case Diagram, Scenario, User Story, Activity Diagram, Base Flow Introduce: Functional Requirements, Information Interchange Requirements, System Requirements, Risks/Issues/Obstacles Review: Functional Requirements, Information Interchange Requirements, System Requirements, Risks/Issues/Obstacles 76/17 Finalize: Functional Requirements, Information Interchange Requirements, System Requirements, Risks/Issues/Obstacles Introduce: Dataset Requirements 1 Review: Dataset Requirements 1 86/24 Finalize: Dataset Requirements 1 Introduce: Dataset Requirements 2 Review: Dataset Requirements 2 97/1 Finalize: Dataset Requirements 2 Introduce: Dataset Requirements 3 Review: Dataset Requirements 3 107/8 Finalize: Dataset Requirements 3 Begin End-to-End Review End-to-End Review by Community 117/15 Review End-to-End Comments and Dispositions Begin Consensus Consensus Voting by Community 127/22Continue ConsensusConsensus Voting by Community 137/29Review Consensus Comments and DispositionsConclude Consensus

6. Review of Key Use Case Sections Assumptions, Pre-Conditions, Post- Conditions Assumptions –Outlines what needs to be in place to meet or realize Use Case requirements –Functional in nature and state broad overarching concepts related to the Initiative –Serve as a starting point for subsequent harmonization activities Pre Conditions –Describes the state of the system, from a technical perspective, that must be true before an operation, process, activity or task can be executed –Lists what needs to be in place before executing information exchange as described by Functional Requirements and Dataset requirements Post Conditions –Describes the state of the system, from a technical perspective, that will result after the execution of the operation, process activity or task 6