Make Both 2026 Attestations a “Yes”
For the 2026 performance year, the Security Risk Analysis measure sits inside the Promoting Interoperability category of Medicare’s Merit-based Incentive Payment System. It is required but unscored: it adds no points, yet the category scores zero if either attestation is missing. The checklist has two items, and both must be answered “Yes” when you report.
- You conducted or reviewed a security risk analysis in line with the HIPAA Security Rule at 45 CFR 164.308(a)(1), including the security of data in your certified EHR technology, such as encryption.
- You carried out security risk management — implementing updates and correcting identified deficiencies to reduce risks to a reasonable and appropriate level.
The first item is not a generic IT review. It is the same HIPAA duty that underlies a proper hipaa security risk assessment, and the second item asks for follow-through. A practice can produce a polished analysis and still fail the MIPS measure if it cannot show that it acted on the findings. Treat the two attestations as a pair: document the analysis or review, then document the risk-management work that followed. The phrase “conducted or reviewed” gives some flexibility, but it does not turn the attestation into a paperwork-only exercise.
Place the Analysis or Review Inside the 2026 Calendar Year
CMS expects the analysis to be conducted or reviewed within the calendar year of the performance period and to cover that period. For the 2026 performance year, that means the work must fall within 2026; it does not need to sit inside the 180-day reporting window used for other measures. It can happen before or after that window, as long as it is in the same calendar year. The practical point is to schedule the work deliberately rather than treating last year’s document as a renewable filing.
You may review an existing analysis during 2026. That is a legitimate route, but the review must be real: document the review, update the analysis where needed, and complete the required risk-management activities. Merely re-submitting last year’s document does not establish a current-year review. A useful calendar entry is a review block in 2026 with three outputs: a dated review record, an updated analysis where changes are needed, and a risk-management log showing what was fixed or updated. If the analysis and the risk-management work happen at different points in the year, connect them in the file so an auditor can follow the sequence.
Confirm Whether You Must Attest, or Whether Reweighting or an Exception Applies
The measure applies to MIPS eligible clinicians, groups, and APM entities that report the Promoting Interoperability category. Before building the attestation into your reporting workflow, confirm that the category actually applies. Two routes can take a practice out of it. Automatic reweighting requires no application for clinicians and groups with one of CMS’s special statuses — small practice, hospital-based, ambulatory surgical center-based, or non-patient facing — and Promoting Interoperability is reweighted to 0%, so no data needs to be submitted for it. Check your status in the QPP Participation Status Tool.
Others may need a hardship exception application by December 2026, for example for decertified EHR technology, insufficient internet connectivity, extreme and uncontrollable circumstances, or lack of control over certified EHR technology. CMS must approve the exception. In either route, a qualifying Promoting Interoperability data submission cancels the reweighting or exception, and the category is scored. One more distinction matters: an exception from MIPS reporting is not an exception from HIPAA. The Security Rule risk analysis is still required.
Keep Audit-Ready Evidence for the Attestations and for HIPAA
Attestations can be audited, so the evidence file should answer two questions: what did you do in 2026, and how do you know it was done? Keep the dated analysis, the risk management plan, and proof of the fixes made during the year. That proof does not need to be elaborate, but it should be specific enough to show implementation rather than intention. A dated review memo, an updated analysis, a risk-management plan with owners and status, and records showing the corrective work completed during the year form a coherent packet.
For both attestations, the evidence should align. If the risk-management attestation is “Yes” because a deficiency was corrected, the file should show the correction. If the analysis was reviewed, the file should show the review date and what changed. HIPAA separately requires keeping risk analysis documentation for six years under 45 CFR 164.316. That retention rule is a floor, not a filing suggestion. Keep the evidence where it can be retrieved without reconstructing the year from memory, and make sure the packet distinguishes the analysis from the attestation. The MIPS attestation is a statement about the year; the HIPAA documentation is the substantiation.
Note the 2027 Removal Without Dropping the HIPAA Duty
CMS’s CY 2027 Physician Fee Schedule final rule, published in November 2026, removes the Security Risk Analysis measure beginning with the 2027 performance year and the 2029 MIPS payment year. CMS’s reason is reporting burden: MIPS eligible clinicians are covered entities, and the same risk analysis and risk management are already required by the HIPAA Security Rule, which the HHS Office for Civil Rights enforces. In the same rule, CMS reminds clinicians to keep conducting the security risk analysis and risk management.
For the 2026 performance year, the attestation still applies, so the checklist above remains the operating plan. From 2027, there is no MIPS attestation, but the HIPAA duty is the same. OCR can still ask for your risk analysis and risk management documentation, and the six-year retention rule still applies. The removal changes the reporting form, not the underlying obligation. A practice that uses 2026 to build a clean, dated evidence trail will be in a stronger position for both the current attestations and the HIPAA requirements that continue afterward.
Osaka quantum-physics postdoc now freelancing from Lisbon’s azulejo-lined alleys. Kaito unpacks quantum sensing gadgets, fado lyric meanings, and Japanese streetwear economics. He breakdances at sunrise on Praça do Comércio and road-tests productivity apps without mercy.