OCR Says Most Practices Fail the Security Risk Analysis. Here’s How to Make Yours Easy
When the HHS Office for Civil Rights (OCR) investigates a healthcare provider, one of the first documents it asks to see is the Security Risk Analysis. For most practices, that is where the trouble starts.
At OCR’s cybersecurity conference earlier this year, senior OCR officials returned to the same point again and again: most organizations they investigate cannot provide a compliant risk analysis. [Insert attributed quote: speaker name, title, exact wording]. In OCR’s view, a practice without an accurate and thorough risk analysis cannot be HIPAA compliant, because every other security decision depends on it.
This is not a new problem, and it is not limited to large health systems. The good news is that a compliant risk analysis does not need to be a burden on a busy practice. This article explains what the Security Risk Analysis is, what OCR expects to see, why so many practices fall short, and how to complete yours quickly with the right tool.
What OCR found when it looked
The clearest evidence comes from OCR’s own audit program. In 2016 and 2017, OCR audited 166 HIPAA-covered entities and 41 business associates. Its industry report found that only 14% of covered entities had substantially fulfilled the requirement to conduct an accurate and thorough risk analysis. Put another way, 86% fell short.
The results for the next step were worse. Only 6% of covered entities adequately implemented risk management, which is the process of acting on what the risk analysis finds.
Those audits are several years old, but OCR’s comments this year suggest little has changed. The risk analysis remains the most commonly cited failure in OCR’s enforcement actions, and OCR has built a dedicated enforcement program around it.
Why the Security Risk Analysis is the foundation of HIPAA compliance
The HIPAA Security Rule requires covered entities to “conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability” of the electronic protected health information (ePHI) they hold (45 CFR 164.308(a)(1)(ii)(A)).
The Security Rule is deliberately flexible. It does not tell a three-doctor family practice to use the same safeguards as a 500-bed hospital. Instead, it asks each organization to decide which safeguards are “reasonable and appropriate” for its own size, systems and risks. That flexibility only works if you know what your risks are.
That is why the risk analysis comes first. It tells you:
- Where ePHI lives in your practice, and who and what can access it.
- Which threats are realistic for you, from phishing and ransomware to a lost laptop or an unlocked records room.
- Which of your current safeguards are working, and where the gaps are.
- Which risks matter most, so you spend time and money in the right places.
Your policies, staff training, access controls, backup plans and vendor agreements should all follow from it. Without a risk analysis, a practice is making security decisions without a map.
What an “accurate and thorough” risk analysis covers
OCR’s guidance on risk analysis sets out what it expects to see. A compliant SRA should:
Cover all ePHI, wherever it is created, received, stored or sent: your EHR, practice management system, email, laptops, phones, tablets, backups, cloud services and systems run by vendors.
Identify realistic threats and vulnerabilities, including human error, cyberattacks, equipment failure and natural events.
Assess your current security measures and whether they are being used properly.
Estimate the likelihood and impact of each threat, and assign a risk level.
Be documented, with the analysis kept for at least six years.
Be reviewed and updated regularly, and whenever something significant changes, such as a new EHR, a new location or a security incident.
It also needs to look across the three types of safeguard in the Security Rule:
Safeguard Examples of what the SRA looks at
Administrative Security officer responsibilities, staff training, access approval, sanctions policy, incident response, contingency planning, business associate agreements
Physical Facility access, workstation placement and use, device and media disposal, protection of servers and paper records
Technical Unique user logins, automatic logoff, encryption, audit logs, multi-factor authentication, secure email and messaging, backups
A generic template downloaded from the internet rarely meets this standard, because it does not describe your practice, your systems or your risks. OCR has made clear that a “check the box” document is not an accurate and thorough analysis.
The cost of getting it wrong
In 2024, OCR launched its Risk Analysis Initiative, an enforcement program aimed specifically at organizations that have not carried out a compliant risk analysis. By July 2026, it had produced 14 enforcement actions, and risk analysis failures also feature in many of OCR’s ransomware settlements.
Recent examples show that size is no protection:
Top of the World Ranch Treatment Center agreed to pay $103,000 and adopt a two-year corrective action plan after a phishing attack exposed the ePHI of 1,980 people. OCR found the organization had not conducted an accurate and thorough risk analysis.
BST & Co. CPAs, an accounting firm acting as a business associate, paid $175,000 after a ransomware attack. Again, OCR cited the failure to conduct a risk analysis.
Financial penalties are only part of the cost. Corrective action plans typically last two years and require the organization to complete a risk analysis, put a risk management plan in place, update policies and train staff, all under OCR monitoring. That work has to be done anyway. Doing it before an investigation is far cheaper and less disruptive than doing it after one.
HIPAA Journal featured on



