Ask five people in healthcare what a "HIPAA risk assessment" is and you may get five answers: a questionnaire, a vulnerability scan, a gap analysis, a vendor review, or the formal analysis the Security Rule requires. The confusion matters, because organizations sometimes believe they have satisfied a legal requirement when they have actually done something narrower.
This guide sets out the regulatory language, the ways the terms are used in practice, and a simple test for whether the work you have done meets the requirement.
Key points
- "Risk analysis" is the term used in the Security Rule at §164.308(a)(1)(ii)(A).
- "Risk assessment" is frequently used as a synonym, but also describes other exercises such as breach risk assessments and vendor assessments.
- Risk management under §164.308(a)(1)(ii)(B) is the separate, required follow-through.
- What matters is the substance: an accurate and thorough assessment of risks to all ePHI.
What the regulation actually says
The Security Rule's security management process standard, §164.308(a)(1), contains two required implementation specifications that sit side by side:
- Risk analysis — §164.308(a)(1)(ii)(A): conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI held by the covered entity or business associate.
- Risk management — §164.308(a)(1)(ii)(B): implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level.
How "risk assessment" gets used
Outside the regulatory text, "risk assessment" is used in at least four ways. Knowing which one someone means avoids misunderstandings with vendors, auditors and boards.
As a synonym for the required risk analysis
This is the most common usage. HHS's own free tool is called the Security Risk Assessment (SRA) Tool, and many service providers market a HIPAA risk assessment that is intended to satisfy §164.308(a)(1)(ii)(A).
As a step within a broader risk framework
In NIST terminology, risk assessment is one component of a larger risk management process that also includes framing, responding to and monitoring risk. NIST SP 800-30 and SP 800-66 Rev. 2 use the term this way.
As the breach risk assessment
Under §164.402, an impermissible use or disclosure is presumed to be a breach unless a risk assessment of at least four factors demonstrates a low probability of compromise. This is incident-specific and completely different from the enterprise risk analysis.
For narrower or adjacent exercises
Vendor risk assessments, application security reviews, privacy impact assessments and gap analyses are all sometimes called risk assessments. They can be valuable, but none of them alone is the Security Rule risk analysis.
Side-by-side comparison
| Security Rule risk analysis | Risk assessment (common usage) | Risk management | |
|---|---|---|---|
| Legal basis | §164.308(a)(1)(ii)(A) — required | Varies; may be the same as risk analysis, or a different exercise | §164.308(a)(1)(ii)(B) — required |
| Question it answers | What could go wrong with our ePHI, how likely is it, and how bad would it be? | Depends on scope — enterprise, system, vendor or incident | What are we doing to reduce those risks, and is it working? |
| Scope | All ePHI the organization creates, receives, maintains or transmits | Can be narrow (one system or vendor) | Risks identified in the analysis |
| Typical output | Asset inventory, threat and vulnerability list, likelihood and impact ratings, risk levels | Findings report or score | Risk register or plan with owners, dates and status |
| Frequency | Ongoing; updated when the environment changes | Project-based | Continuous |
A simple test for your current document
Whatever your report is called, HHS's risk analysis guidance describes elements that should be present. Ask whether your document:
- Covers all ePHI, in every location and system, including mobile devices, backups and vendors.
- Identifies and documents where ePHI is stored, received, maintained or transmitted.
- Identifies reasonably anticipated threats and vulnerabilities.
- Assesses current security measures.
- Determines the likelihood of threat occurrence and the potential impact.
- Assigns a level of risk to each threat–vulnerability combination.
- Is documented and periodically reviewed and updated.
Where risk management fits
A risk analysis without risk management is a list of known problems. The Security Rule expects you to act on findings: select controls, assign owners, track remediation and accept residual risk deliberately. Practically, that means a living risk register reviewed by leadership. Our HIPAA risk management service focuses on exactly this step, which many organizations skip.
How a gap analysis differs
A HIPAA gap analysis compares your program against each requirement and asks "do we have this?" A risk analysis asks "what could happen to our ePHI?" The two complement each other: the gap analysis finds missing policies and controls; the risk analysis prioritizes them by real-world exposure. Doing only a gap analysis is a common reason organizations believe they have a risk analysis when they do not.
A worked example: one risk, three documents
Consider a small orthopedic practice whose front-desk staff share a single login to the practice management system. The same issue shows up differently depending on which exercise you are running.
In a gap analysis
The finding reads something like: "Unique user identification (§164.312(a)(2)(i), required) — not met. Shared account in use at front desk." It tells you a requirement is unmet, but not how serious the exposure is or what to fix first.
In the risk analysis
The same fact becomes a threat–vulnerability pair: a workforce member could view or alter records without accountability, and inappropriate access could not be attributed during an investigation. The analyst rates likelihood (high — the account is used daily by several people) and impact (moderate — misuse is limited to scheduling and demographics, but includes PHI), producing an overall risk level that can be compared against every other risk in the environment.
In the risk management plan
The entry now has an owner (the practice manager), a remediation (individual accounts with role-based permissions, plus a fast-switching login to keep the front desk moving), a target date, and a note on residual risk once complete. When leadership reviews the register, they can see that this item is closed — and evidence of that is exactly what a reviewer later asks for.
Choosing the right scope
If you are commissioning outside help, ask the provider to state explicitly whether the deliverable is intended to meet §164.308(a)(1)(ii)(A), what systems and locations are in scope, and what methodology they follow (for example, NIST SP 800-30 concepts as referenced in NIST SP 800-66 Rev. 2). A well-scoped HIPAA security risk assessment should produce a risk-rated register you can manage from, not just a narrative.
Frequently asked questions
Is a HIPAA risk assessment the same as a risk analysis?
Often, yes — the terms are frequently used interchangeably. But "risk assessment" is also used for narrower exercises. What matters is whether the work meets the substance of §164.308(a)(1)(ii)(A).
Does using the HHS SRA Tool satisfy the requirement?
The SRA Tool can help structure a risk analysis, especially for small providers. Using it does not by itself ensure compliance; you must scope it to all ePHI, answer accurately and follow through with risk management.
How often must the risk analysis be updated?
The rule does not fix an interval. It must be kept current, so update it when systems, vendors, locations or threats change. Many organizations also review it at least annually.
Is the breach risk assessment part of the risk analysis?
No. The breach risk assessment under §164.402 evaluates a specific incident to decide whether notification is required. The risk analysis evaluates risks across your whole environment.
Who should perform the risk analysis?
HIPAA allows it to be done internally or by an outside party. What matters is competence, objectivity and thoroughness. Outside help can add independence and capacity, but cannot guarantee compliance.
Authoritative sources
- HHS — Guidance on Risk Analysis
- NIST SP 800-66 Rev. 2
- HealthIT.gov — Security Risk Assessment Tool
- eCFR — 45 CFR Part 164
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.