electronic Long-Term Services & Supports (eLTSS) Initiative All-Hands Workgroup Meeting October 8,
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 Agenda TopicPresenterTimeframe Welcome Announcements eLTSS Roadmap Lynette Elliott10 mins eLTSS Pilots Kick OffJamie Parker50 mins
Announcements: Interoperability Roadmap Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap version 1.0 – What: This draft interoperability roadmap lays out a clear path to catalyze the collaboration of stakeholders who are going to build and use the health IT infrastructure. It focuses on three key areas for interoperability: Drivers, Policy and Technical Components, and Outcomes. These documents include all the public comments that were submitted during the public comment period. – Roadmap Website: researchers-implementers/interoperabilityhttps:// researchers-implementers/interoperability 4
Announcements: CMS and ONC Health IT Regulations On Oct. 6, 2015 CMS and ONC released final rules: – CMS Meaningful Use Modifications/Stage 3 Rule /medicare-and-medicaid-programs-electronic-health- record-incentive-program----stage-3-and – ONC 2015 Edition Health IT Certification Rule /2015-edition-health-information-technology- certification-criteria-2015-edition-base-electronic 5
Announcements: ONC Rule: Common Clinical Data Set Renamed the “Common MU Data Set.” This does not impact 2014 Edition certification. Includes key health data that should be accessible and available for exchange. Data must conform with specified vocabulary standards and code sets, as applicable. 6 Patient nameLab tests SexLab values/results Date of birthVital signs (changed from proposed rule) RaceProcedures EthnicityCare team members Preferred languageImmunizations ProblemsUnique device identifiers for implantable devices Smoking StatusAssessment and plan of treatment MedicationsGoals Medication allergiesHealth concerns Send, receive, find and use priority data domains to improve health and health quality ONC Interoperability Roadmap Goal Red = New data added to data set Blue = New standards for data
Announcements, cont’d… National Call for Applications Opens: Community Health Peer Learning Program – What: In July 2015 the Office of the National Coordinator for Health Information Technology (ONC) has awarded AcademyHealth $2.2 million to lead the Community Health Peer Learning Program (CHP). Throughout this two-year program, AcademyHealth will work in partnership with ONC to establish a national peer learning collaborative for 15 competitively-awarded communities to address specified population health management challenges through increased sharing and use of data. – When: Application Due Date November 10, 2015 ~ Anticipated Award Date January 8, 2016 – For more information: &navItemNumber= &navItemNumber=17093 – To apply: 7
Announcements, cont’d.. Aging 2.0’s AgeTech Expo – Charting the Course: Innovations in Aging – What: The Aging2.0 AgeTech Expo brings together aging services providers and tech companies for cross-sector innovation insights and collaboration opportunities. The 2-day conference and technology exposition features innovation tours and workshops, inspiring keynotes, practical education panels, technology exhibits and the live “Pitch-for-Pilots (P4P)” session. – When: November 19-20, 2015 – Where: Hyatt Regency Hotel ~ San Francisco, CA – For more information: – To register: 8
Announcements, cont’d… mHealth Summit – What: The 2015 mHealth Summit explores what is new in mobile, telehealth and connected health—from the impact on healthcare delivery, clinical care and patient/consumer engagement to new technologies, research, investment activities, policy and shifts in the business environment. – When: December 8 – December 11, 2015 – Where: Gaylord National Resort and Convention Center ~ Washington, D.C. – To register: 9
eLTSS Initiative Timeline 10 Phase 1 Pilots & Testing … Pilot Guide Development Use Case & Functional Requirements Pre-Discovery DEC 14JUNJAN FEBMAYJULAUGSEPOCTNOV Kick Off 11/06/14 Evaluation... Content Work Stream Content Work Stream eLTSS All-Hands Work Group Use Case 1. eLTSS Use Case eLTSS Plan Content SWG 1.eLTSS Plan Domains & Data Elements Pilot Guide Development 1.Candidate Standards & Technologies 2.Three-tiered implementation Approach 3.Functional Requirements Matrix MARAPRDEC 15JAN 16 Pilot Execution
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
eLTSS Artifacts Final published Project Charter is located here: Term+Services+and+Supports+%28eLTSS%29+Charter Term+Services+and+Supports+%28eLTSS%29+Charter eLTSS Glossary posted here: – 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 Final published Use Case document is located here: – Term+Services+and+Supports+%28eLTSS%29+Use+Case Term+Services+and+Supports+%28eLTSS%29+Use+Case 12
13
Aim for S&I Pilot Programs Bring awareness to national standards addressing existing or emerging interoperability gap Organize and guide the deployment of Pilot projects to test the suitability of the Initiative specifications including those identified in the Use Case and Functional Requirements Matrix Provide tools and guidance for executing, managing and evaluating the Pilot Create a forum to share lessons learned and best practices Conduct Real world evaluation of : – The eLTSS Use Case – eLTSS Functional Requirements Matrix – Pilot Guide 14 The goal is to determine if the work we have done to date is implementable? Useable? And if not what else needs to be done
Pilot Process: How will we get to our goal? 1.Kick Off (today’s call) 2.Completion of the Pilot Design Template Presentation – TEFT States will work with Technical Assistance Team to Complete – Non-TEFT States will be sent a draft of this presentation for completion and review 3.Presentation of Pilot to the larger eLTSS community 4.Begin work on the Requirements Traceability Matrix 5.Attend Thursday Community Calls and provide updates 6.Complete Pilot 7.Prepare a “Lesson’s Learned” and pilot close out presentation 15 Steps 1, 2, 3 Steps 4 Step 7 Steps 6 Steps 5 OctNovDecJan ’16FebMarch April (round 1 complete)
Pilot Activities and Artifacts Kick Off and Pilot Presentations Kick Off Pilots Review Pilot Design Presentation Pilots complete the Pilot Design Presentation Pilot sites present Pilot Design to the community Pilot Design PowerPoint Presentation Executing the Pilot Completing the Tier 1 Requirements Traceability Matrix (RTM) Attending Community meetings and updating the group on progress Working with Technical Assistance and ONC support teams to identify challenges Work through the RTM Finalize Pilot Submit Final RTM Attend Community Calls and update on progress and completion Present a Final “Lessons Learned” presentation to the community identifying successes, challenges and areas for improvement Determine next steps/tier to pilot for round 2 Completed RTM “Lessons Learned” presentation Evaluate Pilots & Update Standards Review Pilot Performance Compile recommendations Identify gaps in standards based on pilot feedback Update Functional Requirements and Use Case as necessary based on feedback Prepare for round 2 pilots Executive summary on pilot outcomes including recommendations Updates to Use Case and Functional Requirements Steps Activities Artifacts ~5 months ~1 month
Keeping Pilots Organized… “Where to Start?” The Pilots wiki page Term+Services+and+Supports+%28eLTSS%29+ Pilots Term+Services+and+Supports+%28eLTSS%29+ Pilots 1.Section for “Meeting Schedule” – As we move into the Holiday season we will keep this section updated with meetings at a glance for at least 3 weeks out 2.Section called “Pilots Starter Kit” – Contains all of the materials you will need to produce as part of the pilot process (RTM, Pilot Slide Deck etc.) 3.Section for “Resource Materials” – This includes materials which help with the context of pilots and the overarching goals (i.e. Pilot Overview)
Starter Kit: Pilot Plan The Pilot Plan is a PowerPoint template that provides each pilot site the opportunity to introduce their pilot to the community. – Pilot Plan is used to help set the foundation for each pilot including pilot logistics, timeline, team members, larger eco-system, success metrics and additional items for consideration – Goal is to have each pilot (TEFT and Non-TEFT) present their respective pilot plans during a community call during the month of October – Pilot Plan PPT Template Pilot Plan PPT Template Pilot Plan is an artifact that supports the piloting process and assists the Initiative Support team in identifying risks, challenges and gaps 18
Starter Kit: Requirements Traceability Matrix Requirements Traceability Matrix (RTM) for Tier 1 is a way to methodically validate the Use Case and The Functional Requirements Document – Tier 2 and 3 under development 19 Copied from the Functional Requirements Matrix Term+Services+and+Supports+%28eLTSS%29+Pilot +Guidance Term+Services+and+Supports+%28eLTSS%29+Pilot +Guidance Translates to: Requirements Traceability Matrix: Term+Services+and+Supports+%28eLTSS%29+Pilots (Starter Kit) Term+Services+and+Supports+%28eLTSS%29+Pilots
Tentative Meeting Schedule: Meeting DateTopicPresentersArtifact October 8 th Pilot Kick offPilot Support TeamPilot Kick Off October 15 th Pilot Presentations- Non TEFT TBDPilot Presentations October 22 nd Pilot Presentations Non TEFT TEFT States TBDPilot Presentations October 29 th Final Pilot Presentation Meeting TEFT States Additional Pilots TBDPilot Presentations November 5 th Pilot Updates and Working Session Deep Dive on Pilot Logistics and Success Metrics Pilots and support team Pilot Logistics Success Metrics November 12 th Pilot Updates and Working Session on RTM Completion (Activities and Roles) Pilots and support team Pilot Updates November 19 th Pilot Updates and Working Session (Domains supporting identified activities and roles) Pilots and Support Team Pilot Updates 20
Next Steps Begin work on the Pilot Plan Presentation Pilot presentations will be held during community calls – Oct 15 th – Oct 22 nd – Oct 29 th – Please pick a time and or any member of the support team your preferred time to present and we will schedule – Non-TEFT state pilots will be asked to present first so that they can be available to support the states If you are interested in piloting, please express your interest using the Pilot Interest Survey form: – orts+Pilot+Interest+Survey orts+Pilot+Interest+Survey 21
Comments/Discussion 22
eLTSS Initiative: Project Team Leads ONC Leadership – Mera Choi – Elizabeth Palena-Hall CMS Leadership – Kerry Lida Community Leadership – Mary Sowers – Terry O’Malley Initiative Coordinator – Evelyn Gallego-Haag Project Management – Lynette Elliott Use Case & Functional Requirements Development – Becky Angeles Pilot Guide Development – Grant Kovich Pilots Management – Jamie Parker Standards and Technologies Identification – Angelique Cortez 23