What the Security Rule actually requires
HIPAA Security Risk Assessment for Small Practices: What It Covers and How Often
The HIPAA Security Rule requires every practice to assess the risks to its patient data. Here is what the assessment must cover and how often to update it.
In shortRequired for every practice, with no fixed schedule
A HIPAA security risk assessment is a documented review of where your practice holds electronic patient information, what could go wrong with it, and what you are doing about it. The Security Rule requires one of every covered practice, whatever its size, and the Office for Civil Rights has made it the focus of a dedicated enforcement initiative.
What the Rule Requires
The requirement sits in the Security Rule’s administrative safeguards. Under 45 CFR 164.308 on the eCFR, a covered entity must conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the electronic protected health information it holds. The rule calls this a risk analysis. It is a required specification, not an addressable one, and there is no exemption for small practices.
The next line of the rule requires risk management: putting security measures in place that reduce the risks you found to a reasonable and appropriate level. The assessment is only half of the obligation. Acting on it is the other half, and it is where managed cybersecurity does most of its work.
What a Risk Assessment Covers
The HHS Guidance on Risk Analysis sets out what regulators expect to see. In plain terms:
- Scope. Every place patient information is created, received, stored or sent: the EHR, email, laptops and phones, imaging devices, copiers and scanners, backups, the patient portal, and the billing or transcription services you send data to.
- Threats and vulnerabilities. What could reasonably happen: ransomware, a stolen laptop, a phished password, a former employee with an active login, a failed backup.
- Current safeguards. What already protects each system, such as encryption, multi-factor authentication, access controls and logging.
- Likelihood and impact. How probable each threat is and how much harm it would do.
- Risk level and a plan. A ranked list of risks, with what you will do about each one, who owns it and by when.
- Documentation. The whole analysis in writing.
A Checklist Is Not a Risk Assessment
A common shortfall is a form that walks through the Security Rule and ticks each requirement. That is a gap analysis: it shows which controls you have. A risk analysis starts from your own systems and data and asks what could go wrong with them. Regulators treat the two differently, and a checklist alone does not satisfy the requirement.
How Often It Must Be Done
The current Security Rule does not name a frequency. The HHS guidance describes risk analysis as an ongoing process and says it should be reviewed and updated as the environment changes. In practice that means revisiting it when you:
- adopt a new EHR, patient portal or telehealth tool
- open or close a location, or change ownership
- have a security incident or a near miss
- change your IT provider or a key vendor
- lose staff who held administrative access
Most practices also review it once a year. That is sound practice and what cyber insurers usually expect, but it is a convention, not the wording of the current rule.
What the Proposed Rule Would Change
In January 2025 HHS published a proposed update, the first major change to the Security Rule in more than a decade. Among other changes, it would require a written risk analysis reviewed at least every 12 months, supported by a technology asset inventory and a network map. The details are in the HHS Security Rule proposed rule fact sheet.
The proposal is not final. The federal regulatory agenda now targets July 2027 for final action, and the content could still change. The current rule applies today. Because the proposed controls are already good practice, building toward them now carries little risk.
A Practical Process for a Small Practice
- List your systems and vendors. Anything that touches patient information, including personal phones used for work.
- Map the data. Where information enters, where it is stored and where it leaves.
- Identify threats and existing safeguards for each system.
- Rate each risk by likelihood and impact.
- Write the remediation plan, with owners and dates.
- Review progress each quarter and update the analysis when something changes.
The federal government offers a free Security Risk Assessment Tool on HealthIT.gov, designed for small and medium practices. It gives the work a structure. It does not do the work for you, and its output only counts if someone acts on it.
Keep the Documentation
The Security Rule requires documentation to be retained for six years. Keep each version of the risk analysis, the remediation plan and evidence of what was fixed. If a regulator, an insurer or a hospital partner asks, a dated file is what answers the question.
Where an IT Provider Fits
An IT provider cannot make the practice’s decisions, but it holds most of the facts the analysis needs: the device inventory, who has access to what, patch status, backup results and security alerts. VirtuWorks signs a Business Associate Agreement and implements the technical safeguards on every managed plan. The formal risk assessment, remediation tracking and audit evidence are delivered through the AI Readiness and Compliance add-on. Our healthcare IT support page describes the full service, and our guide to HIPAA-compliant IT for medical practices covers the controls behind it. Prices are on the plans and pricing page. To talk through where your practice stands, Schedule a Call.
Frequently asked questions
Is a HIPAA risk assessment required for a small practice?
Does HIPAA require a risk assessment every year?
Can we use the free HHS Security Risk Assessment Tool?
Referenced in this article
Ready
HIPAA Security Risk Assessment for Small Practices: What It Covers and How Often