# Checklist: the Security Risk Analysis and SAFER Guides attestations for hospitals from CY 2026

Eleven steps for eligible hospitals and critical access hospitals attesting under the Medicare Promoting Interoperability Program, after the FY 2026 IPPS final rule added a risk management attestation and moved the SAFER Guides measure to the eight 2025 guides.

Checklist · Healthcare · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## What changed for CY 2026

The FY 2026 IPPS/LTCH PPS final rule, published on August 4, 2025, made two changes to the Protect Patient Health Information objective for eligible hospitals and critical access hospitals (CAHs) beginning with the EHR reporting period in CY 2026. The Security Risk Analysis measure now needs a “yes” to having conducted security risk management as well as a “yes” to having conducted or reviewed a security risk analysis. The SAFER Guides measure now needs a “yes” to an annual self-assessment using all eight SAFER Guides published in January 2025 [1]. The same rule set the EHR reporting period for CY 2026 and later at a minimum of any continuous 180 days within the calendar year [1] [3].

## Who should use it

Promoting Interoperability program leads, CISOs, HIPAA security officials, and the clinical informatics leaders who own EHR safety. Steps are tied to the final rule or to the HIPAA Security Rule it points to; suggestions are labeled. The owner under each step is a typical assignment, not one the rule names. The FY 2027 IPPS final rule, published August 4, 2026, lists its Promoting Interoperability changes, and neither of these two measures is among them [7]. Status as checked on November 14, 2026. Not legal advice.

## The checklist

1. **Choose the CY 2026 EHR reporting period and confirm the security and SAFER work falls inside calendar year 2026.** (Promoting Interoperability program lead) The reporting period is a minimum of any continuous 180-day period within the calendar year from CY 2026 [3]. Actions for the Security Risk Analysis measure, and the SAFER self-assessment, may occur any time during the calendar year in which the reporting period falls [1].
2. **Brief executives that both measures are pass or fail: a “no” on either means the hospital is not a meaningful EHR user.** (Program lead to the CFO and CIO) Neither measure earns points [2]. CMS explains that a “no” on the Security Risk Analysis measure means the hospital does not meet the definition of a meaningful EHR user and faces a downward payment adjustment, and that from CY 2026 a hospital must attest “yes” to both the analysis and the risk management components [1].
3. **Conduct or review the HIPAA security risk analysis in 2026, making sure it covers the data created or maintained by certified EHR technology.** (HIPAA security official) The finalized measure requires conducting or reviewing a security risk analysis in accordance with 45 CFR 164.308(a)(1)(ii)(A), including the security of data created or maintained by CEHRT [1]. That section requires an accurate and thorough assessment of risks and vulnerabilities to ePHI [4].
4. **Record the encryption decision for EHR data: implemented, or the reason it is not reasonable and appropriate and the equivalent alternative used.** (HIPAA security official with the EHR technical team) The finalized measure text says the encryption specification at 45 CFR 164.312(a)(2)(iv) must be implemented if reasonable and appropriate, and otherwise an equivalent alternative adopted if reasonable and appropriate [1], following the addressable-specification rule in 45 CFR 164.306(d)(3) [5].
5. **Before attesting to the new risk management component, check that measures from the risk analysis were actually put in place during the year, and keep the evidence.** (CISO with system owners) From CY 2026 the measure also requires security risk management activities under 45 CFR 164.308(a)(1)(ii)(B) [1], which requires security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level [4]. CMS declined a phase-in, noting that HIPAA has required risk management since 2003 [1]. What evidence to keep (remediation tickets, a risk register, sign-offs) is our suggestion.
6. **Keep the risk analysis and risk management records for at least six years.** (Compliance and records management) The HIPAA Security Rule requires required assessments to be documented and kept for 6 years from creation or from when they were last in effect, whichever is later [6].
7. **Use the eight 2025 SAFER Guides, not the nine 2016 guides, for the CY 2026 self-assessment.** (Chief medical information officer) The finalized measure requires an annual self-assessment using all eight 2025 SAFER Guides from the CY 2026 reporting period; CMS said the 2016 guides applied for CY 2025 [1]. ASTP’s SAFER Guides page, as checked on November 14, 2026, still says the 2016 versions apply to the program measures [8]; the final rule is what sets the measure, and the eCFR text at 42 CFR 495.24(e)(4)(iv) still refers to nine guides [2].
8. **Give each guide an owner: the two foundational guides, the two infrastructure guides and the four clinical process guides.** (CMIO, CNIO and IT operations) The 2025 set is organized as foundational (High Priority Practices, Organizational Responsibilities), infrastructure (Contingency Planning, System Management) and clinical process guides (Patient Identification, Computerized Provider Order Entry with Decision Support, Test Results Reporting and Follow-Up, Clinician Communication); the Organizational Responsibilities guide now covers AI-enabled systems [8]. Splitting ownership this way is our suggestion.
9. **Complete all eight self-assessments, record the date, and attest “yes”; send the gaps found into the hospital’s improvement plan.** (CMIO with patient safety) CMS states the measure requires attesting to having conducted the self-assessment and sets no required implementation status for any practice in the guides [1]. Acting on gaps is our suggestion, not a measure requirement.
10. **Keep the two exercises separate: do not count a SAFER self-assessment as the security risk analysis, or the reverse.** (CISO and CMIO) CMS states that a SAFER Guides self-assessment would not constitute a complete security risk analysis, and a security risk analysis would not constitute a self-assessment using the complete set of SAFER Guides [1].
11. **Plan CY 2027 attestations with the FY 2027 IPPS final rule, and keep watching the proposed HIPAA Security Rule changes, which CMS said could lead it to revisit the risk analysis measure.** (Program lead and HIPAA security official) The FY 2027 rule lists its program changes, including removal of the ONC Direct Review and ONC-ACB surveillance attestations and a modified Electronic Prior Authorization measure, without changes to these two measures [7]. The FY 2026 rule notes that HHS’s January 2025 proposal to change the HIPAA Security Rule had not been finalized when it was published, and that if it is finalized CMS will consider whether the measure needs to change [1].

## Sources

1. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). FY 2026 IPPS/LTCH PPS final rule (90 FR 36536, August 4, 2025), Medicare Promoting Interoperability Program sections. <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 for 2019 and subsequent years. <https://www.ecfr.gov/current/title-42/section-495.24> Checked November 14, 2026.
3. Electronic Code of Federal Regulations. 42 CFR 495.4, Definitions (EHR reporting period). <https://www.ecfr.gov/current/title-42/section-495.4> Checked November 14, 2026.
4. Electronic Code of Federal Regulations. 45 CFR 164.308, Administrative safeguards. <https://www.ecfr.gov/current/title-45/section-164.308> Checked November 14, 2026.
5. Electronic Code of Federal Regulations. 45 CFR 164.306, Security standards: General rules. <https://www.ecfr.gov/current/title-45/section-164.306> Checked November 14, 2026.
6. Electronic Code of Federal Regulations. 45 CFR 164.316, Policies and procedures and documentation requirements. <https://www.ecfr.gov/current/title-45/section-164.316> Checked November 14, 2026.
7. Centers for Medicare & Medicaid Services, Federal Register (via GovInfo). FY 2027 IPPS/LTCH PPS final rule (August 4, 2026), summary of Medicare Promoting Interoperability Program changes. <https://www.govinfo.gov/content/pkg/FR-2026-08-04/html/2026-15833.htm> Checked November 14, 2026.
8. 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.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-hospital-promoting-interoperability-security-attestations>
Publisher: Moraph Insights
