24/7 local support: 480-550-8108Existing client? Just call, no ticket needed.
Industries

HIPAA security risk analysis: what small practices need to know

What the risk analysis is, who has to do one, and how often.

By the Inventive Tech teamReviewed by our CISSP-certified security lead4 min readNovember 2026

If you run a medical, dental or specialty practice, there's one HIPAA requirement worth putting at the top of your list: the security risk analysis.

It's required, it's the foundation for most of your other security decisions, and it's one of the things federal regulators look at first after a breach. Here's what small practices need to know.

What it is

The HIPAA Security Rule requires practices to 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."

In plain English: figure out where your electronic patient information lives, what could go wrong with it, how likely that is, how bad it would be, and what you're doing about it. Then write it down.

It isn't a training session, a policy binder or a checklist you sign once. It's an honest look at your actual systems.

Who has to do one

Every covered entity, which includes practices that bill insurance electronically, and every business associate that handles patient data on their behalf. There's no exemption for small practices.

The Security Rule is designed to be scalable, so a three-provider dental office isn't expected to do the same analysis as a hospital. But it does have to do one.

What it should cover

Where patient data lives. Most practices have more locations than they think:

  • Your EHR and practice management system
  • Imaging and diagnostic equipment
  • Email, including messages with attachments
  • Laptops, front desk computers and tablets
  • Phones, including personal phones that get work email
  • Scanners, copiers and fax systems
  • Backups and cloud storage
  • Third-party portals and billing services

Threats and weak spots. Ransomware, phishing emails aimed at the front desk, lost or stolen laptops, former staff who still have access, unpatched computers, weak passwords, power or internet outages.

What you already have in place. Logins, multi-factor authentication, encryption, backups, monitoring, training and physical security.

Likelihood and impact. For each risk, how likely is it, and how much harm would it cause? That gives you a risk level.

A plan. The analysis should lead straight into a risk management plan: what you'll fix, in what order, and who is responsible. The Security Rule requires that step too.

How often to do it

HHS doesn't set a fixed schedule. Its guidance treats risk analysis as an ongoing process, not a one-time project. In practice, that means:

  • Review it on a regular cycle. Many practices do this every year.
  • Update it when something significant changes, like a new EHR, a new location, a move to the cloud or new equipment.
  • Update it after a security incident.

A risk analysis from five years ago, before your current systems were in place, won't hold up well.

Common mistakes

  • Treating HIPAA training as the risk analysis. Training matters, but it's a different requirement.
  • Assuming the EHR vendor covers it. Your vendor is responsible for its own systems. Your practice is responsible for yours, including every computer that connects to the EHR.
  • Doing it once and filing it away. If the analysis never changes, it probably doesn't reflect reality.
  • Finding problems and not fixing them. Risks you identify need to be addressed in your risk management plan. An analysis that finds problems and leaves them sitting can be cited in an investigation, too.
  • Forgetting the less obvious devices. Imaging equipment, personal phones and old computers in a back room all count.

Why regulators care so much

When the HHS Office for Civil Rights investigates a breach, whether the practice had an accurate, up-to-date risk analysis is one of the things it looks at closely. OCR has run a dedicated Risk Analysis Initiative and has announced a steady stream of settlements tied to missing or incomplete risk analyses.

HHS also proposed significant updates to the Security Rule in January 2025 that would make several requirements more specific, including keeping an inventory of the technology that touches patient data. As of this writing the final rule has not been published, and recent reporting points to 2027. Either way, a solid risk analysis today puts you in a better position for whatever comes next.

Where to start

HHS and the Office of the National Coordinator offer a free Security Risk Assessment Tool designed for small and medium practices. It's a reasonable starting point if you want to do it yourself.

Many practices prefer help with the technical side, especially finding every place patient data lives and checking which safeguards are actually working. We have a HIPAA Security Officer on our team, and we sign a business associate agreement before we touch patient data.

This article is general information, not legal advice. Your compliance officer or attorney can confirm how HIPAA applies to your practice.

Request a free IT assessment.

Here's exactly what happens when you request one:

  1. 1
    A 15-minute call about your business and how your IT works today.
  2. 2
    A review of your systems, security and backups, with your permission.
  3. 3
    A short, plain-English summary of your biggest risks, what an auditor or insurer would flag, and where you may be overspending.

Free, with no obligation. After you submit the form, we call you back the same business day to set up the first call.

Prefer to talk now? 480-550-8108

We only use your details to respond to your request. Privacy Policy

Call 480-550-8108Free assessment