HHS cybersecurity rule worries providers

- HHS is still weighing a January 6, 2025 HIPAA Security Rule rewrite, while hospitals, insurers, and physician groups press the Trump administration to pull it. - The fight centers on cost and rigidity — HHS estimated about $9 billion in first-year compliance costs and $6.8 billion annually after that. - The backdrop is relentless healthcare hacking, but providers say prescriptive checklists could drain money from care and from smarter, risk-based defenses.

Hospitals are fighting a cybersecurity rule that, on paper, sounds hard to oppose. The rule would make healthcare organizations lock down patient data more aggressively. But the argument is not really about whether cyber defenses matter. It is about who pays, how fast, and whether Washington is writing a security playbook that is too rigid for a messy real-world health system. ### What is HHS actually trying to do? HHS, through its Office for Civil Rights, proposed a major rewrite of the HIPAA Security Rule on December 27, 2024, and published it in the Federal Register on January 6, 2025. This is the rule that governs how health plans, providers, clearinghouses, and their vendors protect electronic patient information. The proposal is meant to modernize a framework that has not had a big update since 2013, even as ransomware and supply-chain attacks have become routine. (federalregister.gov) ### What would change in practice? Basically, HHS wants fewer vague “do what’s reasonable” obligations and more specific must-dos. The proposal would require written documentation for policies and analyses, a current technology asset inventory, a network map showing how protected health data moves, and tighter timelines for compliance tasks. It would also remove much of the old distinction between “required” and “addressable” safeguards, which providers liked because it gave them flexibility. (hhs.gov) ### Why are providers so upset? Because they think the rule confuses paperwork with security. Hospital groups and physician organizations argue that many of the proposed requirements are too prescriptive, too expensive, and not realistic for complex care environments that run on old software, thousands of connected devices, and huge webs of outside vendors. The Federation of American Hospitals told HHS the proposal was not operationally feasible and drastically underestimated implementation costs. (hhs.gov) The American Academy of Family Physicians made a similar point for smaller practices. ### How big is the cost fight? It is huge. One hospital association comment letter pointed to HHS’s own estimate of roughly $9 billion in first-year compliance costs and $6.8 billion in annual costs after that — and then argued even those numbers are probably too low. The same letter warned that the burden would hit everyone from giant health systems to rural hospitals and independent physician offices. That is why this has turned into more than a privacy-law debate — it is now a spending and access-to-care fight. (news.bloomberglaw.com) ### Why now? The Change Healthcare attack changed the mood. That breach showed how one weak point in the healthcare supply chain can freeze claims, payments, and care operations across the country. HHS framed the proposed rewrite as part of a broader push to harden critical infrastructure after rising attacks and recurring compliance failures it says it keeps seeing in investigations. (calhospital.org) ### Where does the rule stand now? The formal comment period ended on March 7, 2025. OCR said it received roughly 4,745 comments, and as of mid-2025 there had been no further rulemaking action. Then the politics shifted. Under the Trump administration, health industry groups used HHS’s deregulation push to ask for the proposal to be withdrawn or heavily rewritten, and they may have a more sympathetic audience now than they did when the rule was drafted. (federalregister.gov) ### What does this mean for health-tech and AI vendors? Turns out this matters beyond hospitals. If buyers are being pushed to document data flows, map networks, verify vendor controls, and defend every security choice, flashy AI features get less room to coast. Procurement teams will care more about where data goes, who can touch it, what gets logged, and whether a vendor can survive an audit. Inference here, but a fair one — stricter HIPAA security expectations would reward products that are boring in the best way: traceable, controllable, and easy to prove safe. (federalregister.gov) ### Bottom line Healthcare providers are not arguing against cybersecurity. They are arguing against a version of cybersecurity they see as expensive, inflexible, and built by regulators who underestimate how tangled healthcare systems really are. HHS now has to decide whether tougher rules will make the sector safer — or just more burdened. (federalregister.gov) (hhs.gov)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.