Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
HIPAA is the United States law governing protected health information, enforced through the Privacy, Security, and Breach Notification Rules and binding on covered entities and their business associates.

What Is HIPAA?
HIPAA is the Health Insurance Portability and Accountability Act of 1996, the United States federal law that governs how health information is protected. UK readers meet it most often in one of two ways: a British health technology company selling into the American market, or a UK organisation processing data on behalf of a US healthcare client.
The law’s security requirements were added by later rulemaking rather than the 1996 Act itself. The Privacy Rule took effect in 2003, the Security Rule in 2005, and the Breach Notification Rule arrived through the HITECH Act of 2009. The Omnibus Rule of 2013 extended direct liability to business associates, which is the change that matters most to suppliers.
Two categories:
A business associate agreement is mandatory between the parties, and since 2013 business associates face direct enforcement rather than only contractual exposure.
The Privacy Rule governs use and disclosure of protected health information, which covers 18 identifiers including names, geographic subdivisions smaller than a state, dates, contact details, identifiers of every kind, and full-face photographs. It permits disclosure for treatment, payment, and healthcare operations, requires authorisation for most other purposes, and imposes a minimum necessary standard. It also grants individuals rights of access, amendment, and accounting of disclosures.
The Security Rule applies to electronic protected health information and is organised into administrative, physical, and technical safeguards. Its distinctive feature is the split between required specifications and addressable ones. Addressable does not mean optional: an organisation must implement the specification, or document why it is not reasonable and appropriate and implement an equivalent alternative. Encryption at rest is addressable, which is a frequent source of confusion and a frequent enforcement finding.
The Breach Notification Rule requires notification to affected individuals without unreasonable delay and within 60 days. Breaches affecting 500 or more individuals must also be reported to the Department of Health and Human Services within 60 days and to prominent media in the affected area; smaller breaches are reported annually. A risk assessment may show low probability of compromise, which avoids notification, but the presumption is that an impermissible use or disclosure is a breach.
A Security Rule update was proposed in January 2025 that would remove the addressable category and make encryption and multi-factor authentication mandatory. Suppliers should track its progress rather than assume current flexibility persists.
The Office for Civil Rights enforces HIPAA, with penalty tiers based on culpability, running from unknowing violations to wilful neglect that is not corrected, and annual caps that are adjusted for inflation. State attorneys general may also bring actions. Enforcement patterns are instructive: a large proportion of settlements concern failures to conduct an accurate and thorough risk analysis, which is the Security Rule’s foundational requirement, and failures to encrypt portable devices.
UK organisations sometimes assume compliance with one implies the other. It does not.
| Point | HIPAA | UK GDPR |
|---|---|---|
| Scope | Health information held by covered entities and business associates | All personal data; health data is special category under Article 9 |
| Lawful basis | Permitted uses, with authorisation for others | Article 6 basis plus an Article 9 condition |
| Breach notification | Up to 60 days to individuals and HHS | 72 hours to the ICO where risk is likely; individuals without undue delay where high risk |
| Regulator | Office for Civil Rights | Information Commissioner’s Office |
A UK company handling NHS data works to UK GDPR, the Data Protection Act 2018, the common law duty of confidentiality, and the Data Security and Protection Toolkit rather than to HIPAA. Handling US patient data on top of that means meeting both regimes, and the 72-hour ICO clock is considerably tighter than the HIPAA deadline.
There is no HIPAA certification. Vendors advertising one are selling an attestation from a private company, not a government mark. What regulators expect to see is a documented and current risk analysis, a risk management plan, policies that match actual practice, workforce training records, business associate agreements with every relevant supplier, audit logging, access controls, and an incident process capable of meeting the notification timelines.
Most organisations pair this with ISO 27001 or a SOC 2 report for commercial assurance, because those give buyers something to review. Our regulation and compliance services help UK health technology companies build and evidence that control set.
It applies to any organisation acting as a business associate of a US covered entity, regardless of location. A UK software or hosting company processing protected health information for an American healthcare provider or insurer is directly bound, through a business associate agreement and through the law itself since the 2013 Omnibus Rule extended direct liability.
No official one. The US Department of Health and Human Services does not certify compliance, and any certificate on offer comes from a private assessor. What matters in enforcement is evidence: a current risk analysis, a risk management plan, policies matching practice, training records, business associate agreements, and an incident process that can meet the notification deadlines.
Required implementation specifications must be implemented as written. Addressable ones must be implemented if reasonable and appropriate; if not, the organisation must document why and implement an equivalent alternative measure. Addressable never means optional, and failing to document the reasoning is itself a finding. A proposed 2025 Security Rule update would remove the distinction entirely.
No. They overlap on security principles but differ on scope, permitted uses, patient rights, documentation, and notification timelines. HIPAA allows up to 60 days to notify individuals, while UK GDPR requires ICO notification within 72 hours where a risk is likely. An organisation handling both US and UK health data must satisfy each regime separately.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.