HIPAA Privacy Rule vs Security Rule, and the Breach Notification Rule
What each HIPAA rule protects, who must follow it, the three kinds of safeguards, "required" and "addressable", and what to do when PHI goes where it should not.
Who must follow the HIPAA rules?
- Covered entities: health plans, health care clearinghouses, and health care providers that send health information electronically in the standard transactions (claims, eligibility checks and the like).
- Business associates: people or companies that create, receive, keep or send PHI on a covered entity's behalf, such as a cloud host, a billing company or an EHR vendor with access to the data. Since the 2013 Omnibus Rule they are directly liable under the Security Rule and parts of the Privacy Rule, and a business associate agreement (BAA) must be signed before they get PHI.
HIPAA sets a floor across the United States: a state law that protects privacy more strictly still applies.
What does the Privacy Rule cover?
- All PHI, in any form: a paper chart, a conversation at the nurses' station, a fax, a screen.
- Uses and disclosures: PHI may be used for treatment, payment and health care operations without the patient's authorisation; most other uses, such as marketing, need a written authorisation. Some disclosures are permitted without authorisation, such as to public health authorities or where another law requires them; the rule itself requires disclosure only to the patient and to HHS.
- Minimum necessary: only the PHI needed for the purpose may be used or disclosed. The rule does not apply to disclosures for treatment, so a physician treating the patient can see the full record.
- Patient rights: to see and get a copy of their records (in general within 30 days, with one possible 30-day extension), to ask for corrections, to get an accounting of certain disclosures, to ask for restrictions and for confidential communication, and to receive the Notice of Privacy Practices.
- A privacy official must be named.
What does the Security Rule require?
It protects the confidentiality, integrity and availability of ePHI through three kinds of safeguards:
- Administrative: a security risk analysis and risk management, a named security official, workforce training and sanctions, access management, a contingency plan (backups, disaster recovery, emergency mode operation), and business associate agreements.
- Physical: facility access controls, workstation use and security, and device and media controls, such as how a hard disk is wiped before disposal.
- Technical: access control (a unique user ID for everyone, emergency access, automatic log-off, encryption), audit controls, integrity controls, person or entity authentication, and transmission security.
The rule is flexible: it names what must be achieved, not which product to buy, so a small clinic and a large health system can meet it in different ways. The risk analysis is the starting point: every later choice should follow from the risks it found.
Does "addressable" mean optional?
No. Each standard in the Security Rule has implementation specifications that are either required or addressable. For an addressable one, the organisation must assess whether it is reasonable and appropriate for its environment; if it is, implement it; if not, document why and put an equivalent alternative in place where that is reasonable. Encryption is the best-known addressable specification: an organisation that does not encrypt laptops must be able to show why, and what protects them instead.
In January 2025 HHS proposed changes to the Security Rule, among them making almost every specification required. Until a final rule takes effect, the required/addressable distinction above is the one that applies; check whether a final rule has since been published.
Privacy Rule and Security Rule side by side
| Privacy Rule | Security Rule | |
|---|---|---|
| What it protects | PHI in every form: paper, spoken, electronic | Electronic PHI (ePHI) only |
| Its main question | Who may use or disclose PHI, for what, and what rights the patient has | How ePHI is kept confidential, accurate and available |
| How | Permitted uses, authorisations, minimum necessary, patient rights | Administrative, physical and technical safeguards, from a risk analysis |
| Named person | Privacy official | Security official |
| In force since | 2003 | 2005 |
What does the Breach Notification Rule require?
A breach is the acquisition, access, use or disclosure of PHI in a way the Privacy Rule does not permit, which compromises its security or privacy. It covers a lost laptop and an email to the wrong person as much as an attack. The rule applies to unsecured PHI: PHI encrypted according to HHS guidance, with the key kept safe, or destroyed, is not unsecured.
- Presumed a breach: an impermissible use or disclosure is presumed to be a breach, unless a risk assessment shows a low probability that the PHI has been compromised. The assessment weighs at least four factors: the nature and extent of the PHI, the person who used it or received it, whether it was actually acquired or viewed, and how far the risk has been mitigated.
- Exceptions: unintentional access by a workforce member acting in good faith within their role, and an inadvertent disclosure between people authorised at the same organisation (or its business associate), in both cases if the PHI is not further used or disclosed; and a disclosure where the recipient could not reasonably have kept the information.
- Individuals: notified without unreasonable delay and no later than 60 calendar days after the breach is discovered.
- The media: also, when the breach involves more than 500 residents of a state or jurisdiction.
- HHS: at the same time as the individuals when 500 or more people are affected; for fewer than 500, in a yearly log sent within 60 days after the end of the calendar year.
- Business associates notify the covered entity, no later than 60 days after discovery.
What do candidates get wrong?
- "The Security Rule covers paper records." It covers ePHI only; paper is under the Privacy Rule.
- "Addressable means optional." It means assess, then implement, or document why not and use an equivalent alternative.
- Applying minimum necessary to treatment. Disclosures for treatment are not limited by it.
- Waiting the full 60 days. Sixty days is the outer limit; the duty is "without unreasonable delay".
- Mixing up the 500 thresholds. The media: more than 500 residents of one state or jurisdiction. HHS: 500 or more, at the same time as the individuals (within 60 days); fewer than 500, in the yearly log.
- Treating a misdirected email as "not a breach because it was an accident". It is presumed a breach unless the risk assessment shows a low probability of compromise or an exception applies.
- Choosing a policy where a control is needed. When a risk assessment finds an unacceptable risk, such as unencrypted laptops, lowering it (mitigation) means putting a control in place, such as encryption, not only writing a rule.
Summary for revision
- Privacy Rule: all PHI, any form; uses and disclosures, minimum necessary, patient rights.
- Security Rule: ePHI only; confidentiality, integrity, availability; administrative, physical, technical safeguards; starts with a risk analysis.
- Addressable is not optional: assess, implement or document an alternative.
- Breach: presumed unless a four-factor assessment shows low probability of compromise; individuals within 60 days at most.
- 500: media for more than 500 in one state; HHS with the individuals for 500 or more, yearly for fewer.
Sources
- HIPAA Administrative Simplification rules, 45 CFR Parts 160 and 164: Subpart C (Security Rule), Subpart D (Breach Notification Rule), Subpart E (Privacy Rule).
- HHS Office for Civil Rights: summaries of the HIPAA Privacy Rule and Security Rule, and its breach notification guidance.
- HHS, proposed rule to strengthen the HIPAA Security Rule (published January 2025).
Related free practice questions
- Lowering risk to an acceptable level: mitigation with controls
- The presumption of a breach, rebutted by a low probability of compromise
The site files this concept under the domain Healthcare Information and Systems Management.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.