Healthcare organizations hold some of the most sensitive personal data there is, and, in the United States, it’s all governed by one data protection regime: HIPAA. Any organization that touches patient information—from hospitals and clinics to the IT providers and software vendors that serve them—must abide by HIPAA’s rules—with fines reaching millions of dollars for infringement.
With the risk of ransomware continuing to rise—and healthcare data proving particularly valuable to cyber attackers—adhering to HIPAA rules is more important than ever.
This blog explains what HIPAA is, who must comply with it, what its core rules require, and why keeping patient data recoverable has become central to meeting those obligations.
What is HIPAA?
HIPAA stands for the Health Insurance Portability and Accountability Act of 1996—the US federal law that sets national standards for protecting health information. It is administered by the Department of Health and Human Services (HHS) and enforced by its Office for Civil Rights (OCR).
The information HIPAA protects is called protected health information, or PHI: any individually identifiable health information, in any form. When that information is created, stored, or transmitted electronically, it becomes electronic protected health information (ePHI), and it falls under an additional set of technical safeguards.
HIPAA works through a set of rules, three of which set out most of the expectations:
-
The Privacy Rule governs how PHI can be used and shared.
-
The Security Rule sets the standards for protecting ePHI.
-
The Breach Notification Rule dictates what organizations must do when that data is exposed.
Why does HIPAA matter now?
HIPAA has been in force for decades, but the pressure on it has never been greater. Healthcare has become one of the most heavily targeted sectors for ransomware: in Sophos's 2024 survey, two-thirds of healthcare organizations reported being hit in the previous year (Sophos, The State of Ransomware in Healthcare 2024).
Attacks on healthcare don't only expose data—they disrupt care. When systems are encrypted, appointments are cancelled, records become inaccessible, and treatment can be delayed. The 2024 Change Healthcare breach left pharmacies across the US unable to process prescriptions for weeks.
This combination—highly sensitive data, a heavily regulated environment, and an escalating threat—is why HIPAA remains under close scrutiny, and why OCR continues to test compliance through audits and investigations rather than treating it as a paper exercise.
Who must comply with HIPAA?
HIPAA's obligations fall on two groups. The first is covered entities: these are organizations at the front line of healthcare, including providers who transmit health information electronically, health plans, and healthcare clearinghouses. The second is business associates: these are vendors and partners that handle PHI on a covered entity's behalf, including cloud providers, IT and managed service providers—as well as any subcontractors that handle PHI on their behalf.
The distinction matters because business associates are directly liable to OCR, not only to the organizations that hire them—so even a small vendor that handles ePHI carries real responsibilities under HIPAA’s rules.
What does HIPAA require?
At its core, HIPAA asks organizations to protect the confidentiality, integrity, and availability of the health information they hold.
The Privacy Rule sets the boundaries for how PHI can be used and disclosed. The Security Rule translates that into concrete protection for ePHI, grouped into three kinds of safeguard: administrative safeguards, which cover the policies, training, and access decisions that govern who can reach data; physical safeguards, which control the facilities and devices that store it; and technical safeguards, which are the controls inside systems, such as access controls, audit logging, and encryption. The Breach Notification Rule then sets out what must happen when data is exposed, including notifying affected individuals and HHS—and, for larger breaches, the media.
None of this is a one-time exercise. HIPAA compliance is an ongoing, risk-based process, anchored by a documented risk analysis that an organization is expected to keep current as its systems and threats change.
For a full breakdown of what each rule requires and how the safeguards work in practice, read our HIPAA White Paper.
Why recoverability is central to HIPAA compliance
Two of HIPAA's core duties, integrity and availability, depend directly on backup and recovery. If patient data can be altered, destroyed, or made inaccessible, these duties are not being met. This is why the Security Rule expects organizations to maintain a contingency plan built on reliable data backup and recovery.
This is particularly important in the context of the growing threat of ransomware. Secure, recoverable backups are central to the immediate task of restoring patient services without paying a ransom: they cannot prevent the theft of ePHI or the duty to report a breach of confidentiality, but they limit further breaches of availability and integrity.
While HIPAA doesn’t prescribe specific technologies, the Security Rule places emphasis on the ability to preserve backup data in a form that is tamper-proof, verifiable, and isolated from other systems that attackers will try to compromise. Maintaining absolutely immutable backups serves this purpose by ensuring that even the most privileged admin or attacker with access to backup storage cannot modify or delete data.
Conclusion
HIPAA may seem daunting from the outside, but its expectations are straightforward: keep patient data private, intact, and available—and prove how you’re doing it.
To find out more—from what each rule requires, to how OCR enforces them, and how resilient backup and recovery supports HIPAA compliance—read our full HIPAA White Paper.
