Guide
How to do a HIPAA risk assessment in a small practice.
By the Rekha Technologies team · Updated November 18, 2026
A HIPAA risk assessment means listing every place your practice keeps electronic patient information, judging what could go wrong with each and how serious it would be, and writing down what you will fix, who will fix it and by when.
The HIPAA Security Rule calls it a risk analysis and requires every practice it covers to do one, whatever its size (45 CFR § 164.308(a)(1)(ii)(A)).
For practice managers and the person responsible for HIPAA security. Checked against the regulations in November 2026.
Most small practices know they need a HIPAA risk assessment. Fewer know what a finished one contains. This guide walks through the steps HHS describes in its own guidance, in plain English, and ends with what to keep on file.
Why it matters now
The Office for Civil Rights (OCR), the part of HHS that enforces HIPAA, runs a Risk Analysis Initiative that focuses selected investigations on this one requirement. In April 2025 OCR announced a settlement with a small New York neurology practice after a ransomware attack. Its finding was that the practice "failed to conduct an accurate and thorough risk analysis." The settlement included a corrective action plan monitored by OCR for two years.
OCR calls the risk analysis "the foundation for effective cybersecurity practices and the protection of ePHI." ePHI, electronic protected health information, is what this guide calls electronic patient information.
What the rule requires
The Security Rule asks every practice to "conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability" of the electronic patient information it holds (45 CFR § 164.308(a)(1)(ii)(A)). It then requires security measures that reduce those risks "to a reasonable and appropriate level" (§ 164.308(a)(1)(ii)(B)).
There is no exemption for small practices. What the rule allows is scale: when choosing safeguards, a practice takes into account its size and capabilities, its systems, the cost of each measure, and how likely and how serious each risk is (§ 164.306(b)). A three-doctor office is not expected to look like a hospital. It is expected to have looked.
The rule does not prescribe a method or a form, but the analysis must be written down. People say "risk assessment" and "risk analysis" for the same thing; the rule's own term is risk analysis.
The steps, in plain English
HHS guidance lists the elements a risk analysis must include, whatever method you use. Here they are, in order.
1. Set the scope: all electronic patient information
The analysis covers every place electronic patient information is created, received, stored or sent. In a small practice that usually means the EHR and practice management system, email, the fax line or fax service, scanned documents, laptops, phones and tablets, USB drives, backups and cloud storage. It also covers vendors: the billing company, the IT provider, the EHR vendor and anyone else who handles the information for you.
2. Map where the information goes
OCR recommends identifying where electronic patient information is located, "including how ePHI enters, flows through, and leaves" your systems. Follow it from the phone call and the patient portal to the claim at the clearinghouse and the lab result coming back. Ask staff how they really work. This is where shared logins, personal phones and home computers tend to show up.
3. List what could go wrong
For each place, write down the threats you can reasonably expect and the weaknesses they could exploit. HHS groups threats as human (a phishing email, a stolen laptop, someone viewing records they should not), natural (a flood or a hurricane) and environmental (a power failure). Weaknesses can be technical, such as a computer that misses its updates, or not technical, such as having no written procedure for removing a former employee's access.
4. Check the protection you already have
Write down what protects each place today and whether it is set up and used properly: a second step at sign-in, automatic updates, monitored security software, encryption on laptops, tested backups, access removed the day someone leaves, and staff training. A protection that exists but is switched off does not count.
5. Rate how likely and how serious
For each threat and weakness, estimate how likely it is and how much harm it would do. You can use a simple scale of low, medium and high: HHS guidance accepts ratings like these, numbers, or a mix of both.
6. Decide what to fix first
Combine the two ratings into a risk level. Then list a corrective action for each risk, with an owner and a target date, highest risks first. That list is the start of your risk management plan, which the rule requires as a separate step (§ 164.308(a)(1)(ii)(B)).
7. Write it up and keep it
The analysis has to be documented, in writing or electronically, but no particular format is required (§ 164.316(b)(1)). Keep the documentation for six years from the date it was created or last in effect, whichever is later (§ 164.316(b)(2)(i)).
8. Review it when things change
The rule sets no fixed schedule. HHS guidance calls risk analysis an ongoing process and notes that some practices review it annually or as needed. Update it after a security incident, a change of ownership, turnover in key staff or management, or new technology such as a new EHR. A new office, or staff working from home, changes the picture too.
Mistakes small practices make
- Filing a template. A downloaded checklist that nobody compared with your real systems is not an accurate and thorough assessment.
- Leaving things out. Laptops that go home, phones with work email, the fax service and vendors are easy to miss.
- Stopping at the analysis. Finding risks without fixing them leaves the second requirement, risk management, undone.
- Assuming the EHR vendor covers everything. Your vendor protects its own system. Your computers, email, accounts and staff are still yours to assess.
- Letting it go stale. An analysis written before your last system change describes a practice that no longer exists.
Can you do it yourself?
Yes, if someone in the practice understands how your systems are set up and has time to do it properly. HHS offers a Security Risk Assessment Tool, built by its health IT office with OCR, whose target audience is "medium and small providers." HHS also states that use of the tool "is neither required by nor guarantees compliance with federal, state or local laws." The answers still have to describe your real systems, and the risks still have to be fixed.
Outside help makes sense when nobody in the practice knows how the computers, accounts and vendors are really set up, after a security incident, or when you want a second opinion.
Rekha Technologies does the HIPAA security risk analysis as a one-time project, quoted once we understand the scope, and it is also part of our per-device cybersecurity service. We list every place your patient information is held, assess the risks in your actual systems, write the analysis and the plan to fix what it finds, go through it with you in plain language, and update it every year and when something changes. No vendor can make a practice compliant on its own: your practice remains the covered entity and decides what gets fixed.
What may change
In January 2025 HHS proposed changes to the Security Rule (90 FR 898). Among other things, the proposal would require a written inventory of technology assets, a network map, and a review of the risk analysis at least once every 12 months. As of November 2026 the proposal has not been made final, so the rule described in this guide still applies. The steps above are the core of the work either way.
This guide is general information, not legal advice.
Sources
- 45 CFR § 164.308: risk analysis and risk management.
- 45 CFR § 164.306: the flexibility the rule allows by size and capability.
- 45 CFR § 164.316: documentation, and keeping it for six years.
- HHS: Guidance on Risk Analysis.
- HHS press release, April 25, 2025: settlement with a small neurology practice under the Risk Analysis Initiative.
- HealthIT.gov: Security Risk Assessment Tool.
- Federal Register, January 6, 2025: the proposed changes to the Security Rule.
Quick answers
Questions about HIPAA risk assessments.
Does a small practice need a HIPAA risk assessment?
Yes. The Security Rule's risk analysis requirement applies to every practice that keeps patient information electronically, whatever its size (45 CFR § 164.308(a)(1)(ii)(A)). Size changes how much work the analysis takes, not whether it is required: the rule lets a practice choose safeguards that fit its size, systems and costs (§ 164.306(b)).
Is a HIPAA risk analysis the same as a HIPAA risk assessment?
In everyday use, yes. The Security Rule's own term is risk analysis, and the tool HHS offers small and medium-sized practices is called the Security Risk Assessment Tool. Both names describe the same written review of the risks to a practice's electronic patient information.
How often should a practice update its HIPAA risk analysis?
The rule sets no fixed interval. HHS guidance calls risk analysis an ongoing process and notes that some practices review annually or as needed. Update the analysis after a security incident, a change of ownership, turnover in key staff, or a new system such as an EHR.
Can a practice use the HHS Security Risk Assessment Tool?
Yes. HHS built the tool with small and medium-sized providers in mind. HHS also says using the tool is neither required nor a guarantee of compliance: the answers have to describe the practice's real systems, and the risks found still have to be fixed.
What records should a practice keep from a HIPAA risk analysis?
The written analysis, the list of risks with their likelihood and impact, the risk management plan with owners and dates, and evidence of the fixes. The Security Rule requires the documentation to be kept for six years from its creation or the date it was last in effect, whichever is later (45 CFR § 164.316(b)(2)(i)).
Does a HIPAA risk analysis make a practice HIPAA compliant?
No. The risk analysis is one required part of the Security Rule. It shows what else needs doing: the fixes in the risk management plan, written policies, a business associate agreement with each vendor that handles patient information, and staff training.
What happens if a practice skips the HIPAA risk analysis?
The practice is out of compliance with a required part of the Security Rule, and OCR is actively enforcing that requirement. In April 2025 OCR announced a settlement with a small New York neurology practice after a ransomware attack, finding it had failed to conduct an accurate and thorough risk analysis. The settlement included a corrective action plan monitored for two years.
Related services
If you would rather have it done for you.
- HIPAA security risk analysisThe written analysis the Security Rule requires, with a plan to fix what it finds. Also sold on its own.
- Policies, BAA management and staff trainingWritten policies kept current, vendor agreements tracked, and staff trained with a record.
- Monitored protection on every computerSecurity software on each computer, watched around the clock by people who act on the alerts.
- Cybersecurity for medical practicesMonitoring, protection and HIPAA documentation, as one service priced per device.
Not sure your risk analysis would stand up?
A free 30-minute call. We tell you in plain language what a risk analysis of your practice would involve.