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.
Clarifications:
- There is no standard required for this certification criterion.
- ONC administers the ONC Health IT Certification Program; CMS administers the Medicare Promoting Interoperability Program and the Quality Payment Program's (QPP) Merit-based Incentive Payment System (MIPS) Promoting Interoperability Performance Category.
- Questions regarding program requirements for the Medicare Promoting Interoperability Program and QPP MIPS Promoting Interoperability performance category should be directed to CMS.
- Please refer to CMS’ Promoting Interoperability Programs webpage and Quality Payment Program webpage for more resources on specific measures.
- The test for (g)(1) does not require a live demonstration of recording data and generating reports. 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.
- 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.
- Starting in 2019, CMS has clarified that the numerator for the Medicare Stage 3 Eligible Hospital/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.
- 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 Promoting Interoperability Program's 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 36 hours (Eligible Hospital/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 (Eligible Clinician). As such, Health IT Modules certified to only (e)(1) or certified to only (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)(9), or (g)(10). Health IT Modules certified for (e)(1) AND (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)(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.
- The "Support Electronic Referral Loops by Sending Health Information" measure for the Medicare Promoting Interoperability Programs, and the MIPS Promoting Interoperability performance category require that the Eligible Professional/Eligible Clinician/Eligible Hospital/Critical Access Hospital 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 Medicaid Promoting Interoperability Program ended January 2022, the required tests that only supported the Medicaid Promoting Interoperability Program were removed.