Source: https://www.healthit.gov/test-method/automated-measure-calculation
Timestamp: 2020-07-16 13:56:04
Document Index: 214583196

Matched Legal Cases: ['§170', '§170', '§170', '§170', '§170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170', '§ 170']

Automated measure calculation | HealthIT.gov
Version 2.3 Updated on 06-01-2020
Modified test procedure instructions to indicate self-testing and submission of reports.
Added gap criteria option for computerized provider order entry (CPOE) measures.
Reordered required tests to mirror the Centers for Medicare & Medicaid Services (CMS) measure numbers.
Removed (g)(7) from the first table. Modified the first table to link Required Test 9 to the (b)(2) criterion.
Clarified in the global test requirements that health IT developers are not required to use more than one measure for testing.
Added Inpatient CPOE measure statements.
Modified language on which systems need to test for each calculation method.
Modified language to clarify that health IT developers are not required to test 2a, 2b, and 2c and 4a, 4b, and 4c.
Modified the numerator for Required Test 3 Advancing Care Information (ACI) Measure English Statement to reflect that action must occur during the performance period.
Modified language on the options systems have for testing the different calculation methods.
Added an attestation requirement around documentation provided to end users related to systems’ ability to calculate the different methods.
Added "Denominator" in front of the second definition under the ACI Measure English Statement for Required Test 6.
Clarified the View, Download, Transmit Measure for ACI to describe the action as being taken by the patient or the patient’s authorized representative rather than the Eligible Clinician (EC) per the Quality Payment Program Calendar Year (CY) 2018 Final Rule (82 FR 53568).
Made the following changes based on the CMS policy changes per the CY 2019 Hospital Inpatient Prospective Payment System (IPPS) Final Rule: Added Required Tests 13, 14, and 15. Updated the measure thresholds for the Stage 3 measure for Required Test 1, 2a, 2b, 2c, and 7 and the name for Required Test 2a, 2b, 2c, and 7. Modified the name of the EHR Incentive Program to the Promoting Interoperability program.
Added clarification that both the EC Individual and EC Group methods must be tested by a Health IT Module supporting the ACI Transition and/or ACI calculation method.
Modified the timely access requirement for the ACI Patient Access measure based on a CMS policy change per the QPP CY 2018 Final Rule (82 FR 53568).
Added text noting that the Promoting Interoperability measure for Required Tests 3, 4, 5, 6, 8, and 9 are only applicable in 2018. Added text noting the Promoting Interoperability measure for Required Tests 13, 14, and 15 are only applicable starting in 2019.
Modified the name of the ACI Transition and ACI to Promoting Interoperability Transition and Promoting Interoperability.
Updated Required Test 15 to remove the draft status for eligible hospitals/critical access hospitals (EH/CAH).
Per the CY2020 IPPS Final Rule, updated Required Test 13 to remove the EH/CAH measures and the Required Test 14 measure to note it is only applicable in 2019. Per the CY2019 Physician Fee Schedule (PFS) Final Rule, added the EC measures for Required Test 13, 14, and 15.
Updated Required Test 15 to remove the test lab verification requirement to verify the content of the care summary record.
Based on the sunsetting of the 2014 Edition in the 21st Century Cures Act Final Rule, measure descriptions and requirements related only to Modified Stage 2 and Promoting Interoperability Transition were removed. Removed the Promoting Interoperability measure for Required Tests 3, 4, 5, 6, 8, and 9 as they were only applicable in 2018. Made changes to the naming terminology to align with CMS program updates including modifying the measure naming convention from Stage 3 to Medicare and/or Medicaid Promoting Interoperability programs; and added the EH/CAH measure description.
§170.315 (g)(2) Automated measure calculation—
For each Promoting Interoperability Programs percentage-based measure that is supported by a capability included in a technology, record the numerator and denominator and create a report including the numerator, denominator, and resulting percentage associated with each applicable measure.
Test Data Set 1 – EH/CAH
See the file "§170.315(g)(2) EH/CAH" below under the Attachments section. Last updated on 06-15-2020.
Test Data Set 2 – EP/EC
See the file "§170.315(g)(2) EP/EC" below under the Attachments section. Last updated on 06-15-2020.
§170.315(g)(2) EH/CAH 06-15-2020
§170.315(g)(2) EP/EC 06-15-2020
Please consult the Final Rule entitled: 2015 Edition Health Information Technology (Health IT) Certification Criteria, 2015 Edition Base Electronic Health Record (EHR) Definition, and ONC Health IT Certification Program Modifications for a detailed description of the certification criterion with which these testing steps are associated. Developers are encouraged to consult the Certification Companion Resource in tandem with the test procedure as they provide clarifications that may be useful for product development and testing.
Gap Eligibility
Three measures are eligible for gap certification: 1) Required Test 10 –CPOE Medications, Medicaid Promoting Interoperability Program; 2) Required Test 11 – CPOE Laboratory, Medicaid Promoting Interoperability Program; and 3) Required Test 11 – CPOE Radiology/Diagnostic Imaging, Medicaid Promoting Interoperability Program.
The table that provides a description of the Medicare and Medicaid Promoting Interoperability (formerly Electronic Health Record (EHR) Incentive Program) and Merit-based Incentive Payment System (MIPS) Promoting Interoperability performance category objectives supported by the measure calculation (§ 170.315(g)(2)) certification criteria is located in the Master Table of Related and Required Criteria. That document can be found under the 2015 Edition Test Method Resources section on the left hand side of the screen for any criterion under the Topics Navigation menu.
The tests are organized as follows:
Required Tests 1 through 15 are measure-specific sections that address required capabilities for each measure.
Health IT Modules that are ambulatory systems only must use the ambulatory test data and test at least one of the two calculation methods: 1) Medicaid Promoting Interoperability Program; or 2) MIPS Promoting Interoperability performance category (TIN/NPI). Health IT Modules that are inpatient systems only must use the eligible hospital test data and, if the inpatient system is used in the ambulatory setting, the ambulatory test and test at least one of four calculation methods: 1) Medicaid Promoting Interoperability Program; or 2) MIPS Promoting Interoperability performance category (TIN/NPI). Health IT Modules that are both ambulatory and inpatient systems must use the eligible hospital test data and the ambulatory test and test at least one of two calculation methods: 1) Medicare and Medicaid Promoting Interoperability Programs; or 2) MIPS Promoting Interoperability performance category (TIN/NPI). Health IT Modules that test to the MIPS Promoting Interoperability performance category measures are deemed as meeting the testing requirements for the Medicaid Promoting Interoperability Program measures. Health IT Modules that test for the MIPS Promoting Interoperability performance category calculation methods must test for both the EC individual and EC Group calculation methods.
For Measure Specific Sections
Within each of the measure-specific sections, the test procedure addresses the capability to record the numerator and denominator and resulting percentage for § 170.315(g)(2) for each measure for Medicare and Medicaid Promoting Interoperability Programs and MIPS Promoting Interoperability performance category measures:
Record – evaluates the capability to electronically record the numerator and denominator and resulting percentage for each objective with a percentage-based measure
The health IT developer records all numerator and denominator measure elements for the method(s) by which the Health IT Module records the numerator and denominator for each measure.
Within each of the measure-specific sections, the test procedure addresses the capabilities to report each measure for Medicare and Medicaid Promoting Interoperability Programs and MIPS Promoting Interoperability performance category measures. A single set of test patients has been created that occur across all required tests. The health IT developer is required to use all test patients in each scenario. The health IT developer must use the test patients that are in the test data and may not change their names, birthdays, or gender.
Report – evaluates the capability to create a report that includes the numerator and denominator associated with each percentage-based measure.
The health IT developer enters the test patients for Scenario 1 and the corresponding test data for each required test for which they are presenting for testing.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator and denominator and resulting percentage for each measure based on the supplied test data from Test Data Scenario 1 (baseline measure report) across all required tests. The report must also include the list of patients included in the numerator and denominator.
The health IT developer marks the report as Scenario 1.
The health IT developer enters all of the test patients in Scenario 2 and the corresponding test data for each required test.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator and denominator and resulting percentage for each measure based on the supplied test data from Test Data Scenario 2 (populate numerator) across all required tests. The report must also include the list of patients included in the numerator and denominator.
The health IT developer marks the report as Scenario 2.
The health IT developer enters all of the test patients in Scenario 3 and the corresponding test data for each required test.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator and denominator and resulting percentage for each measure based on the supplied test data from Test Data Scenario 3 (populate numerator and denominator) across all required tests. The report must also include the list of patients included in the numerator and denominator.
The health IT developer marks the report as Scenario 3.
The health IT developer enters all of the test patients in Scenario 4 and the corresponding test data for each required test.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator and denominator and resulting percentage for each measure based on the supplied test data from Test Data Scenario 4 (populate denominator) across all required tests. The report must also include the list of patients included in the numerator and denominator.
The health IT developer marks the report as Scenario 4.
The health IT developer enters all of the test patients in Scenario 5 and the corresponding test data for each required test.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator and denominator and resulting percentage for each measure based on the supplied test data from Test Data Scenario 5 (do not populate numerator or denominator) across all required tests. The report must also include the list of patients included in the numerator and denominator.
The health IT developer marks the report as Scenario 5.
The health IT developer submits all five reports to the tester for review.
The tester verifies that the increments in the numerator and denominator produced in the delta report are accurate and complete and represent the expected increments in comparison to the baseline measure report, based on the ONC supplied test data. The tester uses the English Statements described in the Test Guide for each measure. The tester verifies that the correct patients are included in the numerator and denominator for each measure.
The test data for § 170.315(g)(2) are previously supplied. ONC supplies Test Cases to be used during the test, and the health IT developer supplies information as directed in the test data. The measure-specific test data is organized into a single set of 11 test cases or less, depending on the measure, which are used across all required tests. As such, each test case appears in the same scenario in each required test, though the numerator and denominator may not increment the same across each required test. All test cases must be used.
Each measure-specific Test Description provides a Measure Element list and English Statements for each measure. The Measure Element list deconstructs the English Statements to provide the discrete measure elements for recording the numerator and denominator.
Health IT developers with Health IT Modules certified to section (g)(2) are required to attest that they have provided to other health IT developers and end-users documentation including the following as applicable:
For ambulatory only systems or inpatient/ambulatory systems, identify and acknowledge the Health IT Module is not certified or deemed to section (g)(2) for both calculation methods 1) Medicaid Promoting Interoperability program; or 2) Merit-based Incentive Payment System (MIPS) Promoting Interoperability performance category (TIN/NPI).
Tester verifies that the attestation includes all required elements.
Required Test 1 - ePrescribing
Merit-based Incentive Payment System (MIPS) Promoting Interoperability Performance Category
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. Any prescriptions written by the eligible professional (EP) in an ambulatory setting, or discharge medication orders in an inpatient setting, will populate the numerator once per prescription transmitted electronically and queried for a drug formulary for a patient who was seen/admitted during the reporting/performance period.
Medicare and Medicaid Promoting Interoperability Programs Measure:
Medicaid EP: More than 60 percent of all permissible prescriptions written by the EP are queried for a drug formulary and transmitted electronically using certified electronic health record technology (CEHRT).
Medicaid EH/CAH: More than 25 percent of hospital discharge medication orders for permissible prescriptions (for new and changed prescriptions) are queried for a drug formulary and transmitted electronically using CEHRT.
Medicare EH/CAH: At least one hospital discharge medication order for permissible prescriptions (for new and changed prescriptions) is queried for a drug formulary and transmitted electronically using CEHRT.
Medicare and Medicaid Promoting Interoperability Programs Measure English Statements:
Numerator: The number of prescriptions in the denominator generated, queried for a drug formulary, and transmitted electronically.
Denominator: The number of new or changed prescriptions written for drugs requiring a prescription in order to be dispensed other than controlled substances for patients discharged during the EHR reporting period.
Medicare and Medicaid Promoting Interoperability Programs Measure Elements:
Numerator: Prescription generated, queried for a formulary, and transmitted electronically.
Denominator: Prescriptions generated.
MIPS Promoting Interoperability Performance Category Measure:
EC: At least one permissible prescription written by the MIPS EC is queried for a drug formulary and transmitted electronically using CEHRT.
MIPS Promoting Interoperability Performance Category English Statements:
Numerator: The number of prescriptions in the denominator generated, queried for a drug formulary, and transmitted electronically using certified EHR technology.
MIPS Promoting Interoperability Performance Category Measure Elements:
Denominator: Prescriptions other than controlled substances generated; or prescriptions generated.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 1 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 2a, b, or c – Provide Patients Electronic Access to Their Health Information (formerly Patient Electronic Access)
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The act of giving a patient timely online access to his or her health information will populate the numerator if:
Medicare and Medicaid Promoting Interoperability Program: the information is made available to the patient within 48 hours of its availability to the provider for an EP or within 36 hours of its availability to the provider for an eligible hospital or CAH.
Promoting Interoperability performance category: the information is made available to the patient within four business days of its availability to the EC.
Health IT Modules that are certified to § 170.315 (e)(1) and (g)(8), (g)(9) or (g)(10) must use test data in tab RT 2a Provider Patient Exchange (EH/CAH and EP/EC). Health IT Modules that are certified to § 170.315 (e)(1) only must use test data in tab RT 2b Provider Patient Exchange (EH/CAH and EP/EC).
Health IT Modules that are certified to § 170.315 (g)(8) or (g)(9) must use test data in tab RT 2c Provider Patient Exchange (EH/CAH and EP/EC) and will only be tested for the Medicare and Medicaid Promoting Interoperability Programs and Promoting Interoperability performance category measures.
Medicaid EP: For more than 80 percent of all unique patients seen by the EP: (1) The patient (or the patient-authorized representative) is provided timely access to view online, download, and transmit his or her health information; and (2) The provider ensures the patient’s health information is available for the patient (or patient-authorized representative) to access using any application of his or her choice that is configured to meet the technical specifications of the API in the provider’s CEHRT.
Medicaid EH/CAH: For more than 80 percent of all unique patients discharged from the eligible hospital or CAH inpatient or emergency department (POS 21 or 23): (1) The patient (or the patient-authorized representative) is provided timely access to view online, download, and transmit his or her health information; and (2) The provider ensures the patient’s health information is available for the patient (or patient-authorized representative) to access using any application of his or her choice that is configured to meet the technical specifications of the API in the provider’s CEHRT.
Medicare EH/CAH: For at least one unique patient discharged from the eligible hospital or CAH inpatient or emergency department (POS 21 or 23): (1) The patient (or the patient-authorized representative) is provided timely access to view online, download, and transmit his or her health information; and (2) The provider ensures the patient’s health information is available for the patient (or patient-authorized representative) to access using any application of his or her choice that is configured to meet the technical specifications of the API in the provider’s CEHRT.
Medicare and Medicaid Promoting Interoperability Programs English Statements:
Numerator: The number of patients in the denominator (or patient-authorized representative) who are provided timely access to health information to view online, download, and transmit to a third party and to access using an application of their choice that is configured meet the technical specifications of the API in the provider's CEHRT.
Date and time information available to the EP;
Date and time information made available online to patient;
Date and time information made available to an API.
Denominator: Number of patients seen by the EP.
Date and time of discharge;
Denominator: Number of patients discharged from the EH or CAH.
Merit-based Incentive Payment System (MIPS) Promoting Interoperability Performance Category Measure:
EC: For at least one unique patient seen by the MIPS EC (1) the patient (or the patient authorized representative) is provided timely access to view online, download, and transmit his or her health information; and (2) the MIPS EC ensures the patient's health information is available for the patient (or patient-authorized representative) to access using any application of his or her choice that is configured to meet the technical specifications of the API in the MIPS EC's CEHRT.
Numerator: The number of patients in the denominator (or patient authorized representatives) who are provided timely access to health information to view online, download, and transmit to a third party and to access using an application of their choice that is configured to meet the technical specifications of the API in the MIPS EC’s certified EHR technology.
Denominator: The number of unique patients seen by the MIPS EC during the performance period.
Date and time information available to the EC;
Denominator: Number of patients seen by the EC.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 2a, 2b, or 2c and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5. The tester verifies that all of the required information below is made available to patients.
Common Clinical Data Set (which should be in their English representation)
Provider’s name and office contact information (ambulatory setting only)
Admission and discharge dates and locations; discharge instructions; and reason(s) for hospitalization (inpatient setting only)
Laboratory test report(s)
Diagnostic image report(s)
Required Test 3 – Patient Education
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or they may create one report for all of the required tests for which they are seeking certification. For all measures, for the Health IT Module to record the numerator, the provider must provide patient-specific resources identified by the Health IT Module no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting period only), during the reporting/performance period (for a 90-day and full calendar year reporting period), or no later than the last day of the calendar year of the reporting period to populate and record the numerator (for a 90-day and full calendar year reporting period).
Medicaid Promoting Interoperability Program Measure:
Medicaid EP: The EP must use clinically relevant information from CEHRT to identify patient-specific educational resources and provide electronic access to those materials to more than 35 percent of unique patients seen by the EP during the EHR reporting period.
Medicaid EH/CAH: The EH or CAH must use clinically relevant information from CEHRT to identify patient-specific educational resources and provide electronic access to those materials to more than 35 percent of unique patients discharged from the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Medicaid Promoting Interoperability Program Measure English Statements:
Ambulatory/Inpatient:
Denominator: The number of unique patients seen by the EP or the number of unique patients discharged from an eligible hospital or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Medicaid Promoting Interoperability Program Measure Elements:
Numerator: Provision of electronic access to patient specific education resource(s) identified by the CEHRT.
Number of patients seen by the EP.
Number of patients discharged from the EH or CAH.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 3 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 4a, b, or c – View, Download, Transmit
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. For the Health IT Module to record the numerator, the patient must view, download, or transmit his or her health information no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting period only), during the reporting/performance period (for a 90-day and full calendar year reporting period), or no later than the last day of the calendar year of the reporting period to populate and record the numerator (for a 90-day and full calendar year reporting period).
Health IT Modules that are certified to § 170.315 (e)(1) and (g)(8), (g)(9) or (g)(10) must use test data in tab RT 4a VDT.
Health IT Modules that are certified to § 170.315 (e)(1) only must use test data in tab RT 4b VDT.
Health IT Modules that are certified to § 170.315 (g)(8) or (g)(9) must use test data in tab RT 4c VDT, and will only be tested for the Medicaid Promoting Interoperability Program measure.
Medicaid EP: During the EHR reporting period, more than 10 percent of all unique patients (or their authorized representatives) seen by the EP actively engage with the EHR made accessible by the provider and either: (1) view, download, or transmit to a third party their health information; or (2) access their health information through the use of an API that can be used by applications chosen by the patient and configured to the API in the provider's CEHRT; or (3) a combination of (1) and (2).
Medicaid EH/CAH: More than 10 percent of all unique patients (or their authorized representatives) discharged from the EH or CAH inpatient or emergency department (POS 21 or 23) actively engage with the EHR made accessible by the provider and either: (1) view, download, or transmit to a third party their health information; or (2) access their health information through the use of an API that can be used by applications chosen by the patient and configured to the API in the provider's CEHRT; or (3) a combination of (1) and (2).
Numerator: The number of unique patients (or their authorized representatives) in the denominator who have viewed online, downloaded, or transmitted to a third party the patient's health information during the EHR reporting period and the number of unique patients (or their authorized representatives) in the denominator who have accessed their health information through the use of an API during the EHR reporting period.
Denominator: Number of unique patients discharged from an eligible hospital or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Patient (or patient-authorized representative) views, downloads, or transmits the patient's information;
Patient (or patient-authorized representative) accesses the patient's information via API.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 4a, 4b, or 4c and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
The tester verifies that the Health IT Module functions makes the following information available:
Required Test 5 – Secure Messaging
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when the provider sends a secure message no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting period only), during the reporting/performance period (for a 90-day and full calendar year reporting period), or no later than the last day of the calendar year of the reporting period to populate and record the numerator (for a 90-day and full calendar year reporting period).
Medicaid EP: For more than 25 percent of all unique patients seen by the EP during the EHR reporting period, a secure message was sent using the electronic messaging function of CEHRT to the patient (or the patient-authorized representative), or in response to a secure message sent by the patient or his or her authorized representative.
Medicaid EH/CAH: For more than 25 percent of all unique patients discharged from the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period, a secure message was sent using the electronic messaging function of CEHRT to the patient (or the patient-authorized representative), or in response to a secure message sent by the patient or his or her authorized representative.
Denominator: Number of unique patients seen by the EP or discharged from the EH or CAH inpatient or emergency department during the reporting period.
EP/EH Replies to Secure Electronic Message from Patient or Patient Representative;
EP/EH Sends Secure Electronic Message to Patient or Patient Representative;
EP/EH Sends Secure Message to Provider Including Patient or Patient Representative.
Denominator: Number of unique patients seen by the EP or discharged from the EH or CAH.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 5 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 6 – Patient Generated Health Data
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when patient generated data, or data from a non-clinical setting are incorporated during the reporting/performance period.
Medicaid (EP/EH/CAH): Patient generated health data or data from a nonclinical setting is incorporated into the CEHRT for more than five percent of all unique patients seen by the EP or discharged from the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Denominator: Number of unique patients seen by the EP or the number of unique patients discharged from an EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Patients with non-clinical data incorporated into the record;
Patients with patient-generated health data incorporated into the record.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 6 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 7 – Support Electronic Referral Loops by Sending Health Information (formerly Transitions of Care)
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when a provider creates and transmits/exchanges a summary of care record, and confirms receipt of the transmitted/exchanged summary of care record, no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting/performance period only), during the reporting/performance period (for a 90-day and full calendar year reporting/performance period), or no later than the end of the calendar year (for a 90-day reporting/performance period only).
Medicaid EP: For more than 50 percent of transitions of care and referrals, the EP that transitions or refers their patient to another setting of care or provider of care: (1) creates a summary of care record using CEHRT; and (2) electronically exchanges the summary of care record.
Medicaid EH/CAH: For more than 50 percent of transitions of care and referrals, the EH or CAH that transitions or refers their patient to another setting of care or provider of care: (1) creates a summary of care record using CEHRT; and (2) Electronically exchanges the summary of care record.
Medicare EH/CAH: For at least one transition of care or referral the eligible hospital or CAH that transitions or refers their patient to another setting of care or provider of care: (1) creates a summary of care record using CEHRT; and (2) electronically exchanges the summary of care record.
Denominator: Number of transitions of care and referrals during the EHR reporting period for which the EP or EH or CAH inpatient or emergency department (POS 21 or 23) was the transferring or referring provider.
Summary of care record created and exchanged;
Summary of care record receipt confirmed.
Denominator: Number of transitions of care for which the EP, EH, or CAH was the transferring or referring provider.
For at least one transition of care or referral, the MIPS EC that transitions or refers their patient to another setting of care or health care provider: (1) creates a summary of care record using certified EHR technology; and (2) electronically exchanges the summary of care record.
MIPS Promoting Interoperability Performance Category Measure English Statements:
Denominator: Number of transitions of care and referrals during the performance period for which the MIPS EC was the transferring or referring clinician.
Denominator: Number of transitions of care and referrals for which the EP, EH, or CAH was the transferring of referring provider.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 7 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
The tester shall verify that at a minimum, the following fields (listed below) in the summary of care record contain all of the information (or an indication of none) prior to numerator population. If a summary of care record does not contain all of the information (or an indication of none), the numerator should not be populated for both ambulatory & inpatient settings:
Current medication list;
Required Test 8 Receive and Incorporate
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when the provider receives and incorporates a summary of care record no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting/performance period only), during the reporting/performance period (for a 90-day and full calendar year reporting/performance period), or no later than the end of the calendar year (for a 90-day reporting/performance period only).
Medicaid EP: For more than 40 percent of transitions or referrals received and patient encounters in which the provider has never before encountered the patient, the EP incorporates into the patient's EHR an electronic summary of care document.
Medicaid EH/CAH: For more than 40 percent of transitions or referrals received and patient encounters in which the provider has never before encountered the patient, the EH or CAH incorporates into the patient's EHR an electronic summary of care document.
Numerator: Number of patient encounters in the denominator where an electronic summary of care record received is incorporated by the provider into the CEHRT.
Denominator: Number of patient encounters during the EHR reporting period for which an EP, EH, or CAH was the receiving party of a transition or referral or has never before encountered the patient and for which an electronic summary of care record is available.
Numerator: Summary of care record
Requested and available;
Received through query or request;
Incorporated into the record.
Number of patient encounters where the EP, EH or CAH was the receiving party of a transition or referral;
Number of patient encounters where the EP, EH, or CAH has never before encountered the patient;
Electronic summary of care record is available.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 8 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 9 – Medication/Clinical Information Reconciliation
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. Medication reconciliation will populate the numerator if it is performed for a transition of care that is received during the reporting/performance period. The Health IT Module will populate the numerator if the provider performs reconciliation no earlier than the first day of the calendar year of the reporting/performance period (for a 90-day reporting period only), during the reporting/performance period (for a 90-day and full calendar year reporting period), or no later than the end of the calendar year of the reporting/performance period (for a 90-day reporting period only).
Medicaid EP: For more than 80 percent of transitions or referrals received and patient encounters in which the provider has never before encountered the patient, the EP performs a clinical information reconciliation. The provider must implement clinical information reconciliation for the following three clinical information sets: (a) Review of the patient's medication, including the name, dosage, frequency, and route of each medication; (b) Review of the patient's known medication allergies; and (c) Review of the patient's current and active diagnoses.
Medicaid EH/CAH: For more than 80 percent of transitions or referrals received and patient encounters in which the EH/CAH has never before encountered the patient, the EH/CAH performs a clinical information reconciliation. The provider must implement clinical information reconciliation for the following three clinical information sets: (a) Review of the patient's medication, including the name, dosage, frequency, and route of each medication; (b) Review of the patient's known medication allergies; and (c) Current Problem list. Review of the patient's current and active diagnoses.
Denominator: Number of transitions of care or referrals during the EHR reporting period for which the EH or CAH inpatient or emergency department (POS 21 or 23) was the recipient of the transition or referral or has never before encountered the patient.
Numerator: Indication that medication, medication allergy, and problem list reconciliation occurred.
Provision of summary of care record of any type for an existing patient;
Number of transitions of care or referrals for which the EP was the recipient;
Number of patients the EP has not previously encountered.
Number of transitions of care or referrals for which the EH or CAH was the recipient;
Number of patients the provider has not previously encountered.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 9 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 10 – Computerized Provider Order Entry (CPOE) Medications
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when medication orders are ordered using computerized provider order entry (CPOE).
The CPOE measure is only applicable to EPs participating in the Medicaid Promoting Interoperability Program and EHs/CAHs participating in the Medicaid Promoting Interoperability Program only. EHs/CAHs who are participating in both the Medicaid and Medicare Promoting Interoperability Programs or just the Medicare Promoting Interoperability Program are exempt from this measure.
Medicaid EP/EH/CAH: More than 60 percent of medication orders created by the EP or authorized providers of the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period are recorded using CPOE.
Denominator: Number of medication orders created by the EP or authorized providers in the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Numerator: Medication order recorded using CPOE.
Denominator: Number of medication orders.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 10 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 11 – CPOE Laboratory
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when laboratory orders are ordered using CPOE.
Medicaid EP/EH/CAH: More than 60 percent of laboratory orders created by the EP or authorized providers of the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period are recorded using computerized provider order entry.
Numerator: Laboratory order recorded using CPOE.
Denominator: Number of laboratory orders.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 11 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 12 – CPOE Radiology/Diagnostic Imaging
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification. The Health IT Module will populate the numerator when diagnostic imaging orders are ordered using CPOE.
Medicaid EP/EH/CAH: More than 60 percent of diagnostic imaging orders created by the EP or authorized providers of the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period are recorded using CPOE.
Denominator: Number of diagnostic imaging orders created by the EP or authorized providers in the EH or CAH inpatient or emergency department (POS 21 or 23) during the EHR reporting period.
Numerator: Diagnostic Imaging order recorded using CPOE.
Denominator: Number of diagnostic imaging orders.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 12 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Required Test 14 – Verify Opioid Treatment Agreement
The test approach for this Required Test is health IT developer self-declaration. Health IT developers are required to assess their health IT against the full scope of the product’s required capabilities, including but not limited to regulatory/conformance expectation clarifications and interpretations set forth in the applicable Certification Companion Guides and other issued guidance. If the health IT developer has determined from the outcome of its own assessment that its product meets the required capabilities of the criterion, the developer must submit its self-declaration to the ONC-ATL.
Medicare Promoting Interoperability Program Measure (2019 only):
Medicare EH/CAH: For at least one unique patient for whom a Schedule II opioid was electronically prescribed by the EH or CAH using CEHRT during the EHR reporting period, if the total duration of the patient’s Schedule II opioid prescriptions is at least 30 cumulative days within a six-month look-back period, the EH or CAH seeks to identify the existence of a signed opioid treatment agreement and incorporates it into CEHRT.
Medicare Promoting Interoperability Program Measure English Statements (2019 only):
Numerator: The number of unique patients in the denominator for whom the EH or CAH seeks to identify a signed opioid treatment agreement and, if identified, incorporates the agreement in CEHRT.
Denominator: Number of unique patients for whom a Schedule II opioid was electronically prescribed by the EH or CAH using CEHRT during the EHR reporting period and the total duration of Schedule II opioid prescriptions is at least 30 cumulative days as identified in the patient’s medication history request and response transactions during a six-month look-back period.
Medicare Promoting Interoperability Program Measure Elements (2019 only):
Numerator: Number of unique patients the EH or CAH has identified a signed opioid treatment agreement for and incorporated into CEHRT.
Number of unique patients for whom a Schedule II opioid was electronically prescribed;
Number of unique patients who have a total duration of Schedule II opioids of at least 30 cumulative days within the previous six months.
MIPS Promoting Interoperability Performance Category Measures (2019 only):
For at least one unique patient for whom a Schedule II opioid was electronically prescribed by the MIPS EC using CEHRT during the performance period, if the total duration of the patient’s Schedule II opioid prescriptions is at least 30 cumulative days within a six-month look-back period, the MIPS EC seeks to identify the existence of a signed opioid treatment agreement and incorporates it into the patient’s electronic health record using CEHRT.
MIPS Promoting Interoperability Performance Category Measures English Statement ( 2019 only):
Numerator: The number of unique patients in the denominator for whom the MIPS EC seeks to identify a signed opioid treatment agreement and, if identified, incorporates the agreement in CEHRT. A numerator of at least one is required to fulfill this measure.
Denominator: Number of unique patients for whom a Schedule II opioid was electronically prescribed by the MIPS EC using CEHRT during the performance period and the total duration of Schedule II opioid prescriptions is at least 30 cumulative days as identified in the patient’s medication history request and response transactions during a six-month look-back period.
MIPS Promoting Interoperability Performance Category Measure Elements (2019 only):
Numerator: Number of unique patients the EC has identified a signed opioid treatment agreement for and incorporated into CEHRT.
The tester must evaluate the self-declaration documentation for compliance against its defined requirements for the criteria. The tester may require the health IT developer to list or reference its evidence/documentation from which the health IT developers has based its declaration of conformity.
Required Test 15 – Support Electronic Referral Loops by Receiving and Incorporating Health Information
The health IT developer records and creates five reports, one for each scenario. Note that the health IT developer may create each report for a single required test or it may create one report for all of the required tests for which it is seeking certification.
Medicare Promoting Interoperability Program Measure (Starting in 2019):
Medicare EH/CAH: For at least one electronic summary of care record received for patient encounters during the EHR reporting period for which an EH or CAH was the receiving party of a transition of care or referral, or for patient encounters during the EHR reporting period in which the EH or CAH has never before encountered the patient, the EH or CAH conducts clinical information reconciliation for medication, mediation allergy, and current problem list.
Medicare Promoting Interoperability Program Measure English Statements (Starting in 2019):
Denominator: Number of electronic summary of care records received using CEHRT for patient encounters during the EHR reporting period for which an EH or CAH was the receiving party of a transition of care or referral, and for patient encounters during the EHR reporting period in which the EH or CAH has never before encountered the patient.
Medicare Promoting Interoperability Program Measure Elements (Starting in 2019):
The number of electronic summary of care records with an indication that clinical reconciliation of medications, medications allergy, and current problem list occurred.
Number of electronic care summary records received where the EH or CAH was the receiving party of a transition or referral; and
Number of electronic care summary records received where the EH or CAH has never before encountered the patient.
Merit-based Incentive Payment System (MIPS) Promoting Interoperability Performance Category Measures (starting in 2019):
For at least one electronic summary of care record received for patient encounters during the performance period for which a MIPS eligible clinician was the receiving party of a transition of care or referral, or for patient encounters during the performance period in which the MIPS EC has never before encountered the patient, the MIPS EC conducts clinical information reconciliation for medication, medication allergy, and current problem list.
MIPS Promoting Interoperability Performance Category Measures English Statement (starting in 2019):
Denominator: Number of electronic summary of care records received using CEHRT for patient encounters during the performance period for which a MIPS EC was the receiving party of a transition of care or referral, and for patient encounters during the performance period in which the MIPS EC has never before encountered the patient.
MIPS Promoting Interoperability Performance Category Measure Elements (Starting in 2019):
The number of electronic summary of care records with an indication that clinical reconciliation of medications, medication allergy, and current problem list occurred.
Number of electronic care summary records received where the EC was the receiving party of a transition or referral; and
Number of electronic care summary records received where the EC has never before encountered the patient.
The tester verifies that each report, including the numerator, denominator, and resulting percentages, are created correctly and without omission and include sufficient detail to match the patients or actions in the numerator report to the measure’s denominator limitations. The tester ensures that the correct patients are included in the numerator and denominator. The tester will use the information provided in required Test 15 and use ONC Test Data Scenario(s) 1, 2, 3, 4, and 5.
Version 2.3 Updated on 06-15-2020
Added clarification on which Health IT Modules must test to the eligible professional (EP)/eligible clinician (EC) Individual, EC Group, and eligible hospital (EH)/critical access hospital (CAH) tests.
Clarified when actions must occur to increment the numerator.
Added references to the Quality Payment Program (QPP).
Added clarification on deduplication of patients and the transitive effect for the numerator on the EC Individual and Group calculation methods.
Added information about the self-testing option.
Modified the information on when actions must occur to populate the numerator based on recent The Centers for Medicare & Medicaid Services (CMS) guidance.
Added clarification on Health IT Module’s capability requirements on recording Taxpayer Identification Number (TIN)/ national provider identifier (NPI) combinations.
Added clarification on confirmation of receipt of a C-CDA by a receiving provider prior to incrementing the numerator.
Added links to measure-specific guidance.
Added clarification for patient education materials, Meaningful Use Stage 3 Objective 5 automated measure calculation eligibility.
Provided additional clarification for the patient-specific education measure regarding provider ability to configure systems based on patient information.
Added clarification on numerator inclusion for the patient-specific education measure, which provides certification guidance for the use of automation in the provision of patient-specific education materials.
Added clarification about flexibility for testing this criterion and developer expectations for measures to which the transitive effect applies when the Health IT Module is unable to differentiate actions at the TIN/NPI level.
Added clarification that both the EC Individual and EC Group calculation methods must be tested by a Health IT Module supporting the ACI and/or the ACI Transition calculation method(s). Modified the timely access requirement for the ACI Patient Access measure based on a CMS policy change per the QPP CY 2018 final rule (82 FR 53568).
Modified the information on when actions must occur to populate the numerator for Stage 3 measures starting in 2019 based on 2019 inpatient prospective payment systems (IPPS) Final Rule. Modified the name of the EHR Incentive Program to the Promoting Interoperability Program. Updated the Measure-Specific Guidance from CMS.
Modified the name of the Advancing Care Information Transition and Advancing Care Information measures to Promoting Interoperability Transition and Promoting Interoperability. Modified the information on when actions must occur to populate the numerator for Promoting Interoperability measures starting in 2019 based on the 2019 Physician Fee Schedule final rule.
Added a link to CMS FAQs on the new Medicare Promoting Interoperability opioid measures for eligible hospitals in 2019.
Added a link to CMS FAQs on the new Medicare Promoting Interoperability Support Electronic Referral Loops by Receiving and Incorporating Health Information measure for eligible hospitals in 2019.
Added text noting that the previously published CMS FAQs on the new opioid measures and the Support Electronic Referral Loop apply in the Promoting Interoperability performance category of the Merit-based Incentive Payment System (MIPS).
Based on the sunsetting of the 2014 Edition in the Cures Final rule explanations and clarifications related to Modified Stage 2 and ACI Transition were removed. Made changes to the naming terminology to align with CMS program updates including modifying the measure naming convention from Stage 3 to Medicare and/or Medicaid Promoting Interoperability Programs.
Certification Companion Guide: Automated measure calculation
This certification criterion was adopted at § 170.315(g)(2). Quality management system (§ 170.315(g)(4)) and accessibility-centered design (§ 170.315(g)(5)) need to be certified as part of the overall scope of the certificate issued to the product.
Measure-Specific Guidance from CMS
Medicare Promoting Interoperability Program and Dual Eligible Hospitals for 2019
Medicaid Medicare Promoting Interoperability Program -only EH for 2019
Medicaid Promoting Interoperability Program EP for 2019
Medicare EC Merit-based Incentive Program System (MIPS) Promoting Interoperability Performance Category for 2020
Technical outcome – A user can create a report that includes the numerator, denominator, and resulting percentage for each applicable percentage-based Promoting Interoperability Programs measure supported.
The gap certification eligibility of this criterion at § 170.315(g)(2) depends on any modifications to the certification criteria to which this criterion applies and relevant Medicare and Medicaid Promoting Interoperability Programs objectives and measures.
ONC administers the ONC Health IT Certification Program; CMS administers the Promoting Interoperability and Quality Payment Programs. Questions regarding requirements for the Promoting Interoperability and Quality Payment Programs should be directed to CMS.
ONC has issued an FAQ (#50) on testing and certification for the 2014 Edition automated numerator recording (§ 170.314(g)(1)) and automated measure calculation (§ 170.314(g)(2)) certification criteria for measures which are no longer included in the Promoting Interoperability criteria based for EHR reporting periods in 2015-2017 based on updates included in the CMS final rule. [see also 80 FR 62761, 80 FR 62785, 80 FR 62875] Although this FAQ references the 2014 Edition certification criteria for automated numerator recording and automated measure calculation, the policy applies to testing and certification for the 2015 Edition automated numerator recording (§ 170.315(g)(1)) and automated measure calculation (§ 170.315(g)(2)) certification criteria if the Health IT Module will be used to report on measures in 2016 and 2017.
The following measures are no longer applicable for CMS Promoting Interoperability Programs:
Send labs from EH to EP
CPOE Medications (EH and EC only)
CPOE Laboratory (EH and EC only)
CPOE Radiology/Diagnostic Imaging (EH and EC only)
Please refer to CMS’ Promoting Interoperability Programs webpage and Quality Payment Program webpage for more resources on specific measures.
Three Medicaid Promoting Interoperability Program measures are eligible for gap certification: 1) Required Test 10 – CPOE Medications ; 2) Required Test 11 – CPOE Laboratory; and 3) Required Test 11 – CPOE Radiology/Diagnostic Imaging.
The test for (g)(2) does not require a live demonstration of recording data and generating reports. Health IT developers may self-test their Health IT Modules(s) and submit the resulting reports to the ONC-ATL to verify compliance with the criterion. The test procedure specifies what reports must be submitted for each Required Test, as well as what the tester must verify within each report.
Health IT Modules are required to de-duplicate test patients when aggregating together data for the Eligible Clinician (EC) Group calculation method.
Health IT Modules that are testing for the MIPS Promoting Interoperability performance category calculation method must test for both the EC Individual and EC Group calculation methods.
Health IT Modules that are testing for the EC Individual and EC Group calculation methods are required to be able to record an EC’s TIN. Further, they are also required to be able to associate a single NPI with multiple TINs within a single instance, database, etc. of the Health IT Module. Health IT Modules that are testing for the Individual EP calculation method only are not required to record TIN or be able to associate a single NPI to multiple TINs.
For the EC Individual and Group calculation methods, actions that accrue to the numerator have a transitive effect across all of the TINs that an individual NPI is included in. For example, if an EC provides patient education materials to a patient under TIN A, they will receive credit in the numerator for TIN B as long as the same NPI is used in both TINs and the same Health IT Module (i.e. same database, instance, etc.) is used. The test data reflects this transitive effect.
The capability for technology to populate the numerator before, during, and after the reporting/performance period depends on the numerator and denominator statements for the Promoting Interoperability measure. Developers should refer to the numerator and denominator statements in the measure specification sheets provided by CMS’ Promoting Interoperability Programs webpage to determine the reporting/performance period technology needs to support. Regardless of whether an action must occur during the reporting/performance period or can occur outside of the reporting/performance period, all actions must occur during the calendar year of the reporting/performance period.
Starting in 2019, CMS has clarified that the numerator for the Medicare Promoting Interoperability Program EH/CAH measures is constrained to the EHR reporting period. The numerator action therefore must take place during the reporting period. Actions occurring outside of the reporting period, including after the calendar year will not count in the numerator.
Starting in 2019, a MIPS Promoting Interoperability performance category Measure numerator and denominator is constrained to the performance period chosen, with the exception of the Security Risk Analysis measure which may occur any time during the calendar year.
It is possible for the action of “record” in this certification criterion to be implemented in different ways. For example, “record” could comprise the ability of a centralized analytics Health IT Module to accept or retrieve raw data from another Health IT Module or Health IT Modules. Other possible methods could include a Health IT Module that accepts or retrieves raw data, analyzes the data, and then generates a report based on the analysis; a Health IT Module that separately tracks each capability with a percentage-based Promoting Interoperability measure and later aggregates the numbers and generates a report; or an integrated bundle of Health IT Modules in which each of the Health IT Modules that is part of the bundle categorizes relevant data, identifies the numerator and denominator and calculates, when requested, the percentage associated with the applicable Promoting Interoperability Programs measure. In each of these examples, the action of “record” means to obtain the information necessary to generate the relevant numerator and denominator. [see also FAQ #20]
What is required for certification for this criterion depends on the type of flexibility identified by CMS.
In some cases, CMS identifies certain measurement flexibilities that are limited to “either/or” options. In these cases, technology presented for certification must be able to calculate the percentage based on both identified options.
In cases where CMS has identified measurement flexibilities that are open-ended and dependent on a unique decision by an EP, EC, eligible hospital, or CAH at the practice/organization-level for a given EHR reporting period (such as: excluding certain orders from the CPOE measure because they are protocol/standing orders), then the technology presented for certification is not required to support every possible method of calculation in order to meet this certification criterion. Rather, the technology must support at least one calculation method for a certification criterion, as long as the technology supports all distinct options for measurement (such as including controlled substances in the eRx measure or not). We strongly encourage technology developers to work with their clients and to incorporate as many of these practice/organization-level open-ended flexibilities in the technology as appropriate to make the Promoting Interoperability measures as relevant as possible to their clients’ scopes of practice. [77 FR 54244–54245 and ONC FAQ #32]
We also apply to this 2015 Edition “automated measure calculation” criterion the clarification and guidance included for certification to the 2014 Edition “automated measure calculation” criterion in the 2014 Edition Release 2 rulemaking [79 FR 10920 and 54445].
A Health IT Module may be certified to only the ‘‘automated measure calculation’’ certification criterion (§ 170.315(g)(2)) in situations where the Health IT Module does not include a capability that supports a Promoting Interoperability Program percentage-based measure, but can meet the requirements of the ‘‘automated measure calculation’’ certification criterion.
An example of this would be an ‘‘analytics’’ Health IT Module where data is fed from other health IT, and the Health IT Module can record the requisite numerators, denominators and create the necessary percentage report as specified in the ‘‘automated measure calculation’’ certification criterion.
ONC-ACBs can certify a Health IT Module to either § 170.315(g)(1) or (g)(2) per FAQ #28. ONC-ACBs should refer to the scenarios outlined in FAQ #28 for further details.
The Support Electronic Referral Loops by Sending Health Information measure for the Medicare and Medicaid Promoting Interoperability Programs, and the MIPS Promoting Interoperability performance category require that the EP/EC/EH/CAH confirm receipt of the summary of care by the referred to provider in order to increment the numerator. The test data tests this baseline requirement by requiring that a Health IT Module demonstrate confirmation of receipt before incrementing the numerator. ONC does not require a specific method Health IT Modules should use to confirm receipt. Health IT Modules could use a number of methods, including but not limited to, the Direct Message Disposition Notification, a check box, report verifications, etc.
The test data used for this criterion is supplied by ONC and is organized into 5 Test Data scenarios, with a single set of 12 Test Cases. Health IT developers are required to use the ONC-supplied test data and may not modify the test case names.
The Medicare and Medicaid Promoting Interoperability Provide Patients Electronic Access to Their Health Information measure requires that two conditions be met in order to increment/populate the numerator: patient data must be available to view, download, or transmit AND it must be available to an API within 48 hours (EP) or 36 hours (EH/CAH). The MIPS Promoting Interoperability performance category Provide Patients Electronic Access to Their Health Information measure requires that two conditions be met in order to increment/populate the numerator: patient data must be available to view, download, or transmit AND it must be available to an API within 4 business days (EC). As such, Health IT Modules certified to only (e)(1) or certified to only (g)(8), (g)(9) or (g)(10) will be required to demonstrate that the product increments the denominator for the condition for which they are certified. For example, if the Test Case indicates that only view, download, or transmit was met, the numerator will increment for products certified to (e)(1) but will not increment for products certified to (g)(8), (g)(9) or (g)(10). Health IT Modules certified for (e)(1) AND (g)(8), (g)(9) or (g)(10) will be expected to increment the numerator as the measure specifies. Health IT Modules certified to only (e)(1) or certified to only (g)(8) (g)(9) or (g)(10) will be required to provide documentation during testing that demonstrates how the Health IT Module performs the calculation for its “portion” of the measure as a condition of passing testing. This documentation must also be made available with the health IT developer’s transparency statement regarding costs and limitations. Documentation should enable Eligible Professionals, Eligible Clinicians, Eligible Hospitals, and Critical Access Hospitals to determine how to correctly add together the numerator and denominator from systems providing each of the capabilities.
EH/CAH/EP Medicaid Promoting Interoperability Program patient education measure requires that patient educational material identified by the patient rather than the provider do not qualify for inclusion in the automated measure calculation. Providers may configure their health IT to automatically make available patient education materials based on patient-specific information. For numerator inclusion, the automated provision of patient-specific education materials must demonstrate that the health care provider can determine the clinical relevance of such materials, either at a clinician level, provider organization level, or both.
CMS has issued FAQ 22521 regarding the application of the transitive effect to certain MIPS Promoting Interoperability performance category measures. For the purposes of testing to this criterion, the test data is structured to differentiate actions between TIN/NPI combinations. However, Health IT Modules that are not able to differentiate actions between TIN/NPI combinations for the measures to which the transitive effect applies are not required to demonstrate this capability. ONC-ATLs may offer flexibility during testing regarding the transitive effect and focus on the outcome to ensure the correct numerator and denominator are calculated by the Health IT Module. At a minimum, developers of Health IT Modules unable to differentiate actions at the TIN/NPI level for those measures to which the transitive effect applies must provide sufficient documentation and explanation of alternate workflows to the ONC-ATL to demonstrate how actions taken by a provider relate to the numerator and denominator. Health IT developers must also provide documentation to providers on configuration and the logic for properly using the “automated measure calculation” functionality, including details on how the developer has implemented the transitive effect policy.
CMS has issued a series of FAQs that provide additional guidance on the new Medicare Promoting Interoperability Program opioid measures for EHs in 2019: Query of Prescription Drug Monitoring Program, and Verify Opioid Treatment Agreement. The FAQs also apply in 2019 for the new opioid measures in the MIPS Promoting Interoperability performance category.
CMS has issued a series of FAQs that provide additional guidance on the new Medicare Promoting Interoperability Program measure for EHs in 2019: Support Electronic Referral Loops by Receiving and Incorporating Health Information measure. The FAQs also apply in 2019 for the Support Electronic Referral Loops by Receiving and Incorporating Health Information measure in the MIPS Promoting Interoperability performance category.