Meaningful Use Personal Pace Education Module: Transitions of Care.

Slides:



Advertisements
Similar presentations
Meaningful Use and Health Information Exchange
Advertisements

How To Get To The Winners Circle with Your Patient Portal; Our Challenges To Get To The Finish Line. Julie Patterson, Baptist Health Carey Ronan, MHA,
2014 Edition Release 2 EHR Certification Criteria Final Rule.
Connecticut Ave NW, Washington, DC Understanding Patient Engagement in Stage 2 MU: Direct, HIPAA, VDT, and Patient Engagement.
Understanding Meaningful Use Presented by: Allison Bryan MS, CHES December 7, 2012 Purdue Research Foundation 2012 Review of Stage 1 and Stage 2.
Eligible Hospitals (EH) & Critical Access Hospitals (CAH)
Interoperability Kevin Schmidt Director, Clinical Network.
Meeting Stage 1 Meaningful Use Criterion Carlos A. Leyva, Esq. Digital Business Law Group, P.A.
2015 Edition Proposed Rule Modifications to the ONC Health IT Certification Program and 2015 Edition Health IT Certification Criteria.
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Supporting Meaningful Use Stage 2 Transition of Care Requirements
Understanding and Leveraging MU Stage 2 Optional Transports (SOAP)
Interoperability and Health Information Exchange Workgroup April 17, 2015 Micky Tripathi, chair Chris Lehmann, co-chair.
Data Update Health IT Standards Committee Meeting March 18, 2015.
Meaningful Use, Standards and Certification Under HITECH—Implications for Public Health InfoLinks Community of Practice January 14, 2010 Bill Brand, MPH,
Series 1: Meaningful Use for Behavioral Health Providers From the CIHS Video Series “Ten Minutes at a Time” Module 2: The Role of the Certified Complete.
Discussion of 2015 Ed. NPRM Certification/Adoption Workgroup HIT Policy Committee April 2, 2014.
Medicare & Medicaid EHR Incentive Programs
Understanding and Leveraging MU2 Optional Transports Paul M. Tuten, PhD Senior Consultant, ONC Leader, Implementation Geographies Workgroup, Direct Project.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
Moderator Kevin Larsen, MD Medical Director, Meaningful Use Office of the National Coordinator for Health Information Technology Washington, D.C. Using.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group May 17, 2013.
A First Look at Meaningful Use Stage 2 John D. Halamka MD.
Meaningful Use Stage 2 Esthee Van Staden September 2014.
Meaningful Use Measures. Reporting Time Periods Reporting Period for 1 st year of MU (Stage 1) 90 consecutive days within the calendar year Reporting.
Saeed A. Khan MD, MBA, FACP © CureMD Healthcare ACOs and Requirements for Reporting Quality Measures Meaningful Use Are you still missing out? © CureMD.
Connecticut Ave NW, Washington, DC Direct Exchange An Introduction for Providers Engaged in Stage 2 Meaningful Use David.
New Opportunity for Network Value: Using Health IT to Improve Transitions of Care 600 East Superior Street, Suite 404 I Duluth, MN I Ph
Series 1: Meaningful Use for Behavioral Health Providers From the CIHS Video Series “Ten Minutes at a Time” Module 2: The Role of the Certified Complete.
Cross Vendor Exchange Testing and Certification Plans April 18, 2013.
New Jersey Institute of Technology Enterprise Development Center (EDC) 211 Warren Street, Newark, NJ Phone: Fax:
NWH TRANSITION OF CARE DOCUMENT FOR MU STAGE 2 JUNE 6, 2014.
Cross Vendor Exchange Testing and Certification Plans April 18, 2013 Meaningful Use Stage 2 Exchange Summit Avinash Shanbhag, ONC.
A First Look at Meaningful Use Stage 2 John D. Halamka MD.
Exchange: The Central Feature of Meaningful Use Stage Meaningful Use and Health Care Innovation Conference Craig Brammer Office of the National.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group August 9, 2013.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group August 16, 2013.
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
Transitions of Care Initiative Companion Guide to Consolidated CDA for Meaningful Use.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group July 19, 2013.
GloStream and Meaningful Use August, Table of Contents Final rule from the ONC and CMS The gloStream path to truly meaningful use Medicare payment.
Unit 1b: Health Care Quality and Meaningful Use Introduction to QI and HIT This material was developed by Johns Hopkins University, funded by the Department.
1 Meaningful Use Stage 2 The Value of Performance Benchmarking.
Medicare & Medicaid EHR Incentive Programs Stage 2 Final Rule Travis Broome HIT Standards Committee
Provider Data Migration and Patient Portability NwHIN Power Team August 28, /28/141.
©2011 Falcon, LLC. All rights reserved. Proprietary. May not be copied or distributed without the express written permission of Falcon, LLC. Falcon EHR.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group July 26, 2013.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group September 13, 2013.
Component 11/Unit 2a Meaningful Use of the Electronic Health Record (EHR)
Meaningful Use Made Easy Step by Step Approach to Stage 1 Compliance and 2013 Changes My Vision Express Practice Management and EMR Software Presented.
Meaningful Use: Stage 2 Changes An overall simplification of the program aligned to the overarching goals of sustainability as discussed in the Stage.
CMS Medicare and Medicaid Electronic Health Record (EHR) Incentive Programs Final Rule Overview 1 Robert Anthony.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group June 14, 2013.
Beacon Community Program Build and Strengthen – Improve – Test innovation Beacon-EHR Vendor Full Affinity Group June 7, 2013.
Interoperability and Health Information Exchange Workgroup April 24, 2015 Micky Tripathi, chair Chris Lehmann, co-chair.
HIT Standards Committee Privacy and Security Workgroup Standards and Certification Requirements for Certified EHR Modules Dixie Baker, Chair Walter Suarez,
Meaningful Use Measures Series – Session 3 Objectives related to interoperability and exchanging data to outside entity 1.
The NC Medicaid EHR Incentive Program Presented by: Rachael Williams, Program Manager Layne Roberts, Data Specialist.
Meaningful Use Workgroup Subgroup 2 - Engaging Patients and Families Christine Bechtel, Subgroup Chair Paul Tang, MU WG Chair July 2,
360Exchange (360X) Project 12/06/12. Reminders / announcements 360X Update CEHRT 2014 / MU2 Transition of Care Requirements 1 Agenda.
Electronic Exchange of Clinical Information Configuring RPMS-EHR for Meaningful Use Resource Patient Management System.
By: Rebecca Cameron Amie Dennis Amy Everson Debborah Stokes.
2014 Edition Test Scenarios Development Overview Presenter: Scott Purnell-Saunders, ONC November 12, 2013 DRAFT.
Interoperability Measurement for the MACRA Section 106(b) ONC Briefing for HIT Policy and Standards Committee April 19, 2016.
Meaningful Use Update 2015: How Does It Impact Family Medicine? Ryan Mullins, MD, CPE, CPHQ, CPHIT.
Modified Stage 2 Meaningful Use: Objective #8 – Patient Electronic Access Massachusetts Medicaid EHR Incentive Payment Program July 19, 2016 Today’s presenter:
The Value of Performance Benchmarking
An Overview of Meaningful Use Proposed Rules in 2015
Modified Stage 2 Meaningful Use: Objective #5 – Health Information Exchange (Summary of Care) Massachusetts Medicaid EHR Incentive Payment Program July.
Health Information Exchange for Eligible Clinicians 2019
Presentation transcript:

Meaningful Use Personal Pace Education Module: Transitions of Care

Prerequisites This education module assumes you have general familiarity with: – The Medicare and Medicaid EHR Incentive Programs (“meaningful use”). – The Standards and Certification Criteria 2014 Edition final rule and standards terminology. – The relationship between meaningful use and Certified EHR Technology (CEHRT). 2

Meaningful Use & Certification Relationship “Transitions of Care” (ToC) Objective When looked across both Stages 1 & 2, the ToC objective includes 3 measures: Measure #1 requires the provision of a summary of care record for more than 50% of transitions of care and referrals. Measure #2 requires that the provision of a summary of care record using electronic transmission through CEHRT or eHealth Exchange participant for more than 10% of transitions of care and referrals Measure #3 requires at least one summary care record electronically transmitted to recipient with different EHR vendor or to CMS test EHR Meaningful Use2014 Edition Certification Two 2014 Edition EHR certification criteria (b)(1) : Transitions of care— receive, display, and incorporate transition of care/referral summaries (b)(2) : Transitions of care— create and transmit transition of care/referral summaries. Stage 1 onlyStage 2 Exclusion: Eligible professionals who have less than 100 transitions of care and referrals in the reporting period do not have to meet these measures Note: For any of these measures it is important to remember that the recipient does NOT also have to have Certified EHR Technology. 3

Feature Focus: ToC Measure #2 & (b)(2) The eligible provider, eligible hospital or CAH that transitions or refers their patient to another setting of care or provider of care provides a summary of care record for more than 10% of such transitions and referrals either: (a) electronically transmitted using CEHRT to a recipient; or (b) where the recipient receives the summary of care record via exchange facilitated by an organization that is a NwHIN Exchange participant or in a manner that is consistent with the governance mechanism ONC establishes for the nationwide health information network. ToC Measure # (b)(2) Transitions of care—create and transmit transition of care/referral summaries. (i) Enable a user to electronically create a transition of care/referral summary formatted according to the Consolidated CDA with, at a minimum, the data specified by CMS for meaningful use. (ii) Enable a user to electronically transmit CCDA in accordance with: “Direct” (required) “Direct” +XDR/XDM (optional, not alternative) SOAP + XDR/XDM (optional, not alternative) eHealth Patient name; Sex; Date of birth. Race; Ethnicity; Preferred language; Smoking status; Problems; Medications; Medication allergies; Laboratory test(s) and value(s)/result(s); Vital signs (height, weight, blood pressure, BMI); Care plan field(s), including goals and instructions; Procedures ; Care team member(s) and other ambulatory and inpatient specific data 4

MU ToC Measure #2 Numerator & Denominator For your reference Denominator: – Number of transitions of care and referrals during the EHR reporting period for which the EP or eligible hospital’s or CAH’s inpatient or emergency department (POS 21 or 23) was the transferring or referring provider. Numerator: – The number of transitions of care and referrals in the denominator where a summary of care record was a) electronically transmitted using CEHRT to a recipient or b) where the recipient receives the summary of care record via exchange facilitated by an organization that is a NwHIN Exchange participant or in a manner that is consistent with the governance mechanism ONC establishes for the nationwide health information network. The organization can be a third-party or the sender’s own organization. 5

Certification Options 6

Option 2 1.EHR sends “data” to HISP 2.HISP generates CCDA 3.HISP performs as STA and sends Direct msg HISP/HIE certified on its own. Option 3 1.EHR generates CCDA 2.EHR sends CCDA to HISP 3.HISP performs as STA and sends Direct msg HISP/HIE certified as “relied upon software” with the EHR. Certification given to the pair, not separately to EHR and HISP. Option 1 1.EHR generates CCDA 2.EHR performs as STA and sends Direct msg STA/HISP function integrated into EHRs; no separate certification testing for HISP. 3 Valid Certification Options for EHR Technology (to meet minimum certification requirement) Provider A Provider B EHR Affiliated HISP/HIE Provider A HISP/HIE Provider A Direct (SMTP + S/MIME) Provider B Direct (SMTP + S/MIME) Direct (SMTP + S/MIME) Any Edge Protocol Any Edge Protocol What gets presented for certification 45 CFR (b)(2) (i)Create CCDA with requisite data specified for MU (ii)Enable a user to electronically transmit ToC in accordance with “Direct” (or “Direct” +XDR/XDM; or SOAP + XDR/XDM) 7

MU “Measure #2” Approaches Note: it is important to remember that the summary care record must reach the provider it is being sent to before it can be counted towards Measure #2. 8

MU Approach #1A: Transmit Summary Care Record Using CEHRT “Direct” Transport Capability Provider A Provider B EHR Affiliated HISPProvider A HISP Provider A Direct (SMTP + S/MIME) Provider B Direct (SMTP + S/MIME) Any Edge Protocol Represents Certified EHR Technology or “CEHRT” Direct (SMTP + S/MIME) Any Edge Protocol Example 1 Example 2 Example 3 9

1. EHR generates CCDA 2. EHR (certified to include optional SOAP + XDR/XDM transport) sends message to Provider B using SOAP + XDR/XDM MU Approach #1B: Transmit Summary Care Record Using CEHRT Optional SOAP +XDR/XDM Transport Capability Provider A Provider B SOAP + XDR/XDM CEHRT Example 1 Example 2 [Approach 1B - Example 2] Key notes for Providers and EHR technology developers to consider: The fact there’s a “HISP/HIE in the middle” is irrelevant with respect to Provider A meeting MU requirements. Provider A’s use of their CEHRT’s optional transport capability enables Provider A to include this transmission in Measure #2’s numerator (consistent with the measure’s requirements and that Provider B receives the summary care record). Under this approach, HISPs/HIE entities do not have to be certified. This allows any EHR vendor supporting the SOAP + XDR/XDM option to interoperate with any HISP that also offers SOAP + XDR/XDM support. 1. EHR generates CCDA 2.EHR (certified to include optional SOAP + XDR/XDM transport) sends message to Provider B (via HISP) using SOAP + XD 3.HISP/HIE repackages content and sends to Provider B HISP/HIE Provider A Provider B SOAP + XDR/XDM 10

NwHIN Example 1.EHR generates CCDA 2.EHR sends CCDA to eHealth Exchange Participant 3.eHealthExchange Participant sends to Provider B MU Approach #2: Transmit via eHealth Exchange Participant Provider A Provider B CEHRT eHealth Exchange Participant (formerly NwHIN Exchange) Example 1 [Approach 2 – Example 1] Key notes for Providers and EHR technology developers to consider: Similar to Example 2 in Approach1B, the fact that there is an eHealth Exchange participant in the middle is irrelevant with respect to Provider A meeting MU requirements. An eHealth Exchange participant does not have to be certified, however, Provider A must still use their CEHRT’s capability to generate a standard summary care record in accordance with the CCDA and Provider B still needs to receive the summary care record in order for it to count in Provider A’s numerator. 11

MU Approach #3: “Pull” or “Query” Scenarios provider 1provider 2provider 3provider 4 provider 5 [Approach 3] Key Notes for Providers and EHR technology developers to consider: Similar to Example 2 under Approach 1B, the fact that there is an entity in middle is irrelevant with respect to providers #1-4 meeting MU requirements. However, there are two scenarios to keep in mind when it comes to having EHR technology that meets the Certified EHR Technology definition and how that could affect MU measurement. Scenario 1: If provider’s #1-4 have CEHRT without the aid of an HIE and use the CEHRT’s transport capability (Direct or SOAP) to send a CCDA formatted summary care record to an HIE entity which subsequently enables the summary care record they’ve sent to be pulled by another provider, then a pull of that summary care record just needs to occur by provider #5. Scenario 2: In contrast to scenario 1, if provider’s #1-4 depend on the HIE entity to satisfy the CEHRT definition (from either a paired or stand alone certification approach) and thus rely on it to create the CCDA formatted summary care record and transmit it to provider 5 as a result of a pull, these providers would need to have EHR technology that had been certified in a stand alone way or combination with the HIE to perform the full requirements specified in the certification criterion (as described per prior slides). In either scenario, for all providers where the patient meets the denominator requirements for measure #2, when provider #5 pulls the patient’s summary care record from the HIE entity, they can then count that pull in their numerator as a transmission to provider #5. HIE entity 12

Let’s Recap Three certification options are available for ToC certification 1: “Native” capabilities all within the same EHR technology solution 2: EHR technology + HIE/HISP combination 3: HIE/HISP stand alone EHR technology developers that include and seek testing and certification for the optional SOAP + XDR/XDM can provide a “HISP/HIE agnostic” solution for their customers. There are three approaches to demonstrating MU: 1A: Use CEHRT’s “Direct” capability 1B: Use CEHRT’s “SOAP+XDR/XDM” capability 2: Use CEHRT to create a CCDA and partner with an eHealth Exchange participant 3: Use CEHRT to create a CCDA that is then retrieved/queried by another provider For any of these MU approaches transmissions will only count in the measure’s numerator if they are received by the provider to whom the sending provider is referring or transferring the patient. The recipient does NOT also have to have Certified EHR Technology. 13

Resources See these general resources for more info – ONC resources: use-stage-2http:// use-stage-2 – CMS resources: Guidance/Legislation/EHRIncentivePrograms/EducationalMaterials.htmlhttp:// Guidance/Legislation/EHRIncentivePrograms/EducationalMaterials.html ToC specific FAQs from ONC and CMS – ONC FAQ ( implementers/faqs/how-can-i-learn-more-about-onc-regulations-guidance-and-electro) implementers/faqs/how-can-i-learn-more-about-onc-regulations-guidance-and-electro – CMS FAQ 7699 ( Consolidated CDA – “Direct” specification and XDR/XDM specification – SOAP specification –