HIPAA Risk Analysis Requirements Under §164.308(a)(1)

HIPAA Risk Analysis

The HIPAA Security Rule states the requirement in exact terms: “Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate.” That’s §164.308(a)(1)(ii)(A), and it’s Required, not Addressable.

Risk Analysis is one of four required specifications under the Security Management Process standard. The other three are Risk Management, Sanction Policy, and Information System Activity Review. All four sit at the top of the Administrative Safeguards, and Risk Analysis comes first because the other three depend on its output.

Everything else in the Security Rule assumes this happens before it. Encryption decisions, access control choices, training priorities, contingency planning: all of it should trace back to what the risk analysis actually found. Skip this step, and every safeguard decision downstream becomes a guess instead of a documented judgment, which is exactly the gap HHS’s Office for Civil Rights (OCR), the agency that enforces HIPAA, looks for first.

Who conducts the risk analysis

Nothing in the Security Rule requires an outside party. A covered entity or business associate can conduct its own risk analysis internally, often working from a structured tool like HHS’s own Security Risk Assessment (SRA) Tool, provided whoever does the work has the expertise to cover all nine elements below accurately.

Many organizations bring in outside help instead, and that help takes different forms. A managed IT or security provider typically has direct visibility into the technical environment already, which suits the data collection and technical vulnerability portions of the work. A dedicated privacy or compliance consulting firm typically brings deeper familiarity with how OCR evaluates these documents and how similar organizations have been cited in enforcement actions. An attorney specializing in healthcare regulatory compliance can address legal exposure alongside the technical findings. None of these is a required or default choice; the right fit depends on what the organization already has in place and what gaps it’s trying to close.

Whoever performs the work, the obligation stays with the covered entity or business associate. There’s no government body or independent organization that reviews and approves a risk analysis before it’s used. It’s a self-conducted, self-documented process, and the organization signs off on it regardless of who assembled it.

That doesn’t mean there’s no outside accountability. OCR periodically audits organizations directly, independent of any breach or complaint, and its ongoing Risk Analysis Initiative has produced enforcement actions specifically targeting weak or missing risk analyses. When OCR does review one, whether in a formal audit or an investigation after a breach, it applies its own Audit Protocol, a separate document from the guidance the nine elements below are drawn from, to judge whether the analysis holds up.

The closest thing to third-party certification in this space is HITRUST, a separate framework built partly on HIPAA that does involve an independent, certified assessor. HIPAA’s risk analysis requirement itself has no equivalent: it’s evaluated after the fact, not approved in advance.

The nine elements of a compliant risk analysis

OCR’s Guidance on Risk Analysis breaks the requirement into nine elements. None of them are optional. OCR evaluates a risk analysis against all nine, and an element that’s missing or undocumented gets cited as a deficiency.

1. Scope of the analysis

The analysis has to cover every form of ePHI the organization creates, receives, maintains, or transmits, regardless of medium: servers, workstations, portable devices, backups, and any third party that touches the data. Defining scope means answering concrete questions before anything else starts: which systems, which locations, which vendor relationships actually touch ePHI, and which don’t.

2. Data collection

Once scope is set, the next step is mapping where ePHI actually lives and moves: which systems store it, which applications process it, where it travels in transit. A data flow diagram or table is a common output, tracing ePHI from where it enters the organization to everywhere it ends up.

3. Identify and document threats and vulnerabilities

Threats and vulnerabilities aren’t the same thing. A vulnerability is a weakness: a missing patch, a misconfigured server, a flat network. A threat is what could exploit that weakness, whether that’s a phishing email, a natural disaster, or an employee mistake. Both technical findings, like unpatched systems or weak authentication, and non-technical ones, like untrained staff or uncontrolled physical access, belong in this step.

4. Assess current security measures

Before deciding what’s missing, the organization has to document what’s already in place and whether it’s actually functioning the way it’s supposed to. That covers technical controls like encryption and backup systems, and administrative and physical measures like whether a sanction policy has ever been enforced or whether visitors are actually required to sign in.

5. Determine the likelihood of threat occurrence

This step estimates how probable it is that a given threat exploits a given vulnerability, based on factors like how exposed a system is, whether similar vulnerabilities have been exploited elsewhere, and how attractive the organization’s data might be to an attacker. It’s a judgment call, not a fixed calculation, and it has to be one the organization can explain and defend.

6. Determine the potential impact of threat occurrence

Impact measures what happens if the threat succeeds: how many records are affected, what a specific outage or disclosure costs the organization financially and operationally, and what it does to patient care and trust. Some of this is measurable directly; some of it requires judgment about the organization’s own circumstances.

7. Determine the level of risk

Risk level combines the likelihood and impact ratings into a single score for each threat-vulnerability pair, typically using a matrix that turns two ratings into one. This step is where the analysis actually prioritizes: which risks need to be addressed first, which are acceptable as is.

8. Finalize documentation

The Security Rule doesn’t require a specific format, but it does require the analysis to be written down completely: the scope, the findings, the ratings, and the reasoning behind them. An incomplete or informal document, a stack of scan results with no analysis attached, doesn’t satisfy this element even if the underlying work was thorough.

9. Periodic review and updates

A risk analysis isn’t a one-time project. It has to be revisited when something changes: a new system, a new vulnerability, a change in ownership, turnover in key staff. What counts as a meaningful change and how often to check for one is addressed later on this page.

Three terms recur throughout this process, and OCR’s guidance sources all three to NIST Special Publication 800-30. A vulnerability is a flaw or weakness in security procedures, design, implementation, or internal controls that could be triggered accidentally or exploited intentionally. A threat is the potential for a person or thing to exercise that vulnerability. Risk is the combination of how likely a threat is to occur and what happens if it does.

Threats fall into three categories. Natural threats include floods, earthquakes, and severe weather. Human threats include both intentional acts, like a network intrusion, and unintentional ones, like an employee entering the wrong data. Environmental threats include power failures and equipment failure from heat, humidity, or chemical exposure.

What this looks like in practice

Take one example: an automated appointment reminder system that pulls patient names and appointment times from the EHR and sends text messages.

Scope and data collection establish the basics: the reminder service connects to the EHR through an API, pulls patient name, phone number, and appointment time, and sends that data to a third-party texting platform, which stores message logs for 90 days.

The threat and vulnerability review finds two issues: the texting platform doesn’t have a signed BAA on file, and the API connection uses an authentication key that hasn’t been rotated in over a year.

Assessing current measures shows the API connection is encrypted in transit, but nobody has verified how the vendor stores its message logs.

Likelihood is rated high: a stale credential is more exposed than a recently rotated one, and the missing BAA means there’s no contractual assurance about how the vendor handles the data at all.

Impact is also rated high: every text sent carries identifiable health information, and the volume scales with the practice’s appointment schedule, meaning the exposure repeats weekly rather than being a one-time risk.

Combined, the risk level lands high on both counts. The output isn’t a vague sense that texting reminders is “probably fine.” It’s a specific, documented finding: this vendor lacks a BAA, this credential needs rotating, and here’s the reasoning behind the rating.

MIS’S TAKE

The one we run into most often is backups. Ask a practice whether its data is backed up and the answer is always yes, because everyone assumes the IT company has it handled. Then someone finally tests it. The backup has been failing quietly for months, or it covers the old server but not the system the practice actually uses, and nobody has ever tried to restore a single file. Nothing looked wrong until the day it mattered. That’s the whole point of a risk analysis: it replaces “I’m pretty sure someone’s handling that” with someone actually checking, writing down what they found, and putting a name next to who fixes it.

Risk analysis vs. vulnerability scan

A vulnerability scan and a risk analysis get treated as interchangeable more often than they should. They’re not.

A vulnerability scan is a technical tool. It checks for missing patches, outdated software, open ports, and exposed services, and it produces a list of technical findings. It’s useful, and it’s often a genuine input into a risk analysis.

A risk analysis is broader by design. It has to account for people, processes, vendors, and business operations, not just what a scan can detect. A perfectly clean vulnerability scan says nothing about whether an employee is emailing patient records to a personal account, whether a vendor’s BAA covers what it needs to, or whether a terminated employee’s access was actually removed.

OCR treats the two as distinct. In enforcement action after enforcement action, organizations that could produce scan results but no broader analysis have been cited for failing to conduct an accurate and thorough risk analysis.

Documentation and retention

The Security Rule requires the risk analysis to be documented under §164.316(b)(1), but it doesn’t dictate a specific format. A spreadsheet, a report, or a structured tool output can all satisfy it, as long as the documentation actually reflects the nine elements above.

Retention runs six years from the date the documentation was created or the date it was last in effect, whichever is later, under §164.316(b)(2)(i). That applies to the risk analysis itself and to any updates made to it.

The finished analysis isn’t the end of the obligation. It’s the direct input to the separate risk management process, the step where identified risks actually get addressed.

When the first risk analysis is due

There’s no grace period for a new practice. The obligation begins the moment the organization starts creating, receiving, maintaining, or transmitting ePHI, which for most practices is essentially day one of seeing patients or handling their records electronically. A brand-new practice can’t wait until its first year is over to get around to it; the risk analysis is supposed to inform the safeguards a practice puts in place from the start, not follow behind them.

How often it should be conducted

The Security Rule doesn’t set a fixed frequency for updating a risk analysis today. OCR’s own guidance says explicitly that the rule doesn’t prescribe one, and that how often an organization needs to revisit it depends on its circumstances. Some organizations do it annually. OCR’s guidance gives examples of others doing it every two or three years.

What the rule does require right now is that the analysis stay current, and that means certain events should trigger an update regardless of schedule: a security incident, a change in ownership, turnover in key staff or management, or the introduction of new technology.

The pending 2025 NPRM would remove this flexibility. As proposed, it would require every covered entity and business associate to complete a documented risk analysis at least once every 12 months, turning what’s currently a judgment call into a fixed annual requirement. That provision isn’t in effect yet, and per HHS’s own Fall 2026 regulatory agenda, final action isn’t expected before July 2027 at the earliest. Until then, frequency stays tied to what’s actually changed in the organization, not a fixed interval.

Considerations for small organizations

OCR’s guidance doesn’t treat every organization’s risk analysis the same way. It notes directly that smaller organizations tend to have fewer variables, fewer systems, fewer workforce members, and more direct control over their environment than larger ones, and that the appropriate security measures for a small practice can reasonably differ from what a hospital system needs.

Two companion documents from CMS’s Security Series apply this directly. Implementation for the Small Provider addresses how a smaller organization can approach Security Rule compliance realistically. Basics of Risk Analysis and Risk Management walks through the same nine elements at a level built for an organization without a dedicated compliance function.

None of this lowers the bar on what the risk analysis has to cover. It changes what’s reasonable and appropriate for meeting it: a 20-person practice doesn’t need the same risk analysis infrastructure as a multi-site hospital system, but it does need one that’s accurate and thorough for its own environment.

MIS’S TAKE

The gap is rarely that a small practice did nothing. Usually there’s a checklist the EHR vendor handed them at go-live. Somebody checked the boxes and it went in a drawer. Since then the practice has added a texting service, a billing company, cloud email, and a few new laptops, and none of that is written down anywhere. What OCR expects is simpler than people fear, but it has to be real: show that you know where patient information lives today, in every system, with every vendor, on every laptop. Show that you thought through what could go wrong, and that you wrote down what you decided to do about it. A small practice doesn’t need a binder the size of a hospital’s. It needs one honest, current document that matches how the practice actually runs.

Resources

HHS’s Guidance on Risk Analysis is the primary source the nine elements above are drawn from, and it’s worth reading directly rather than relying on a summary.

OCR’s Audit Protocol is the separate document OCR uses when formally auditing an organization’s compliance, distinct from the guidance above.

The HHS/ONC Security Risk Assessment (SRA) Tool is a free application built specifically to help small and medium-sized practices and business associates work through this requirement.

CMS’s Implementation for the Small Provider and Basics of Risk Analysis and Risk Management are the two companion papers referenced above.

NIST SP 800-30 is the publication OCR’s guidance sources its definitions and risk-assessment approach from; Revision 1 is the current edition.

Frequently asked questions

When does a new practice need its first HIPAA risk analysis?

There’s no grace period. The obligation starts the moment the organization begins creating, receiving, or transmitting ePHI, typically from day one of operations. It’s meant to inform the safeguards a practice puts in place from the start, not follow behind them.

What’s the difference between the nine risk analysis elements and OCR’s audit protocol?

The nine elements come from OCR’s Guidance on Risk Analysis and define what the analysis itself has to cover. The Audit Protocol is a separate document OCR uses when it formally audits an organization, to evaluate whether the resulting analysis and documentation hold up. Both apply; they answer different questions.

Is a vulnerability scan the same as a HIPAA risk analysis?

No. A vulnerability scan checks for technical weaknesses like missing patches or exposed ports. A risk analysis is broader, covering people, processes, and vendors in addition to technical findings. A vulnerability scan on its own doesn’t satisfy the requirement.

What happens if a risk analysis is missing or incomplete when OCR investigates?

A missing or inadequate risk analysis is treated as its own violation, separate from whatever incident triggered the investigation. It’s the most frequently cited Security Rule deficiency in OCR’s investigations and audits, and it can result in penalties even when no breach occurred.

Does a small practice need the same risk analysis as a hospital system?

Both need to cover all nine required elements, but OCR’s own guidance recognizes that appropriate security measures can differ by organization size. A small practice’s analysis should be accurate and thorough for its own environment, not modeled on enterprise-scale infrastructure it doesn’t have.

Lliam Holmes

Lliam Holmes

Chief Executive Officer

Lliam Holmes is the Chief Security Strategist, Co-Founder, and CEO of MIS Solutions, Inc., bringing more than 30 years of expertise in designing, implementing, and securing IT infrastructure.

Social Media:

Table of Contents

Schedule a free 15-minute discovery call
We’ll discuss your IT requirements and assess whether we’re the right fit for you.

Share:

Liked the articles?

Well, there’s plenty more where that came from! Our incredible team is constantly on the lookout for the latest and greatest IT content to keep you informed about what’s cooking in the world of technology. Make sure you don’t miss out on our amazing content by subscribing to receive blog updates.

  • Remark: We will collect your information for marketing purposes. However, we respect your privacy rights. If you wish to access or amend any Personal Data we hold about you, or request that we delete any information about you that we have collected, please send us an email: info@mis-solutions.com