# The hospital Promoting Interoperability security measures after the FY 2026 IPPS final rule, explained

From the CY 2026 EHR reporting period, eligible hospitals and critical access hospitals must attest yes to both a security risk analysis and security risk management, and to a self-assessment using all eight 2025 SAFER Guides.

Explainer · Healthcare · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Set in the FY 2026 IPPS/LTCH PPS final rule, published August 4, 2025 (90 FR 36536) and effective October 1, 2025.
- Applies to eligible hospitals and critical access hospitals (CAHs) in the Medicare Promoting Interoperability Program, beginning with the EHR reporting period in CY 2026.
- Security Risk Analysis measure: two separate yes attestations, one for conducting or reviewing a security risk analysis and one for conducting security risk management, under 45 CFR 164.308(a)(1)(ii)(A) and (B).
- SAFER Guides measure: an annual self-assessment using all eight 2025 SAFER Guides, published by ASTP/ONC in January 2025, in place of the nine 2016 guides.
- The Security Risk Analysis measure earns no points; a no on either component means the hospital is not a meaningful EHR user and faces a downward payment adjustment. A yes on the SAFER Guides measure is also required to be considered a meaningful EHR user.

## Where the two measures fit

Both measures belong to the Protect Patient Health Information objective of the Medicare Promoting Interoperability Program for eligible hospitals and CAHs. The objective is to protect electronic protected health information created or maintained by certified EHR technology through the implementation of appropriate technical, administrative and physical safeguards [2]. The Security Risk Analysis measure is not scored and contributes no points to the objective [1].

The FY 2026 IPPS/LTCH PPS final rule made three changes that matter here [1]:

- it set the EHR reporting period for CY 2026 and later years at a minimum of any continuous 180-day period within the calendar year, amending 42 CFR 495.4;
- it modified the Security Risk Analysis measure, with modifications to the proposal, beginning with the EHR reporting period in CY 2026; and
- it modified the SAFER Guides measure beginning with the EHR reporting period in CY 2026.

The rule took effect on October 1, 2025 [1].

## Security risk analysis becomes analysis plus management

Before this rule, the measure asked hospitals to attest yes or no to having conducted or reviewed a security risk analysis, as the HIPAA Security Rule requires at 45 CFR 164.308(a)(1)(ii)(A). A yes was required to be a meaningful EHR user and avoid a downward payment adjustment [1]. CMS noted that, as of the CY 2025 reporting period, the measure did not require hospitals to manage their security risk or to attest to having implemented security measures to manage it [1].

The HIPAA risk management implementation specification, at 45 CFR 164.308(a)(1)(ii)(B), requires security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. From CY 2026, the measure adds that component. As finalized, it reads in part: first, conduct or review a security risk analysis and second, conduct security risk management activities, in accordance with 45 CFR 164.308(a)(1)(ii)(A) and (B) [1]. The finalized text also says:

- security risk analysis and management activities include addressing the security of data created or maintained by certified EHR technology, including encryption, under 45 CFR 164.312(a)(2)(iv) and 164.306(d)(3);
- encryption must be implemented if it is reasonable and appropriate, and if it is not, the hospital would adopt an equivalent alternative measure if that is reasonable and appropriate; and
- actions may occur any time during the calendar year in which the EHR reporting period occurs [1].

CMS proposed that a hospital attest yes separately to each component, and finalized the proposal with clarified wording for the measure text. A no to the risk analysis component, the risk management component, or both, means the measure is not met, the hospital does not satisfy the definition of a meaningful EHR user under 42 CFR 495.4, and it is subject to a downward payment adjustment. Scoring does not change [1].

CMS also noted that the HIPAA Security Rule does not prescribe a specific methodology for conducting and documenting a risk analysis or managing risk, and pointed to resources from HHS’s Office for Civil Rights, NIST SP 800-66 Revision 2 and the HHS 405(d) program [1]. In our view, the practical effect is that the attestation now reaches the remediation record, not the analysis report alone: the evidence a hospital keeps should show what was found and what was done about it.

## SAFER Guides: eight 2025 guides replace nine 2016 guides

CMS adopted the SAFER Guides measure in the FY 2022 IPPS/LTCH PPS final rule, beginning with the EHR reporting period in CY 2022. In the FY 2024 rule it required hospitals, from CY 2024, to attest yes to an annual self-assessment using all nine 2016 SAFER Guides to be considered meaningful EHR users [1].

In January 2025, ASTP/ONC published the 2025 SAFER Guides: eight guides in three groups, all edited, with new recommendations and with overlapping 2016 recommendations consolidated [1]. ASTP lists them as [3]:

- **Foundational:** High Priority Practices; Organizational Responsibilities, which now addresses AI-enabled systems.
- **Infrastructure:** Contingency Planning; System Management, which combines the former System Configuration and System Interfaces chapters [1].
- **Clinical process:** Patient Identification; Computerized Provider Order Entry with Decision Support; Test Results Reporting and Follow-Up; Clinician Communication.

The final rule requires hospitals and CAHs to conduct an annual self-assessment using all eight 2025 SAFER Guides at any point during the calendar year in which the EHR reporting period occurs, beginning with CY 2026 [1]. For CY 2025, CMS said hospitals should continue to use the 2016 guides [1].

Contingency Planning covers planned or unplanned EHR unavailability, and System Management covers configuration, validation and maintenance of EHR hardware, software and system-to-system application programming interfaces [3]. In our view, those two guides overlap most with the work of security and resilience teams.

## Three things to reconcile

- **The regulation text.** The FY 2026 rule’s amendments to part 495 changed 42 CFR 495.4; the measure changes are set out in the preamble [1]. As shown in the eCFR on November 14, 2026, the only hospital measure text for these two measures in 42 CFR 495.24 is in paragraph (e)(4), which applies to 2019 through 2022 and describes the security risk analysis measure in its earlier form and the SAFER Guides measure as a self-assessment using all nine SAFER Guides. Paragraph (f), for 2023 and later years, requires hospitals to meet the objectives and measures CMS selects for an EHR reporting period [2].
- **The ASTP page.** The SAFER Guides page, last updated February 27, 2026, says the 2016 versions continue to be applicable for the SAFER Guides measures in the Medicare Promoting Interoperability Program and MIPS [3]. The final rule says the 2025 guides apply to hospitals from the CY 2026 reporting period [1]. As checked on November 14, 2026, the two sources conflict; CMS’s current specification sheets are where to confirm which set an attestation covers.
- **The next rule.** The FY 2027 IPPS/LTCH PPS final rule was published August 4, 2026 and is effective October 1, 2026. A search of its text on November 14, 2026 found no mention of the Security Risk Analysis or SAFER Guides measures [4].

The companion [Security Risk Analysis and SAFER Guides attestation checklist](https://insights.moraph.com/checklist-hospital-promoting-interoperability-security-attestations) sets out the steps in order. This explainer describes the program rules; it is not legal advice, and hospitals should confirm with counsel and their CMS resources how the measures apply to them.

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). FY 2026 IPPS/LTCH PPS final rule (90 FR 36536), CMS-1833-F. <https://www.govinfo.gov/content/pkg/FR-2025-08-04/html/2025-14681.htm> Checked November 14, 2026.
2. Electronic Code of Federal Regulations. 42 CFR 495.24, Stage 3 meaningful use objectives and measures for EPs, eligible hospitals and CAHs. <https://www.ecfr.gov/current/title-42/section-495.24> Checked November 14, 2026.
3. Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT. SAFER Guides. <https://healthit.gov/clinical-quality-and-safety/safer-guides/> Checked November 14, 2026.
4. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). FY 2027 IPPS/LTCH PPS final rule (FR Doc. 2026-15833). <https://www.govinfo.gov/content/pkg/FR-2026-08-04/html/2026-15833.htm> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/hospital-promoting-interoperability-security-risk-analysis-safer-guides-explained>
Publisher: Moraph Insights
