HIPAA security for small practices
How to do a HIPAA risk analysis for a small practice
A HIPAA risk analysis is a written assessment of what could go wrong with the patient information on your practice's computers, how likely each problem is, and how bad it would be. For a small practice it means listing every place electronic patient data lives, pairing each threat with the weakness it would exploit, rating likelihood and impact, and turning the results into a plan with owners and dates. HHS publishes a free tool that walks a small office through it. The rule doesn't set a schedule, but HHS expects the analysis to stay current, and OCR has made it the focus of an enforcement initiative.
What the rule requires
The requirement is one sentence in the HIPAA Security Rule, at 45 CFR 164.308(a)(1)(ii)(A), and it is marked Required:
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.
The next line of the rule, 164.308(a)(1)(ii)(B), is also required: put security measures in place that reduce those risks "to a reasonable and appropriate level." The analysis finds the problems and the risk management plan fixes them. Neither is optional, and both have to be written down and kept for six years (164.316(b)).
The risk analysis is the first step of the rule as a whole. Every "addressable" decision, such as whether to encrypt laptops, rests on it. The full guide to the HIPAA Security Rule for small practices covers the other safeguards it feeds into.
What HHS says a risk analysis must include
HHS's Guidance on Risk Analysis says the Security Rule doesn't prescribe a method. It then lists the elements a risk analysis must incorporate "regardless of the method employed." Reading the guidance (last reviewed by HHS on August 12, 2026), we counted nine:
- Scope. All ePHI the practice creates, receives, maintains or transmits, on every kind of electronic media, from a single workstation to a network.
- Data collection. Where ePHI is stored, received, maintained or transmitted, documented.
- Threats and vulnerabilities. The reasonably anticipated threats, and the weaknesses a threat could exploit, documented.
- Current security measures. What you have in place, and whether it is configured and used properly.
- Likelihood. How likely each threat is to occur.
- Impact. How bad it would be if it did.
- Level of risk. A risk level for every threat and vulnerability pair, with corrective actions.
- Documentation. Written, in any format.
- Periodic review. An ongoing process, updated as things change.
The HHS Security Risk Assessment Tool
The Office of the National Coordinator for Health IT (ONC) and OCR publish the free Security Risk Assessment (SRA) Tool. It is built for small and medium practices and comes as a Windows application or an Excel workbook with the same content. HealthIT.gov says everything you enter stays on your own computer and HHS does not collect it.
We downloaded the version 3.7 Excel workbook from HealthIT.gov on October 14, 2026 and counted what it asks. It has seven sections, 127 multiple-choice questions and 40 vulnerabilities to rate:
| Section | Questions | Vulnerabilities |
|---|---|---|
| 1. SRA basics | 11 | 5 |
| 2. Security policies | 8 | 4 |
| 3. Security and workforce | 20 | 4 |
| 4. Security and data | 30 | 10 |
| 5. Security and the practice | 23 | 7 |
| 6. Security and business associates | 15 | 4 |
| 7. Contingency planning | 20 | 6 |
| Total | 127 | 40 |
Section 4, on technical safeguards such as access, encryption and activity logs, is the longest. Not every practice sees all 127 questions. The SRA Tool user guide, downloadable from the same page, says the sections use branching logic that skips questions based on earlier answers.
After each section, you tick the vulnerabilities that apply and rate each linked threat Low, Moderate or High for likelihood and for impact. The workbook's scoring table turns the pair into a risk level, and it weighs impact more heavily than likelihood. A threat rated low likelihood but high impact scores High. One rated high likelihood but low impact scores Moderate. Moderate or high likelihood with high impact scores Critical.
The tool has limits, and its own user guide spells them out. It says that using the tool doesn't mean your practice is compliant, and that a risk you know about but the tool didn't ask about still has to be identified, assessed and documented, either inside the tool or in a separate document. Treat the questions as a floor.
How to do a risk analysis in a small office
You can use the SRA Tool, a spreadsheet or a written document. These steps follow HHS's elements in order.
1. List everywhere ePHI lives
Walk the office. Write down every front desk PC, operatory or exam room computer, the doctor's computer, the server, imaging PCs, laptops, tablets and phones that open patient data. Add the practice management or EHR software, email, any fax service that delivers to email, cloud storage, backups and USB drives. Then add the vendors: billing company, clearinghouse, imaging vendor, IT support. For each, note how patient data comes in, where it moves and how it leaves. OCR lists that exact step, finding where ePHI enters, flows through and leaves, first among its recommendations in its settlement announcements.
2. Pair threats with vulnerabilities
HHS groups threats as natural (floods, tornadoes), human (attacks, malware, unauthorized access, accidental deletion) and environmental (power failures, water leaks). A risk exists where a threat meets a weakness. Write them as pairs:
- a phishing email meets an email account with only a password
- a stolen laptop meets an unencrypted drive
- ransomware meets backups the infected server can delete
- a former employee meets an account nobody turned off
- an imaging PC on an old version of Windows meets the internet
3. Record what's already in place
For each pair, write down the control you have and whether it works. "We have backups" isn't enough; note when a restore was last tested. "Screens lock" should say after how many minutes, on which computers.
4. Rate likelihood and impact
Use a simple scale. The SRA Tool's user guide defines likelihood as Low (a modest or insignificant chance), Moderate (a significant chance) or High (a probable chance), and impact as Low (a modest disruption with minor impact), Moderate (a significant disruption with some damage) or High (a catastrophic disruption with consequential damage). Be honest. A ransomware attack that takes the schedule down for a week is a high impact for any practice.
5. Assign a risk level
Combine the two ratings into one level for every pair. HHS's guidance gives averaging likelihood and impact as one example; the SRA Tool uses its own table. Either is acceptable if you apply it the same way every time and write it down.
6. Write the risk management plan
For every risk above Low, write the action, who does it and the due date. Turn on multi-factor authentication for email. Encrypt the laptops. Move backups somewhere the server can't delete them; the guide to protecting backups from ransomware covers what that takes. Set a same-day process for departures using the employee offboarding checklist. If you decide to accept a risk, write down why. Date it, have the security official sign it, and keep it for six years.
How often to redo it
The Security Rule doesn't set a frequency. HHS's guidance says the process "should be ongoing," and that some covered entities repeat it annually or as needed, giving bi-annual or every three years as examples. It also names events that call for a fresh look: a security incident, a change in ownership, turnover in key staff or management, and new technology.
The SRA Tool asks the same question. Of the answers it offers to "How often do you review and update your SRA?", the one it marks as the most effective is periodically and in response to environmental or operational changes or security incidents. For a small practice, that means a full review once a year, plus an update when you change practice software, add a location, replace the server, lose a key employee or have an incident.
What OCR has found missing
OCR runs a Risk Analysis Initiative that focuses investigations on this one requirement. By June 18, 2026 it had announced its 14th enforcement action under the initiative.
Small practices are among them. In April 2025, OCR settled with a small New York neurology practice whose network and all of its ePHI had been encrypted by ransomware, affecting about 6,800 people. OCR found it had failed to conduct an accurate and thorough risk analysis. The practice paid $25,000 and agreed to two years of OCR monitoring, with a corrective action plan that starts with doing the risk analysis and writing the risk management plan it lacked.
Size doesn't change the finding. OCR's July 2026 settlement with OSF Healthcare System, a health system in Illinois and Michigan, also began with ransomware, and its list of potential violations starts with the same failure to conduct an accurate and thorough risk analysis.
Keeping it current
A risk analysis goes stale the moment the office changes. A new laptop, a new hire, a different backup service or a move to cloud practice software each adds or removes a risk. Keep the inventory from step 1 as a living list, and note changes as they happen rather than reconstructing them in December.
Review the risk management plan monthly until every item is closed. A plan whose dates slipped months ago shows the risks were known and left open.
Crashcart, which runs IT for small offices, drafts a practice's risk analysis from its computers, practice software and setup answers, mapping where patient information is created, kept and sent, rating each risk and recording the action taken, and sends it for review every year. A practice that already has one pastes its text next to the risk analysis on its Documents page. The draft keeps what still applies, fills in the rest from the computers, updates anything out of date and flags questions only the practice can answer before it signs.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.