Compliance · 5 min read

The HIPAA security risk assessment, explained for small practices

It's one of the first things an auditor asks for, and in HHS's own audits most organizations fell short on it. (source: Federal Register) Here is what it is, what goes in it, and how often it needs redoing.

If you remember one HIPAA requirement, make it this one. The Security Rule tells every practice to carry out an "accurate and thorough" assessment of the risks to the electronic patient information it holds. (source: 45 CFR 164.308) Almost everything else in the rule builds on it, because you can't sensibly protect information until you've written down where it is and what could happen to it. (source: 45 CFR 164.306)

It's also where practices most often come up short. Not because the work is hard, but because nobody was ever told it was theirs to do.

What it actually is

A security risk assessment is a written review, not a product and not a scan. It answers a short list of questions about your own practice, in your own words, and it's dated. Software can help you organize it. Software can't do it for you, because half the answers live in how your office really works.

What goes in it

A useful assessment has five parts. (source: NIST) First, an inventory: every place patient information lives or passes through, including the practice-management system, imaging, email, laptops, phones, backups, and the vendors who touch any of it.

Second, what could go wrong in each of those places. A stolen laptop, a phishing email, a failed backup, a former employee whose login still works. Third, what you already have in place to prevent each one.

Fourth, a judgment: how likely is each problem, and how bad would it be? This is the step that turns a list into priorities. Fifth, and most often missing, a plan. For each meaningful risk, what will be done, by whom, and by when.

How often it needs doing

The rule doesn't name a schedule. It expects the assessment to be kept current and revisited when your environment changes. (source: 45 CFR 164.316) A yearly review, plus another after anything significant, is a sensible habit (source: NIST): new practice software, a move, a new location, a new kind of device, or a security incident.

An assessment from several years ago, never touched since, tells a reviewer that security stopped being managed the day it was filed.

Who can do it

You can do it yourself. The Department of Health and Human Services publishes a free Security Risk Assessment Tool aimed at small and medium practices, and it's a reasonable place to start. (source: HHS ONC) The honest difficulty is the technical half. Knowing whether every laptop is encrypted, or whether two-step login covers every account, takes someone who can check rather than assume.

That's why many practices do it with their IT provider. The provider supplies the facts about the systems. The practice supplies how the office runs and makes the decisions. Neither can finish it alone.

Common mistakes

The first is treating it as an equipment list. An inventory is one-fifth of the job. The second is letting a vendor fill it in without anyone at the practice reading it, which produces a document no one can speak to when asked. The third is filing it and never opening it again.

The last is throwing old versions away. HIPAA requires this documentation to be kept for six years from when it was created or last in effect, whichever is later, and earlier versions show the work has been continuous. (source: 45 CFR 164.316)


The takeaway

The risk assessment isn't paperwork for its own sake. It's the one document that shows someone looked at your whole practice, decided what mattered, and did something about it. If yours is missing or out of date, it's the most valuable compliance task you can start this month.

Free assessment

When was your last risk assessment?

Healthcare-only IT for the Colorado Front Range. A free, no-pressure assessment tells you exactly where your practice stands.