Key takeaways
- A risk analysis is a required part of the HIPAA Security Rule: an accurate and thorough look at risks to the confidentiality, integrity and availability of electronic patient information.
- The HHS and ONC Security Risk Assessment Tool is built for small and medium providers, but using it does not by itself make you compliant.
- Most of the work happens before you open the tool: listing devices, systems, vendors and how patient data moves.
- The analysis only counts if it leads to a risk management plan with owners and dates, revisited when things change.
What the rule actually asks for
The Security Rule lists risk analysis as a required implementation specification: the practice must 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[1]. Right next to it sits risk management, the duty to put in place security measures that reduce those risks to a reasonable and appropriate level[1].
Those two go together. A thick binder that lists every risk but changes nothing does not meet the standard, and neither does a set of new passwords chosen without any analysis behind them. The rule also expects a regular review of system activity, such as audit logs and access reports, and periodic evaluations when your environment or operations change[1].
Nearly every practice now holds patient information electronically: 91% of office-based physicians used a certified EHR in 2024, and a further 4% used a non-certified one[2]. If your practice is in that group, the Security Rule applies to you, whatever your size.
Four misconceptions to drop
- It is not a vendor's job. Your EHR vendor secures its system, but your risk analysis covers your devices, your network, your staff habits and your other vendors too.
- It is not a yes or no checklist. The point is to judge how likely each threat is and how bad the impact would be, then decide what to do.
- It is not one-and-done. The analysis should be revisited when you change systems, move offices, add a location or suffer an incident, and at a regular interval in between.
- A tool does not make you compliant. The HHS tool's own page says that its use neither is required by nor guarantees compliance with federal, state or local laws[3].
About the HHS SRA Tool
The Security Risk Assessment Tool was developed by the Office of the National Coordinator for Health IT together with the HHS Office for Civil Rights, and is designed to help medium and small health care providers; its page notes it may not be appropriate for larger organizations[3]. It comes as a desktop application for 64-bit Windows and as an Excel workbook that works in other spreadsheet software, and version 3.7 is the current release listed[3].
The tool walks you through questions about your policies, safeguards, devices and vendors, helps you rate risks, and produces a report you can keep as documentation. It is a sensible default for a small practice that does not have an IT security team. Larger groups and practices with complex networks often use a consultant or a commercial framework instead, but the underlying steps are the same.
Gather this before you open the tool
The questions go much faster when the facts are ready. Spend an hour collecting these, ideally with whoever manages your IT.
- Devices: every desktop, laptop, tablet, phone, server, scanner, copier and fax machine that stores or displays patient information, with who uses it and where it sits.
- Systems: your EHR or practice management system, imaging, billing, phone system, patient portal, email, texting and booking tools.
- Vendors: every business associate, with the status of each agreement.
- Data flows: how patient information enters, moves through and leaves the practice, including faxes, portal messages, referrals and exports.
- Current safeguards: backups and where they live, encryption, logins and multi-factor sign-in, antivirus, firewall, physical locks, shredding.
- History: past incidents, near misses, lost devices and the results of any earlier assessment.
Running the assessment
Set the scope
Decide which locations and systems are in scope. For most small practices the answer is everything that touches electronic patient information.
Enter your assets and vendors
Load the device, system and vendor lists you gathered. Do not skip the copier and the old laptop in the back office.
Answer the questions honestly
Answer for what actually happens, not what the policy says. If staff share a login at the front desk, record that.
Rate each risk
For every threat and vulnerability pair, rate how likely it is and how severe the impact would be. Use the same scale throughout.
Review the report as a team
Go through the high and medium risks with the physician owner and IT support. Agree which to fix first.
Turn it into a plan
For each risk you will address, write the action, the owner and the due date. Record any risk you decide to accept, and why.
| Likelihood \ Impact | Low impact | Medium impact | High impact |
|---|---|---|---|
| High likelihood | Medium | High | High |
| Medium likelihood | Low | Medium | High |
| Low likelihood | Low | Low | Medium |
Small practices depend more on outside vendors
Small practices tend to run on a wider mix of software suppliers than large groups. In 2024, only 32% of physicians in solo practice used an EHR from one of the five market-leading developers, compared with 90% in practices with more than 50 physicians[4]. That is not a problem in itself, but it does mean your analysis should look closely at each vendor's security features, support and update practices rather than assuming them.
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[4]
Show the data
| Item | Value |
|---|---|
| Solo practice | 32% |
| More than 50 physicians | 90% |
For each key vendor, note whether multi-factor sign-in is available and switched on, how quickly security updates are applied, where backups are stored, and what happens to your data if the vendor goes out of business. Those answers belong in the risk analysis as much as your own firewall settings do.
Threats every small practice should include
- Ransomware and other malware, usually arriving by email. Ransomware complaints to the FBI's Internet Crime Complaint Center rose from 2,385 in 2022 to 3,156 in 2024[5].
- Phishing and stolen passwords that let an attacker into email or the EHR.
- Lost or stolen laptops, phones and USB drives.
- Staff looking at records they have no work reason to open.
- Misdirected faxes, emails and portal messages.
- Power, internet or vendor outages that make records unavailable during clinic hours.
- Physical risks: an unlocked server closet, a break-in, water damage.
Availability counts. A ransomware attack that encrypts your schedule is a security incident even if no record is stolen, because patients cannot be seen safely without their information. Rate outage risks as seriously as theft.
What a usable risk management plan looks like
The report the tool produces is the analysis. The plan is the part you will actually use week to week, so keep it short enough to review at a monthly management meeting. One line per risk is enough.
- Risk: a plain description, such as front desk staff share one login.
- Rating: the likelihood and impact score from the analysis.
- Action: what you will do, such as unique logins with multi-factor sign-in for every user.
- Owner: one named person, not a role shared by three people.
- Due date and status: open, in progress or done, with the completion date.
- Evidence: where the proof lives, such as a screenshot of the new setting or a vendor's confirmation email.
- Accepted risks: anything you decide not to fix yet, with the reason and a date to revisit it.
Small practices often fix the cheapest risks first because they are easy. It is better to start with the high ratings, even if they take longer, and fit quick wins around them.
Keep it current and keep the proof
Repeat the analysis when something significant changes, such as a new EHR, a move, a merger, a new location or a serious incident, and review it at a fixed interval in between; many small practices choose once a year. Keep each version of the analysis, the risk management plan and evidence of the actions you completed for at least six years[6]. When investigators look at a breach, a missing or stale risk analysis is one of the first gaps they find.
Example: a two-dentist office
Example (fictional): A two-dentist practice with six staff runs the SRA Tool over two lunch hours. The inventory turns up an old front desk computer still holding scanned insurance cards, a shared front desk login, a backup drive that sits next to the server, and two vendors without signed agreements.
The team rates the shared login and the on-site-only backup as high risks. The plan gives the office manager a month to set up unique logins with multi-factor sign-in, asks the IT contractor to add an encrypted off-site backup and test a restore, wipes and recycles the old computer, and chases both agreements. Six weeks later the manager records each action as done, files the report and diaries the next review.
Frequently asked questions
Is a risk analysis really required for a tiny practice?
Yes. Risk analysis is a required part of the Security Rule for every covered practice that holds electronic patient information, whatever its size. The depth can match the size of the practice.
Does using the SRA Tool make us HIPAA compliant?
No. The tool helps you structure and document the analysis, but its own page says its use does not guarantee compliance. The analysis has to be accurate and lead to action.
How often should we redo it?
Whenever your systems, locations or operations change significantly, after a serious incident, and at a regular interval in between. Many small practices review it every year.
Can our IT company do it for us?
They can help, and their input is valuable. The practice still owns the analysis and the decisions about which risks to fix or accept.
References
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.308 - Administrative safeguards (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Office of the National Coordinator for Health IT (HealthIT.gov) (2026). Security Risk Assessment Tool (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Federal Bureau of Investigation, Internet Crime Complaint Center (IC3) (2024). Internet Crime Report 2024 (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑