Data Access Framework (DAF) Use Case Kickoff

1. Data Access Framework (DAF)Use Case Kickoff August 7, 2013

2. Meeting Etiquette From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute  All Panelists • Remember: If you are not speaking, please 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 = frustrated speakers and participants • This meeting is being recorded • Another reason to keep your phone on mute when not speaking • Use the “Chat” feature for questions, comments and items you would like the moderator or other participants to know. • Send comments to All Panelists so they can be addressed publically in the chat, or discussed in the meeting (as appropriate).

3. Agenda Update me

4. Welcome and Announcements Update me Please check the meeting schedule weekly as the meeting link and call in numbers will change. • Data Access Framework (DAF) Initiative holds weekly community meetings on Thursdays at 3:25 pm EST. • Due to the HIMSS conference, the meeting scheduled for Thursday, March 4 is CANCELLED. • Next meeting is scheduled for March 14, 2013. • Please see the DAF Wiki Page for meeting information • http://wiki.siframework.org/Structured+Data+Capture+Initiative

5. ReminderVote on the DAF Project Charter Voting form is on the DAF Project Charter Page http://wiki.siframework.org/Structured+Data+Capture+Charter+and+Members • IMPORTANT • Only Committed Members may vote on the Project Charter. • Each Organization, no matter the number of Committed Members only receives 1 Vote. If there are multiple committed members from your organization please verify your collective vote with them. Update me For more information on the S&I Framework Consensus Process, see http://wiki.siframework.org/S%26I+Steering+and+Consensus+Process Consensus voting OPENS on ________. Consensus voting CLOSES on _______.

6. Notional Project Timeline S&I Lifecycle (Discovery  Pilot & Evaluation) Jan 2014 July 2013 Sept Nov Pre-Discovery, Call for Participation Kick-off (7/16) Use Case 1 Consented 10/22 Technical Project Outline (11/14) UC 1: Local Data Access: Intra-Organizational Query Discovery Implementation Harmonized Specifications Standards Gap Analysis Define Use Case & Functional Requirements Charter Review & Consensus Technology Evaluations Use Case 2 Consented 11/29 UC 2: Targeted Data Access: Inter-Organizational Query Implementation Discovery Define Use Case & Functional Requirements Standards Gap Analysis

7. S&I FrameworkData Access Framework Initiative Update me Use Case & Functional Requirements Kickoff Meeting 2/28/13

8. Agenda Update me

9. Use Case Development in the S&I Framework NwHIN Exchange Operations S&I Framework S&I Pilots ATCBs and Testing Infrastructure Update me S&I Framework NWHIN Implementation & Pre-Certification Testing eHealth Exchange Use Cases Standards Development Harmonization Federal Responsibility Joint Efforts Private Sector

10. Use Case Development Objectives • Engage Stakeholders as Committed Members, Invited Experts, or Interested Parties in the creation of a Use Case • Identify a Use Case and User Stories that address real-world problems • 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 • Establish the Use Case and supporting artifacts in a reusable fashion to support future health information interchange Initiatives

11. Use Case OutlineTailored for each Initiative • 7.0 Scenario: Generic Provider Workflow • 7.1 User Story 1, 2, x, … • 7.2 Activity Diagram • 10.2.1 Base Flow • 10.2.2 Alternate Flow • 7.3 Functional Requirements • 10.3.1 Information Interchange Requirements • 10.3.2 System Requirements • 7.4 Sequence Diagram • 8.0 Dataset Requirements • 9.0 Risks, Issues and Obstacles • Appendices • Related Use Cases • Previous Work Efforts • References • 1.0 Use Case Scope • 1.1 Background** • 1.2 In Scope • 1.2 Out of Scope • 1.3 Stakeholders** • 2.0 Value Statement** • 3.0 Use Case Assumptions • 4.0 Pre-Conditions • 5.0 Post Conditions • 6.0 Actors and Roles Hema – please verify correctness ** Leverage content from Charter

12. Use Case Development Process Hema to update

13. Review of Key Use Case SectionsDefining the Actors • This section of the Use Case outlines the business actors that are participants in the information exchange requirements for each scenario. A business actor is a person or organization that directly participates in a scenario. Thus, as a person or organization, the actor can (and should) be a stakeholder. • The business actor must use a system to perform the functions and to participate in the information interchange. The system or system actor has roles (send, receive, publish, subscribe or in some cases display) and actions which involve exchanging content. Please see the table below for an example of these designations. • NOTE: A Business Actor may be a Stakeholder and also can have more than one role. DAF Example

14. Review of Key Use Case SectionsUse Case Diagrams • The Use Case and Context Diagrams conceptually represents the Business Actors interacting with the Use Case and the User Stories • These diagrams characterize the types of interactions that an actor has with a specific system • The section can include a Use Case Diagram and, if applicable, a Context Diagram (examples are shown below) • The Use Case diagram shows the association and interaction between the business actors and the Use Case • It provides an overview of the actors (users or external systems), Use Cases, and the interactions between them • The context diagram uses inputs and outputs to provide a pictorial representation of the environment, both internal and external, where the exchange takes place • As the UML associated with the diagrams proceeds through the different S&I Framework functions (i.e., Harmonization, Reference Implementation), it is defined at a more granular level closer to the coding (implementation). • Example of Use Case Diagram Update me

15. Local Data Access Workstreamvia Intra-Organizational Query DAF - Local Data Access Workstream via Intra-Organizational Query Scenario Example: Information Requester sends a data query to his/her Internal Information System requesting information about one or more patient(s). The Internal Information System returns the requested patient data or document to the Information Requester. Organization Entity A Internal Information System Information Requester Sends: Data Query Receives: Patient(s) Data or Document 15

16. Targeted Data Access Workstreamvia Inter-Organizational Query Scenario Example: Originating Request System from Org A sends a data query to a known external organization requesting information for a known patient to Data Source System from Org B. The Data Source System from Org B returns the requested patient data or document to the Originating Request System in Org A. Organization Entity A Organization Entity B Originating Request System Data Source System Sends: Data Query Firewall Receives: Patient(s) Data or Document

17. Data Access Framework – Context Diagram Actors & Roles Context Diagrams Local Data Access Targeted Data Access

18. Review of Key Use Case SectionsScenarios • The scenario is a comprehensive description of the actors, interactions, activities, and requirements associated with the information exchange • It is a prototypical sequence of interactions in a business collaboration or the application context • Scenarios pertain to supporting the health information exchange and, describing key flows, and are supplemented by User Stories Update me

19. Review of Key Use Case SectionsUser Story • User Stories summarize the interaction between the actors of the Use Case, and specify what information is exchanged from a contextual perspective • Furthermore, the User Stories describe the real world application as an example of the Scenario • These interactions are further described in subsequent sections. Historically, user stories have been utilized to provide clinical context. Update me

20. Review of Key Use Case SectionsActivity Diagram • An Activity Diagram is a special form of a state transition diagram in which all or most of the states are activity states or action states • An action state represents the fulfillment of associated responsibilities in response to the communication received from the previous step • Most transitions are triggered by completion of activities in the source states • The Activity Diagram illustrates the Use Case flows graphically, and represents the flow of events and information between the actors • It also displays the main events/actions that are required for the data exchange and the role of each system in supporting the change • Example of Activity Diagram Update me

21. DAF Activity Diagram Update me

22. Review of Key Use Case SectionsSequence Diagram • A Sequence Diagram is primarily used to show the interactions between objects in the sequential order that they occur • This representation can make it easy to communicate how the exchange works by displaying how the different components interact • The primary use of the diagram is in the transition from requirements expressed as use cases to the next and more formal level of refinement • Note: Horizontal lines are used to identify the specific activity between the systems • Example of DAF Sequence Diagram on next slide Update me

23. DAF Sequence Diagram Update me

24. Review of Key Use Case SectionsFunctional Requirements • Functional Requirements identify the capabilities a system in a role must have in order to enable interoperable exchange of the healthcare data of interest • They provide a detailed breakdown of the requirements in terms of the intended functional behaviors of the application • The Functional Requirements include: • Information Interchange Requirements • System Requirements • Dataset Requirements • Detailed descriptions of requirement types on next slides Update me

25. Review of Key Use Case SectionsFunctional Requirements • The Information Interchange Requirements define the system’s name and role. They also specify the actions associated with the actual transport of content from the sending system to the receiving system • System Requirements include the requirements internal to the system necessary to participate successfully in the transaction. System requirements may also detail a required workflow that is essential to the Use Case • Dataset Requirements • Include the data elements and data element sets that will be available within the message or document. Each data element included is necessary for some aspect of the Use Case; however, the requirements do not specify exactly how they may be used together. All data element sets may contain multiple data elements unless otherwise stated. • The identification of data elements forms the foundation for harmonization activities. The data elements identified in the Use Case set constraints on the contents of documents and messages. • NOTE: This content of this section will vary per Initiative as the references are contingent upon the specific list of Functional Requirements that is developed by the Workgroup. The Use Case Simplification Workgroup is tasked with creating a structure for this section that will eventually be applied to all Use Cases. Data element sets are defined for reuse within the Use Case Simplification Workgroup Update me

26. S&I Community Enabling Toolkit (CET)Use Case Overview

27. Previous and Ongoing S&I Use Cases

28. Agenda Update me

29. Data Access Framework InitiativeProposed Use Case & Functional Requirements Development Timeline Update me

30. Agenda Update me

31. DAF Initiative Conceptual Workflow Update me • Word document

32. DAF Use Case Approach Update me Use Case Scope • The full diagram below highlights an overall picture of the full DAF workflow • The DAF Use Case itself will only focus on generic functionality outlined below and the exchanges in scope for standardization

33. Agenda Update me

34. DAF Use Case Context Diagram Update me • Word document

35. Agenda Update me

36. DAF Use Case Assumptions Update me • Word document

37. Agenda Update me

38. Next Steps for DAF Use Case...! Update me • Next week is cancelled for HIMSS – • DAF Initiative Meet and Greet on Tuesday 3/5/13 • Accenture Booth Meeting Room (Booth #4331) from 5:00 – 5:30 pm • S&IFramework Wide Meet & Greet Tuesday 3/5/13 • Wolfe's in the Warehouse Bar at the Marriott a block down from the Convention Center starting at 5:30 • Review content & submit comments by Tuesday 3/12 COB • Context Diagram • Assumptions • Wiki link: http://wiki.siframework.org/Structured+Data+Capture+Use+Case • Attend our next session on Thursday 3/14 to discuss... • Pre & Post Conditions • User Stories

39. Data Access Framework InitiativeProposed Use Case & Functional Requirements Development Timeline Update me

40. Next Steps Update me Update me • HOMEWORK: Committed Members VOTE on the Project Charter: • http://wiki.siframework.org/Structured+Data+Capture+Charter+and+Members • Next Work Group Meeting • March 7, 2013 Meeting is CANCELLED • Next Meeting is Thursday, March 14, 2013 from 3:30pm - 4:30pm Eastern • http://wiki.siframework.org/Structured+Data+Capture+Initiative • Reminder: All DAF Announcements, Meeting Schedules, Agendas, Minutes, Reference Materials, Use Case, Project Charter and general information will be posted on the DAF Wiki page • http://wiki.siframework.org/Data+Access+Framework+Homepage

41. Next Steps – Getting Started Update me • Details on the Data Access Framework launch including this presentation are posted on the wiki: http://wiki.siframework.org/Data+Access+Framework+Homepage • Please feel to review and comment on the Proposed Project Charter • To review the Data Access Framework Project Charter go to the Charter wiki page: http://wiki.siframework.org/Data+Access+Framework+Charter+and+Members • Complete the Data Access Framework Project Charter Comment Form: http://wiki.siframework.org/Data+Access+Framework+Charter+and+Members(you will need to select the “Click Here to Provide Comments” in the Project Charter Comments Section) • Join us for our next meeting July 24th, 2013 from 12-1 pm EST • All meeting updates, call in number and web meeting details can be found here: http://wiki.siframework.org/Data+Access+Framework+Homepage

42. Resources and Questions • Please feel free to reach out to any member of the Data Access Framework Initiative team: • Initiative Coordinator: • John Feikema: john.feikema@siframework.org • ONC Sponsors • Mera Choi: mera.choi@hhs.gov • Support Team: • Project Management: Jamie Parker jamie.parker@esacinc.com and Gayathri Jayawardena gayathri.jayawardena@esacinc.com • Technical Support: Dragon (Nagesh) Bashyam nagesh.bashyam@drajer.com • Use Case Development: Presha Patel presha.patel@accenture.com • Vocabulary and Terminology Subject Matter Expert: Mark Roche mrochemd@gmail.com