Source: https://www.healthit.gov/test-method/automated-numerator-recording
Timestamp: 2020-07-16 14:18:27
Document Index: 70173842

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

Automated numerator recording | HealthIT.gov
§170.315(g)(1) Automated numerator recording
Version 2.4 Updated on 06-01-2020
Removed incorrect references to a denominator.
Added an attestation requirement around documentation provided to end users.
Added an attestation requirement around documentation provided related to the end user’s system’s ability to calculate the different methods.
Removed 2nd bullet under the Advancing Care Information (ACI) Measure English Statement of the Required Test 6 - Patient Generated Health Data section.
Removed the wording "of of" before 'the following' within the first sentence of the Required Attestation section.
Clarified the View, Download, Transmit Measure for ACI to describe the action as being taken by the patient or patient-authorized representative rather than the Eligible Clinician (EC) per the Quality Payment Program (QPP) Calendar Year (CY) 2018 Final Rule (82 FR 53568).
Made the following changes based on CMS policy changes per the CY 2019 Hospital Inpatient PPS final rule (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.
Removed the reference to tax identifier number and national provider identifier (TIN/NPI) in the Required Tests organization section as it is not applicable to g1.
Per the CY2020 Physician Fee Schedule (PFS) Final Rule, removed Required Test 13 for ECs and updated Required Test 14 to note it is only applicable in 2019 for ECs.
Per the ONC Cures Act Final Rule removed the Modified Stage 2 and Advancing Care Information (ACI) Transition measures.
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 Medicaid EH/CAH measure description.
§170.315 (g)(1) Automated numerator recording—
For each Promoting Interoperability Programs percentage-based measure, technology must be able to create a report or file that enables a user to review the patients or actions that would make the patient or action eligible to be included in the measure's numerator. The information in the report or file created must be of sufficient detail such that it enables a user to match those patients or actions to meet the measure's denominator limitations when necessary to generate an accurate percentage.
See the file "§170.315(g)(1) EH/CAH" below under the Attachments section. Last updated on 06-15-2020.
See the file "§170.315(g)(1) EP/EC" below under the Attachments section. Last updated on 06-15-2020.
§170.315(g)(1) EH/CAH 06-15-2020
§170.315(g)(1) 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 also encouraged to consult the Certification Companion Resource in tandem with the test procedure as they both provide clarifications that may be useful for product development and testing.
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 the 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.
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 Merit-based Incentive Payment System (MIPS) Promoting Interoperability performance category (TIN/NPI). Health IT Modules that are inpatient systems only must use the EH test data and, if the inpatient system is used in the ambulatory setting, the ambulatory test and test at least one of two calculation methods: 1) Medicaid Promoting Interoperability Program 3; or 2) Merit-based Incentive Payment System (MIPS) Promoting Interoperability performance category. Health IT Modules that are both ambulatory and inpatient systems must use the EH 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 testing requirements for the relevant Medicaid Promoting Interoperability Program measures.
For Measure-Specific Sections
Within each of the measure-specific sections, the test procedure addresses the capability to record the numerator for § 170.315(g)(1) for each measure for Medicare and Medicaid Promoting Interoperability Programs and the MIPS Promoting Interoperability performance category measures:
Record – evaluates the capability to electronically record the numerator for each objective with a percentage-based measure.
The health IT developer records all numerator measure elements for the method(s) by which the Health IT Module records the numerator for each measure.
Report – evaluates the capability to create a report that includes the numerator 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 it is presenting for testing.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator 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.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator 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.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator for each measure based on the supplied test data from Test Data Scenario 3 (populate numerator) across all required tests. The report must also include the list of patients included in the numerator.
Using the functions of the Health IT Module, the health IT developer creates a report that includes the numerator for each measure based on the supplied test data from Test Data Scenario 4 (do not populate numerator) across all required tests. The report must also include the list of patients included in the numerator.
The health IT developer submits all four reports to the tester for review.
The tester verifies that the increments in the numerator 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 for each measure.
The test data for § 170.315(g)(1) 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 eight 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 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.
Health IT developers with Health IT Modules certified to (g)(1) are required to attest that they have provided to other health IT developers and end-users documentation, including the following as applicable:
Identify and acknowledge specific situations where the Health IT Module certified to (g)(1) does not have access to information that allows the module to determine if a numerator should be incremented or decremented for a measure.
Identify and acknowledge that the Health IT Module does not record TIN/NPIs and that the health IT developer or end-user is responsible for calculating performance at the TIN/NPI or group TIN for Promoting Interoperability measures.
For ambulatory only systems or inpatient/ambulatory systems, identify and acknowledge the Health IT Module is not certified or deemed to (g)(1) for both calculation methods 1) Medicaid Promoting Interoperability Program; or 2) Merit-based Incentive Payment System (MIPS) Promoting Interoperability performance category (TIN/NPI.
Required Test 1 – ePrescribing
The health IT developer records and creates two 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.
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 terminology (CEHRT).
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.
EC: At least one permissible prescription written by the MIPS EC is queried for a drug formulary and transmitted electronically using certified EHR technology.
Merit-based Incentive Payment System (MIPS) Promoting Interoperability Performance Category Measure Elements:
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 1 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates two 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 Programs: 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 EH or CAH.
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), (g)(9) or (g)(10) 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 EH/CAH: For more than 80 percent of all unique patients discharged from the EH 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 EH 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.
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 meet the technical specifications of the API in the provider's CEHRT.
Date and time information made available online to the patient;
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 CEHRT.
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 2a, 2b, or 2c and use ONC Test Data Scenario(s) 1, 2, 3, and 4. The tester verifies that all of the required information below is made available to patients.
The health IT developer records and creates two 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 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).
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 3 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates four 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 (g)(8), (g)(9), or (g)(10) 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 electronic health record (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).
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, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 4a, 4b, or 4c and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates four 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 EH/CAH: 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.
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 5 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
Stage 3 Objective 6 Measure 3
Promoting Interoperability Objective 4 Measure 3
The health IT developer records and creates four 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.
The tester verifies that each report, including the numerator, 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. The tester will use the information provided in required Test 6 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates four 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 who transitions or refers his or her 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 its 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 EH or CAH that transitions or refers its 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.
For at least one transition of care or referral, the MIPS EC that transitions or refers his or her patient to another setting of care or health care provider (1) creates a summary of care record using CEHRT; and (2) electronically exchanges the summary of care record.
The tester verifies that each report, including the numerator, 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. The tester will use the information provided in required Test 7 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
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 and inpatient settings:
The health IT developer records and creates four 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).
Numerator: Number of transitions of care or referrals in the denominator where an electronic summary of care record received is incorporated by the provider into the CEHRT.
The tester verifies that each report, including the numerator, 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. The tester will use the information provided in required Test 8 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates four 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).
The tester verifies that each report, including the numerator, 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. The tester will use the information provided in required Test 9 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
The health IT developer records and creates four 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 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 participate in both the Medicaid and Medicare Promoting Interoperability Programs or just the Medicare Promoting Interoperability Program are exempt from this measure.
Numerator: The number of medication orders recorded using CPOE.
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 10 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
Required Test 11 – Computerized Provider Order Entry (CPOE) Laboratory
The health IT developer records and creates four 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.
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 participate 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 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 CPOE.
Numerator: The number of laboratory orders recorded using CPOE.
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 11 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
Required Test 12 – Computerized Provider Order Entry (CPOE) Radiology/Diagnostic Imaging
The health IT developer records and creates four 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.
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.
Numerator: The number of diagnostic imaging orders recorded using CPOE.
The tester verifies that each report, including the numerator, is created correctly and without omission and includes 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. The tester will use the information provided in required Test 12 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
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 EHR using CEHRT.
MIPS Promoting Interoperability Performance Category Measures English Statement (2019 only):
The tester must evaluate the self-declaration documentation for compliance against its defined requirements for the criteria. The tester may require the developer to list or reference its evidence/documentation from which the health IT developer has based its declaration of conformity.
The health IT developer records and creates four 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.
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.
Numerator: The number of electronic summary of care records with an indication that clinical reconciliation of medications, medications allergy, and current problem list occurred.
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 EC 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.
The tester verifies that each report, including the numerator, 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. The tester will use the information provided in required Test 15 and use ONC Test Data Scenario(s) 1, 2, 3, and 4.
Added clarification on which Health IT Modules must test to the EP/EC Individual, EC Group, and EH/CAH tests.
Clarified how Health IT Modules must test for Required Test 2, and the documentation that they must submit.
Added references to the QPP.
Modified the information on when actions must occur to populate the numerator based on recent CMS guidance.
Removed bullet point related to testing when systems are an ambulatory systems only or an inpatient systems only.
Added clarification on Health IT Module’s capability requirements on recording TIN/NPI combinations.
Added clarification for patient education materials, MU3 Objective 5 Measure 2 numerator eligibility.
Modified the information on when actions must occur to populate the numerator for Stage 3 measures starting in 2019 based on 2019 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 PFS final rule.
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 MIPS.
Certification Companion Guide: Automated numerator recording
This certification criterion was adopted at § 170.315(g)(1). 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.
Technical outcome – A user must be able to create a report or file to review patients or actions that would make the patient or action eligible to be included in a Promoting Interoperability Programs percentage-based measure’s numerator. The user must be able to use the information in the report or file to match those patients or actions to meet the measure’s denominator limitations.
The gap certification eligibility of this criterion at § 170.315(g)(1) 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 has issued 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 Stage 2 measures are no longer applicable for the CMS Promoting Interoperability Programs:
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)(1) 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.
Starting in 2019, CMS has clarified that the numerator for the Medicare Stage 3 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.
The test data used for this criterion is supplied by ONC and is organized into 4 Test Data scenarios, with a single set of 8 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 numerator. 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 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 Promoting Interoperability performance category of MIPS.
CMS has issued 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 Promoting Interoperability performance category of MIPS.