Longitudinal Coordination of Care (LCC) Workgroup (WG)

1. Longitudinal Coordination of Care (LCC) Workgroup (WG) Review of HITPC MU Stage 3 Request For Comments (RFC) January 08, 2013

2. Overview • S&I Longitudinal Coordination of Care (LCC) Overview • Key Accomplishments of the LCC WG • Care Plan & Meaningful Use • Health IT Policy Committee (HITPC) MU3 Request for Comment (RFC) • RFC Care Plan Questions • S&I LCC WG Care Plan Considerations • Summary & Discussion • Next Steps: • Expanded collaboration and participation

3. S&I Longitudinal Coordination of Care (LCC) Workgroup • Initiated in October 2011 as a community-ledinitiative with multiple public and private sector partners, each committed to overcoming interoperability challenges in long-term, post-acute care (LTPAC) transitions • Supports and advances interoperable health information exchange (HIE) on behalf of LTPAC stakeholders and promotes LCC on behalf of medically-complex and/or functionally impaired persons • Goal is to identify standards that support LCC of medically-complex and/or functionally impaired persons that are aligned with and could be included in the EHR Meaningful Use Programs • Seeks to influence Meaningful Use Stage 3 • Consists of three sub-workgroups (SWGs): • Longitudinal Care Plan (LCP) • LTPAC Care Transition • Patient Assessment Summary (PAS)

4. LCC Sub Workgroups (SWG) Longitudinal Coordination of Care Workgroup COMMUNITY-LED INITIATIVE • Providing subject matter expertise and coordination of SWGs • Developing systems view to identify interoperability gaps and prioritize activities, and align identified standards with the EHR MU Program Longitudinal Care Plan SWG LTPAC Care Transition SWG Patient Assessment Summary (PAS SWG • Identify standards for an interoperable, longitudinal care plan which aligns, supports and informs person-centric care delivery regardless of setting or service provider • Identify the key business and technical challenges that inhibit LTC data exchanges • Define data elements for long-term and post-acute care (LTPAC) information exchange using a single standard for LTPAC transfer summaries • Engage directly with HL7 to establish the standards for the exchange of patient assessment summary documents • Inform the development of the Keystone Beacon PAS Document Exchange GOALS *Care Plan will enable providers to create, transmit and incorporate goals, objectives, and outcomes for the benefit of medically complex and/or functionally impaired individuals, their families and caregivers.

5. Key Accomplishments • LCC Use Case. Outlines three scenarios for health information exchanges between LTPAC and acute care settings • LCC Whitepaper. Meaningful Use Requirements For: Transitions of Care & Care Plans For Medically Complex and/or functionally Impaired Persons. • Transitions of Care Data Set. Developed 480+ data elements needed by receiving clinicians to safely and appropriately care for patients at times of transitions of Care. • Stage 2 MU C-CDA Refinements. Supported and advanced, with HL7, refinements to C-CDA for interoperable exchange of Functional Status, Cognitive Status, & Pressure Ulcer • HL7 Balloted Patient Assessment IGs (avail. DEC2012) • CDA R2 Questionnaire Assessment • Consolidated CDA LTPAC Summary (formerly Patient Assessment Summary)

6. CARE PLANS & MU Bill Russell drbruss@gmail.com

7. Why Exchange of a Care Plan is Important • The S&I LCC WG believes that: • The exchange of a care plan is needed to support coordination and continuity of care, particularly on behalf of medically complex/functionally impaired persons; and • The concept of “Care Plan” and its component parts needs to be unambiguously defined for interoperable exchange. • The LCC WG has been considering advancing to the HITPC recommendations that MU3 include requirements for the interoperable exchange of a care plan and component parts We need your input on care plan components necessary to support Transitions of Care and Coordination of Care.

8. Information Exchange Needs to Support Transitions and Coordination of Care • HIE at times of transition in care (ToC) and referrals in care is critically important to support care coordination, particularly on behalf of medically complex/functionally impaired persons • MU2 requirements identify some required data elements that should be included in Summary Care Records at times of ToC and referrals in care

9. MU2 Requirements and Exchange of Care Plan Content MU2 includes requirements related to the exchange of care plans: • Care plan content, if known, is required in the Summary Care Record for each transition of care or referral • Care plan content required in the Summary Care Record includes: • Care plan field, including goals and instructions. • Care team including the primary care provider of record and any additional know care team members beyond the referring or transitioning provider and the receiving provider.

10. MU2 Requirements and Exchange of Care Plan Content cont. The MU Stage 2 Final Rule also provides the following definition of “Care plan”: For purposes of the clinical summary, we define a care plan as the structure used to define the management actions for the various conditions, problems, or issues. A care plan must include at a minimum the following components: problem (the focus of the care plan), goal (the target outcome) and any instructions that the provider has given to the patient. A goal is a defined target or measure to be achieved in the process of patient care (an expected outcome) (page 54001).

11. Health IT Policy Committee • MU3 Request for Comment • Jennie Harvell, ASPE • Jennie.harvell@hhs.gov

12. HITPC MU 3 RFC – Care Plans • In section SGRP 304, four questions are posed related to Care Plans: • How might we advance the concept of an electronic shared care planning and collaboration tool that crosses care settings and providers, allows for and encourages team based care, and includes the patient and their non-professional caregivers? • What are the most essential data elements to ensuring safe, effective care transitions and ongoing care management? • How might sharing key data elements actually improve the communication? Consider health concerns, patient goals, expected outcomes, interventions, including advance orders, and care team members. • What data strategy and terminology are required such that the data populated by venue specific EHRs can be exchanged? How might existing terminologies be reconciled?

13. LCC WG Care Plan Considerations • To help frame responses to the RFC, the LCC WG has developed definitions for key terms, structure, and components of a care plan to support transitions in and coordination of care • These terms/components apply to both the ‘care plan’ and ‘plan of care’: • Health concern • Goals • Instructions • Interventions • Outcomes • Team member

21. Exchange of Care Plan & MU Standards

22. Summary & Discussion • Jennie Harvell, ASPE • Jennie.harvell@hhs.gov

23. Summary & Discussion • The S&I LCC WG anticipates advancing to the HITPC recommendations that MU Stage 3 include requirements for the interoperable exchange of care plans and component parts: • Health concerns • Goals • Instructions • Interventions • Outcomes • Team member WE WANT TO HEAR FROM YOU! LET’S DISCUSS…

24. NEXT STEPS

25. Participate & Collaborate! • We welcome your thoughts on the need for these care plan concepts and definitions as a way to respond to the HITPC RFC due January 14 2013 • Please share with us! • Evelyn Gallego-Haag, S&I LCC Initiative Coordinator at evelyn.gallego@siframework.org • Becky Angeles, S&I LCC Support, rebecca.angeles@esacinc.com S&I Longitudinal Coordination of Care Workgroup http://wiki.siframework.org/Longitudinal+Coordination+of+Care

26. Appendix: SUBMITTING RFC COMMENTS

27. Comments will only be accepted electronically • Follow the “Submit a comment” instructions at http://www.regulations.gov • Attachments should be in Microsoft Word or Excel, WordPerfect, or Adobe PDF • HIT PC requests that duplicate comments not be submitted

28. Search for "Office of the National Coordinator for Health Information Technology; Health Information Technology; HIT Policy Committee: Request for Comment"

29. Enter identification information • Type comments • Upload files • Submit comments

30. Appendix: HITPC RFC – CARE PLANS