Atlassian Data Center: no new expansions after March 30, 2028. Plan your migration →

HIPAA Security Rule Update Delayed to 2027: What Healthcare IT Should Do Now

The HIPAA Security Rule update now targets July 2027. Here is what the proposal requires and the controls healthcare IT should build now.

HIPAA Security Rule update delayed to 2027, VTPMO Insights card for healthcare IT leaders

The HIPAA Security Rule update that the HHS Office for Civil Rights (OCR) proposed in December 2024 is still not final. The latest federal regulatory agenda lists the final action for July 2027. For hospitals, health plans, Medicaid agencies, and their business associates, that delay is not a pause button. Instead, it is a window to build the controls that OCR already enforces today.

This article explains where the rule stands, what the proposal would require, and a practical plan healthcare IT leaders can start this quarter.

Where the HIPAA Security Rule update stands

OCR announced the proposed rule on December 27, 2024. It was published in the Federal Register on January 6, 2025, at 90 FR 898. It is the first major revision of the Security Rule in over two decades.

The current Unified Agenda entry for the rule (RIN 0945-AA22) lists it under long-term actions. It is marked economically significant, and the final action date is shown as July 2027. Agenda dates are planning targets, not legal deadlines. So OCR could move sooner, later, or issue a narrower final rule.

Meanwhile, the existing Security Rule still applies in full. OCR also continues to settle cases where organizations skipped the basics. In June 2026, OCR announced its 14th enforcement action under its Risk Analysis Initiative. In other words, regulators are not waiting for the new rule to hold organizations accountable.

What the HIPAA Security Rule update would require

According to the HHS fact sheet, the proposal turns many of today’s flexible safeguards into specific, testable requirements. The most important changes for IT teams are listed below.

Proposed requirementWhat it means in practice
Remove the “addressable” labelNearly all implementation specifications become required, with limited exceptions.
Technology asset inventory and network mapDocument every system that touches ePHI and how data moves. Review at least every 12 months and after changes.
Written risk analysisIdentify reasonably anticipated threats and vulnerabilities, then rate each risk by likelihood.
EncryptionEncrypt ePHI at rest and in transit, with limited exceptions.
Multi-factor authenticationRequire MFA, with limited exceptions.
Vulnerability scanning and penetration testingScan at least every six months. Test at least every 12 months.
Network segmentationSeparate systems so one compromise does not spread.
Recovery within 72 hoursKeep written procedures to restore certain systems and data within 72 hours.
Annual compliance auditAudit Security Rule compliance at least every 12 months.
Business associate verificationBusiness associates verify their safeguards at least every 12 months, with a written analysis and certification.
Access change noticeCertain entities must be notified within 24 hours when a workforce member’s access changes or ends.

OCR also proposed that all Security Rule policies, procedures, plans, and analyses be documented in writing. As a result, “we do this informally” will no longer be a defensible answer.

Why waiting for the final rule is a mistake

First, most of these controls are already good practice. NIST SP 800-66 Revision 2 maps the current Security Rule to the NIST Cybersecurity Framework. Therefore, work you do now counts under today’s rule and the proposed one.

Second, the hard items take time. An accurate asset inventory, a tested 72-hour recovery plan, and MFA everywhere are multi-quarter projects. If the final rule keeps a short compliance window, late starters will be squeezed.

Third, ransomware remains the main threat. OCR’s recent settlements repeatedly cite a missing or incomplete risk analysis. Even if the final rule changes, those findings will not.

A 90-day HIPAA Security Rule update plan for healthcare IT

The goal for the next 90 days is simple. Build the evidence base that any version of the HIPAA Security Rule update will ask for.

Days 1 to 30: Know what you have

  • Build or refresh the technology asset inventory for every system that creates, receives, stores, or transmits ePHI.
  • Draw a current network map, including cloud services, vendor connections, and remote access paths.
  • List business associates and the ePHI each one handles.
  • Assign a named owner for each critical system.

Days 31 to 60: Close the biggest gaps

  • Update the written risk analysis using the new inventory and map.
  • Measure MFA and encryption coverage, then plan to close the gaps.
  • Schedule vulnerability scans on a six-month cycle and book an annual penetration test.
  • Automate access removal through your identity platform so changes take effect quickly.

Days 61 to 90: Prove it works

  • Run a recovery exercise against your top clinical and claims systems, and record the actual restore time.
  • Review segmentation between clinical, business, and guest networks.
  • Collect written assurances from key business associates.
  • Brief leadership on remaining gaps, cost, and a 12-month roadmap.

Above all, keep the evidence. Screenshots, reports, tickets, and signed reviews are what auditors and investigators ask for first.

How this fits with other healthcare deadlines

Many payers and state Medicaid agencies are also building new interfaces under the CMS Interoperability and Prior Authorization rule. Each new API adds systems to your inventory and new paths to your network map. For that reason, it makes sense to run both programs from one portfolio view. Our earlier article on CMS-0057-F API compliance covers that side of the work.

Frequently asked questions

Is the HIPAA Security Rule update final?

No. As of November 2026, the proposal has not been finalized. The federal regulatory agenda lists the final action for July 2027, but that date is a target, not a commitment.

Does the current Security Rule still apply?

Yes. All existing Security Rule requirements remain in force. OCR continues to enforce them, especially the requirement for an accurate and thorough risk analysis.

Should business associates prepare too?

Yes. The proposal would require business associates to verify their safeguards at least every 12 months. Covered entities would also need written verification from them. Starting early makes those reviews far easier.

How VTPMO can help

VTPMO helps healthcare and public sector organizations turn security requirements into delivered work. We support risk analysis, identity and access controls, DevSecOps practices, and portfolio governance for regulated programs. Our team has supported organizations such as Optum, Indiana FSSA, and Wellmark. Explore our healthcare industry services and DevSecOps services, or contact us to plan your readiness work.

Sources

Privacy Overview
VTPMO PROD

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Necessary

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

Analytics

This website uses Google Analytics to collect pseudonymous information such as the number of visitors to the site, and the most popular pages.

Keeping this cookie enabled helps us to improve our website.

Marketing

We use the LinkedIn Insight Tag to measure the results of our LinkedIn advertising and to see which industries and companies visit our site. LinkedIn cookies are set only if you allow Marketing cookies.