Rule Update
OCR Director: The Cost of Doing Nothing Is Very High
TL;DR
OCR Acting Director Paula Stannard told HIMSS 2026 attendees that the proposed HIPAA Security Rule update is necessary because cyberattacks on healthcare organizations directly harm patients — delaying care, diverting ambulances, and exposing sensitive data. She rejected industry arguments that the proposed rule is too burdensome, arguing that the cost of maintaining weak security controls far exceeds the cost of compliance.
OCR Acting Director Paula Stannard used her HIMSS 2026 address to defend the proposed HIPAA Security Rule update, warning that weak cybersecurity controls have enabled a wave of ransomware attacks that harm patients and that inaction is not a cost-free option.
OCR Acting Director Paula Stannard took the stage at HIMSS 2026 to deliver a pointed defense of the agency's proposed HIPAA Security Rule update — and to push back on industry critics who have argued the proposed requirements are too expensive and technically demanding for smaller healthcare organizations.
"The cost of doing nothing is very high," Stannard told the audience. "We have seen hospitals divert ambulances. We have seen surgeries canceled. We have seen patients harmed. That is the cost of the status quo."
Note
OCR's position: cyberattacks on healthcare organizations are a patient safety issue, not just a compliance matter. The proposed Security Rule update is OCR's response to more than a decade of rising breach counts and ransomware incidents.
Background: The Proposed Rule
HHS published a Notice of Proposed Rulemaking in January 2025 that would represent the first substantive update to the HIPAA Security Rule since 2013. The proposed rule attracted more than 4,000 public comments, many from hospital associations, small provider groups, and health IT vendors concerned about implementation costs.
The most contested provision is the elimination of the "addressable" specification category. Under current rules, certain safeguards are designated "addressable," meaning covered entities can choose not to implement them if they document a reasonable basis for that decision. The proposed rule would eliminate this distinction, making all implementation specifications required.
45 CFR §164.312(a)(2)(iv)Other significant proposals include mandatory multi-factor authentication for all access to electronic protected health information, annual penetration testing and vulnerability scanning, network segmentation requirements, and more prescriptive incident response plan requirements.
"Not a Paperwork Exercise"
Stannard was direct about OCR's intentions. She framed the proposed rule not as a paperwork exercise but as a direct response to documented patient harm.
"We are not asking for binders and checkboxes," she said. "We are asking you to actually implement the controls that prevent ransomware from shutting down your hospital."
She pointed to high-profile incidents — including ransomware attacks that forced hospital systems to divert emergency patients and cancel procedures — as evidence that the current rule's flexibility has been exploited.
OCR views the flexibility built into the 2013 Security Rule as a bug, not a feature. The proposed rule is designed to close the gap between organizations that use "addressable" specifications to avoid hard controls and organizations that implement them seriously.
Industry Response
Trade groups including the American Hospital Association and HIMSS itself have urged HHS to reconsider some of the more prescriptive provisions, particularly mandatory penetration testing timelines and MFA requirements for legacy clinical systems that were not designed with modern authentication in mind.
HIMSS submitted formal comments arguing that a phased implementation timeline of at least two years would be necessary for many members, and that small and rural providers would need additional technical assistance and safe harbors.
Stannard acknowledged the concerns but indicated that OCR is not inclined to weaken the core technical requirements.
"We hear you on implementation timelines," she said. "We are less sympathetic to the argument that you should not have to implement multi-factor authentication because it is hard."
What Covered Entities Should Do Now
The final rule has not yet been published. However, OCR has made clear that it views the proposed requirements as reflective of current best practices — meaning that enforcement actions under the existing rule may increasingly benchmark against the proposed standards even before they become final.
Note
Practical implication: do not wait for the final rule. Organizations that begin closing gaps now — particularly around MFA, vulnerability management, and incident response planning — will be better positioned for both compliance and any OCR investigation.
Key steps to take now:
- Audit your MFA coverage. Identify all systems that access ePHI and determine which do not currently support or enforce MFA.
- Review your risk analysis. The proposed rule requires documented risk analysis updates whenever the environment changes materially. Many organizations have not updated their risk analysis since before the COVID-era shift to remote access.
- Map your network segmentation. Determine whether ePHI systems are isolated from general corporate networks in a way that would limit the spread of ransomware.
- Test your incident response plan. The proposed rule requires tabletop and technical exercises, not just a documented plan on a shelf.
The direction of HIPAA enforcement is clear regardless of when the final rule publishes. OCR is moving toward mandatory, testable controls — and it is treating cyberattacks that harm patients as a top enforcement priority.
Sources & citations
- HHS OCR — HIPAA Security Rule NPRMOpen
- HIMSS 2026 Annual ConferenceOpen
- 45 CFR §164.306 — Security Standards: General RulesOpen
- 45 CFR §164.312 — Technical SafeguardsOpen
All content verified against official HHS guidance and the Code of Federal Regulations.
Frequently asked questions
What did OCR Director Stannard say at HIMSS 2026?▾
What is the proposed HIPAA Security Rule update?▾
Why is the HIPAA Security Rule being updated now?▾
What are the most significant proposed changes to the Security Rule?▾
When will the updated HIPAA Security Rule take effect?▾
Related intelligence
Rule Update
HIPAA Victims May Soon Receive a Share of OCR Fines: What the Proposed Compensation Program Means
7 min read
Rule Update
OCR Restructured: Three New Divisions and What It Means for HIPAA Enforcement
4 min read
Rule Update
HIPAA Security Rule Final Rule: May Deadline Passes With No Announcement
5 min read
Not legal advice. medcomply.ai provides compliance intelligence for educational and operational planning. Consult qualified counsel for legal interpretation.