1. electronic Long-Term Services & Supports (eLTSS) Initiative All-Hands Workgroup Meeting April 16, 2015 1

2. Meeting Etiquette 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 o Hold = Elevator Music = frustrated speakers and participants This meeting is being recorded o 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. o Send comments to All Panelists so they can be addressed publically in the chat, or discussed in the meeting (as appropriate). o Please DO NOT use the Q&A—only the presenter sees Q&A, not necessarily the person facilitating the discussion From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute All Panelists 2

3. 3 Agenda TopicPresenterTimeframe Welcome Announcements eLTSS Roadmap Lynette Elliott10 mins Use Case Working Session: In & Out of Scope Assumptions Pre/Post-Conditions User Stories and Actors & Activities Activity Diagrams & Base Flows Becky Angeles Sweta Ladwa eLTSS Community 75 mins Homework / Next StepsBecky Angeles5 mins

4. Announcements HHS, CMS and ONC announced the release of the following on March 20, 2015: – Stage 3 Notice of Proposed Rulemaking (NPRM) for the Medicare and Medicaid Electronic Health Records (EHRs) Incentive Program Stage 3 Notice of Proposed Rulemaking (NPRM) for the Medicare and Medicaid Electronic Health Records (EHRs) Incentive Program specifies new criteria that EPs, EHs, and CAHs must meet to qualify for Medicaid EHR incentive payments proposes criteria that providers must meet to avoid Medicare payment adjustments based on program performance beginning in payment year 2018 – 2015 Edition Health IT Certification Criteria 2015 Edition Health IT Certification Criteria aligns with the path toward interoperability identified in ONC's draft shared Nationwide Interoperability Roadmap builds on past editions of adopted health IT certification criteria, includes new/updated IT functionality and provisions that support the EHR Incentive Programs care improvement, cost reduction, and patient safety across the health system – Comment period ends May 29, 2015 4

5. Announcements (continued) PUBLIC COMMENTS: You may submit comments, identified by RIN 0991-AB93, by any of the following methods (please do not submit duplicate comments). Because of staff and resource limitations, we cannot accept comments by facsimile (FAX) transmission. Federal eRulemaking Portal: Follow the instructions for submitting comments. Attachments should be in Microsoft Word, Microsoft Excel, or Adobe PDF; however, we prefer Microsoft Word. http://www.regulations.gov.http://www.regulations.gov Regular, Express, or Overnight Mail: Department of Health and Human Services, Office of the National Coordinator for Health Information Technology, Attention: 2015 Edition Health IT Certification Criteria Proposed Rule, Hubert H. Humphrey Building, Suite 729D, 200 Independence Ave, S.W., Washington, D.C. 20201. Please submit one original and two copies. Hand Delivery or Courier: Office of the National Coordinator for Health Information Technology, Attention: 2015 Edition Health IT Certification Criteria Proposed Rule, Hubert H. Humphrey Building, Suite 729D, 200 Independence Ave, S.W., Washington, D.C. 20201. Please submit one original and two copies. (Because access to the interior of the Hubert H. Humphrey Building is not readily available to persons without federal government identification, commenters are encouraged to leave their comments in the mail drop slots located in the main lobby of the building.) 5

6. Announcements (continued) 2015 Long Term Post Acute Care (LTPAC) & HIT Summit – What: The LTPAC HIT Summit is the premiere health IT conference for individuals within and working with the LTPAC industry for over 10 years. As the key conference of HIT leaders, policy makers, providers, vendors and professionals, the Summit continues to advance initiatives facing the long term, post acute care industry and priorities from the latest Roadmap for Health IT in LTPAC. – When: June 21-23, 8am-5pm ET – Where: Baltimore, MD in the Baltimore Hilton – To register: http://www.ahima.org/events/2015june-ltpac http://www.ahima.org/events/2015june-ltpac 6

7. Concert Series Presentations 7 Organizations are invited to present on an existing project or initiative that is related to the eLTSS scope of work and/or will help inform the eLTSS target outcomes and deliverables These projects do not have to be technically-focused Criteria for consideration: Has solution, whether it is technical or process driven, been implemented in a one or more of the eLTSS settings: home and community-based setting or clinical setting? Does solution incorporate existing or emerging standards and/or other relevant guidance?

8. Concert Series Presentations: Logistics Presentations will be scheduled as part of the weekly eLTSS Community Meetings and will occur the last 30 mins of the call Duration: 15-20 mins webinar (or demo); 5-10 mins Q&A eLTSS Workgroup activities will always take precedence over concert series presentations If you have an interest in participating, please contact Evelyn Gallego (evelyn.gallego@siframework.org ) and Lynette Elliott (lynette.elliott@esacinc.com)evelyn.gallego@siframework.orglynette.elliott@esacinc.com A pre-planning meeting will be scheduled prior to any public demonstration 8

9. Upcoming Concert Series Presentations 9 April 23 rd : Care at Hand April 30 th : State of Colorado May 7 th : Inofile / Kno2 May 14 th : State of Minnesota May 21 st : Harmony Information Systems May 28 th : (available)

10. Timelines for Consideration: Two Pilot Phases, SDO Ballot Cycles eLTSS Initiative Roadmap Q3 ‘14Q4 ‘14Q1 ‘15Q2 ‘15Q3 ‘15Q4 ‘15Q4 ‘17 Phase 4: Pilots & Testing Pilot site readiness Implementation of solution Test User Stories and Scenarios Monitor Progress & Outcomes Utilize Requirements Traceability Matrix Phase 5: Evaluation Evaluate outcomes against Success Metrics and Criteria Update Implementation Guidance Develop, review, and finalize the Use Case and Functional Requirements Pre-Planning Call for Participation Conduct Environmental Scan Success Criteria Stakeholder Engagement Finalize Candidate Standards Standards Gap Analysis Technical & Standards Design Develop Requirements Traceability Matrix Develop Implementation Guide Launch initiative Review and Finalize Charter Review initial Candidate Standards 10 Initiative Kick Off: 11/06/14 Phase 1: Pre-Discovery Phase 2: Use Case Development & Functional Requirements Phase 3: Standards & Harmonization

11. Goals for the eLTSS Initiative Identify key assessment domains and associated data elements to include in an electronic Long-term Services & Supports (eLTSS) plan Create a structured, longitudinal, person-centered eLTSS plan that can be exchanged electronically across and between community-based information systems, clinical care systems and personal health record systems. 11

12. Project Charter and eLTSS Glossary FINAL Published Project Charter located here: http://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Charter http://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Charter eLTSS Glossary posted here: http://wiki.siframework.org/eLTSS+Glossary http://wiki.siframework.org/eLTSS+Glossary – The eLTSS Glossary is a working document containing eLTSS-relevant terms, abbreviations and definitions as defined by stakeholders – We are looking for your feedback and comments Discussion Thread available Submit any change requests via the Change Request Form located on the wiki – Reminder: the Glossary is a living document and content may change as the initiative progresses 12

13. eLTSS Plan vs. eLTSS Record The S&I eLTSS leads and the eLTSS community defined the scope of this Initiative to the LTSS Plan because: The concept of a “LTSS record” is: – not defined and not specified in HIT standards – Would require work to define (time and money) – While potentially useful, even once defined, may not immediately result in something (information) that is exchangeable The concept of “LTSS plan” is: – narrower (than a record) – more easy to define (than the concept of a record) – more aligned w/ CMS requirements for a “person centered service plan” – more easy to link to available HIT standards 13

14. Beneficiary vs. Consumer vs. Individual CMS regulations refer to Beneficiary As noted in the eLTSS Project Charter: – “For the purpose of the eLTSS Initiative, beneficiary will refer to all individuals who are eligible for and receive LTSS benefits to include Medicaid. These beneficiaries are also referred to as recipients, consumers, persons, clients and individuals.” 14

15. Wk. Target Date (2015) All Hands WG Meeting Tasks Review & Comments from Community via Wiki page due following Tuesday by 8 P.M. Eastern 1-51/22-2/19 Use Case Kick-Off & UC Process Overview Use Case Value Framing Discussions Review and Answer Value Framing Questions on wiki 62/26 Review: Consolidated UC Value Framing Introduce: Context Diagram & User Stories Review: Context Diagram & User Stories 73/12Finalize: Context Diagram & User StoriesReview: User Stories 83/19Review: User Stories CommentsReview: User Stories, Glossary 93/26 Review: User Stories Introduce: Actors & Roles Review: User Stories, Actors & Roles 104/2 Finalize: Actors & Roles Introduce: In/Out of Scope Review: In/Out of Scope 114/9 Finalize: In/Out of Scope Introduce: Assumptions & Pre/Post Conditions Review: Assumptions & Pre/Post Conditions 124/16 Finalize: Scope, Assumptions & Pre/Post Conditions Introduce: Activity Diagram & Base Flow Review: Activity Diagram & Base Flow 134/23 Finalize: Activity Diagram & Base Flow Introduce: Functional Requirements & Sequence Diagram Review: Functional Requirements & Sequence Diagram 144/30 Finalize: Functional Requirements & Sequence Diagram Introduce: Data Requirements Review: Data Requirements 155/7Review: Data Requirements 165/14 Finalize: Finalize Data Requirements Introduce: Risks & Issues Review: Risks & Issues 175/21 Finalize: Risks and Issues Begin End-to-End Review End-to-End Review by community 185/28End-to-End Comments Review & dispositionEnd-to-End Review ends 196/4Finalize End-to-End Review Comments & Begin ConsensusBegin casting consensus vote 206/11Consensus Vote*Conclude consensus voting Proposed Use Case Development Timeline 15

16. We Need YOU! In order to stick to our timeline and to ensure that the artifacts we develop fit the need of our stakeholders (you), we need your feedback, comments and participation Each week, please review the use case content and provide comments via the wiki at: http://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Use+Case http://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Use+Case – Or email Becky Angeles directly at becky.angeles@esacinc.com with edits, comments or feedbackbecky.angeles@esacinc.com Discussions moving forward will be more technically (systems information and functionality, data sets/data elements, etc.). We encourage tech savvy individuals and teams to participate and provide input. 16

17. 17

18. 18

19. Next Steps HOMEWORK – Due by COB Tuesday, April 21st: –Review Use Case Content posted on the eLTSS Use Case –Utilize Comment Form at http://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Use+Casehttp://wiki.siframework.org/electronic+Long- Term+Services+and+Supports+%28eLTSS%29+Use+Case –Email feedback / comments to becky.angeles@esacinc.com or evelyn.gallego@siframework.orgbecky.angeles@esacinc.com NEXT WEEK: –Activity Diagram & Base Flow –Introduce Functional Requirements and Sequence Diagrams Join the eLTSS Initiative: http://wiki.siframework.org/eLTSS+Join+the+Initiative http://wiki.siframework.org/eLTSS+Join+the+Initiative –Included on the eLTSS distribution list –Committed Members can vote on artifacts 19

20. eLTSS Initiative: Project Team Leads ONC Leads – Elizabeth Palena-Hall (elizabeth.palenahall@hhs.gov)elizabeth.palenahall@hhs.gov – Patricia Greim (Patricia.Greim@hhs.gov)Patricia.Greim@hhs.gov CMS Lead – Kerry Lida (Kerry.Lida@cms.hhs.gov)Kerry.Lida@cms.hhs.gov Federal Lead – Jennie Harvell (jennie.harvell@hhs.gov)jennie.harvell@hhs.gov Community Leads – Andrey Ostrovsky (andrey@careathand.com)andrey@careathand.com – Nancy Thaler (nthaler@nasddds.org)nthaler@nasddds.org – Terry O’Malley (tomalley@mgh.harvard.edu)tomalley@mgh.harvard.edu Initiative Coordinator – Evelyn Gallego-Haag (evelyn.gallego@siframework.org)evelyn.gallego@siframework.org Project Management & Pilots Lead – Lynette Elliott (lynette.elliott@esacinc.com)lynette.elliott@esacinc.com Use Case & Functional Requirements Development – Becky Angeles (becky.angeles@esacinc.com)becky.angeles@esacinc.com Standards Development Support – Angelique Cortez (angelique.j.cortez@accenture.com)angelique.j.cortez@accenture.com Harmonization – Atanu Sen (atanu.sen@accenture.com)atanu.sen@accenture.com 20

21. 21

22. Scope Further defines the scope of the Use Case itself and NOT the scope of the Initiative Diagrams and other supplemental data / examples help provide context and clarify the basis for the Use Case 22

23. Scope Subsections Background – describes the relevance of the Use Case in relation to what gaps currently exist within the healthcare industry. Includes all policy and/or regulatory issues/dependencies that may impact the Use Case In Scope – indicates what is in scope for the Use Case. For example, the type of transactions, the information/data to be exchanged, and specific aspects that need to be in place to enable the information to be sent, received and understood the same at both ends of the transmission. Out of Scope – indicates what is out of scope for the Use Case. These points may highlight dependencies on the feasibility, implementability, and usability that result in limitations of the Use Case. At a high level, whatever is not declared “In Scope” is by definition, “Out of Scope”. – Note: Items that are out of scope for the Use Case, Functional Requirements and Standards Harmonization activities can be still be part of a Pilot. Communities of Interest 23

24. Assumptions Outlines what needs to be in place to meet or realize the requirements of the Use Case (i.e. the necessary privacy and security framework) Functional in nature and state the broad overarching concepts related to the Initiative Serve as a starting point for subsequent harmonization activities 24

25. Pre-Conditions Conditions that must exist for the implementation of the eLTSS Plan creation and sharing Describe 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 the information exchange as described by the Functional Requirements and Dataset requirements 25

26. Post-Conditions Describe the state of the system, from a technical perspective, that will result after the execution of the operation, process activity or task 26

27. Activity Diagram An Activity Diagram is a action state transition diagram – 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 events and information between the actors Displays the main events/actions that are required for the data sharing and the role of each system in supporting the sharing 27

28. Base Flow The Base Flow is the step by step process of the information sharing depicted in the activity diagram Indicates the actor who performs the action, the description of the event/action, and the associated inputs (records/data required to undertake the action) and outputs (records/data produced by actions taken) 28