How does a small clinic do a HIPAA security risk analysis?

The short answer
Under 45 CFR 164.308(a)(1)(ii)(A), a HIPAA covered clinic must make an accurate and thorough assessment of the risks to its electronic patient data. In a small clinic that means listing where the data lives, what could go wrong, how likely and how bad each risk is, and the fix. The free federal Security Risk Assessment Tool walks you through it.
A HIPAA security risk analysis is your written answer to three questions. Where does electronic patient data live in your clinic? What could go wrong with it? What are you doing about the worst of it? The HIPAA Security Rule requires one from each covered clinic, and a small practice can do it in-house with a free federal tool.
What does the HIPAA Security Rule require?
The rule lists risk analysis as a required step. A covered clinic must "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information" that it holds (45 CFR 164.308(a)(1)(ii)(A)) 1. Electronic protected health information, or ePHI, is the patient health information you create, receive, keep or send in electronic form.
The next required step is risk management. You put security measures in place that bring those risks down "to a reasonable and appropriate level" 1.
The rule scales to your clinic. When you choose safeguards, you weigh your size, complexity and capabilities, your technical setup, the cost of each measure, and how likely and how serious each risk is (45 CFR 164.306(b)) 2. A three-person clinic does the same analysis as a hospital, sized to three people.
You keep the analysis in writing, and electronic records count. You keep it for six years from the date you created it or the date it was last in effect, whichever is later, and you review it from time to time (45 CFR 164.316(b)) 3.
How does a small clinic do one?
NIST, the National Institute of Standards and Technology, published a guide to the Security Rule in February 2024: NIST SP 800-66 Rev. 2 4. Its risk assessment runs in seven steps 4. The examples in parentheses are ours.
- Prepare. Map where ePHI is created, received, stored and sent (the EHR, laptops, phones, the fax line, cloud services, outside vendors, anyone who works from home).
- Name the threats you can reasonably expect (a phishing email, ransomware, a lost phone, a former employee whose login still works).
- Find the weak points a threat could use (no multi-factor sign-in, shared passwords, an unpatched computer, a backup drive that stays plugged in).
- Judge how likely each threat is to exploit each weak point.
- Judge the impact if it does.
- Combine the two into a risk level.
- Write down the results, for example in a risk register: one line per threat and weak point, with its likelihood, impact, risk level and planned fix.
NIST says the steps need not run in that order and should fit your organization 4. It says small organizations "may find benefit in using the HHS Security Risk Assessment (SRA) Tool," and that its own guide "does not supplement, replace, modify, or supersede the Security Rule itself" 4.
A few lines from a made-up small-clinic register show the idea. Front desk email, phishing, no multi-factor sign-in: high likelihood, high impact, turn on multi-factor sign-in this week. Physician's phone, loss, no screen lock: medium likelihood, high impact, set a screen lock and remote wipe. Backups, ransomware, drive always connected: medium likelihood, high impact, keep one copy offline.
What is the free federal Security Risk Assessment Tool?
ONC, the Office of the National Coordinator for Health Information Technology, built the Security Risk Assessment Tool with the HHS Office for Civil Rights (OCR). Its target audience is small and medium providers 5. Version 3.7 runs on 64-bit Windows, and an Excel workbook carries the same content for clinics without Windows 5. What you enter stays on your computer. HHS does not collect it 5.
Treat the tool as the backbone of the analysis. Its page says using it "is neither required by nor guarantees compliance with federal, state or local laws," and version 3.7 reminds users that the survey alone may not find every risk 5. Add what its questions miss, such as the apps your staff use on their own phones.
How often should a clinic redo its risk analysis?
The current rule sets no fixed calendar. It asks for a periodic evaluation, plus a new one when changes in your environment or operations affect the security of ePHI 1. It also asks you to review your documentation from time to time and update it as needed 3. We would redo the analysis when you change EHR, add a vendor that touches patient data, move, start telehealth or have a security incident.
A change is pending. On January 6, 2025, HHS proposed a rewrite of the Security Rule (90 FR 898) 6. Among other changes, it would require a written risk analysis that you review, verify and update at least once every 12 months 6. HHS has not published a final rule (last checked 2026-10-26), so section 164.308 still reads as amended in 2013 1.
What happens if a clinic skips it?
HHS can impose civil money penalties for HIPAA violations in four tiers. The tier depends on what the clinic knew and whether it fixed a willful-neglect violation within 30 days (45 CFR 160.404) 7. HHS adjusts the amounts for inflation each year in 45 CFR 102.3. In that table's 2025 column, the lowest tier starts at $145 per violation, and identical violations in one calendar year are capped at $2,190,294 8.
Good practice counts in your favor. A 2021 amendment to the HITECH Act requires HHS to consider whether a clinic had recognized security practices in place for at least the previous 12 months when it decides fines, audits and settlement terms (42 U.S.C. 17941) 9. Recognized practices include the standards and guidance NIST develops under its cybersecurity mandate 9. The same section bars HHS from raising a fine because a clinic lacked them 9.
What is ZunovaMD building that bears on this?
ZunovaMD is in pilot. We are designing the platform so a clinic that runs on it has fewer moving parts to analyze: one system in place of several, single sign-on with multi-factor sign-in for staff, an append-only audit log, and a named list of each vendor that can touch patient data. We do not train models on patient data, de-identified data included. Our security page lists each control with its status, and the subprocessors by name. Your clinic still owns its risk analysis. We will answer the vendor questions in it, and a business associate agreement is available.
Two related guides: texting patients under HIPAA and the TCPA and records requests and lab results.
Questions
Does a cash-only DPC clinic need a HIPAA risk analysis?
It depends on whether HIPAA covers the clinic. Under 45 CFR 160.103, a health care provider is a covered entity when it sends health information electronically in connection with a standard transaction, such as a claim or an eligibility check. A clinic that never does may fall outside that definition. One electronic claim changes the answer, so ask counsel before you rely on it.
Can the SRA Tool be our whole risk analysis?
It can be the backbone. ONC's page says the tool is not required and does not guarantee compliance, and version 3.7 reminds users that the survey alone may not find every risk. Add anything its questions miss, then keep the report with your risk management plan.
How long do we keep the risk analysis?
Six years from the date it was created or the date it was last in effect, whichever is later, under 45 CFR 164.316(b)(2)(i). Keep each version so you can show the work over time.
Does our EHR vendor's security cover our risk analysis?
No. The Security Rule asks each covered entity and each business associate to assess the risks to the electronic patient data it holds. Your vendor's controls are one input to your analysis, next to your own devices, staff and other vendors.
Sources
- 45 CFR 164.308: Administrative safeguards (Cornell LII, e-CFR text), checked 2026-10-26
- 45 CFR 164.306: Security standards, general rules (Cornell LII, e-CFR text), checked 2026-10-26
- 45 CFR 164.316: Policies and procedures and documentation requirements (Cornell LII, e-CFR text), checked 2026-10-26
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule, A Cybersecurity Resource Guide (NIST, February 2024), checked 2026-10-26
- Security Risk Assessment Tool (ONC), checked 2026-10-26
- HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 (HHS, Jan. 6, 2025, via GovInfo), checked 2026-10-26
- 45 CFR 160.404: Amount of a civil money penalty (Cornell LII, e-CFR text), checked 2026-10-26
- 45 CFR 102.3: Penalty adjustment and table (Cornell LII, e-CFR text), checked 2026-10-26
- 42 U.S.C. 17941: Recognition of security practices (Cornell LII), checked 2026-10-26
- 45 CFR 160.103: Definitions (Cornell LII, e-CFR text), checked 2026-10-26
Not medical advice. This post is general information about running a clinic and the software behind it. For a question about your health or a patient's care, ask a licensed clinician.
You've tried the workarounds.This one runs itself.
Thirty minutes on a clinic like yours: the overnight queue, a visit with the scribe on, a dispense from the note and a state report. Bring an export and we run the dry-run import while we talk.