Crashcart Start your free trial

HIPAA security for small practices

HIPAA Security Rule requirements for small practices

The HIPAA Security Rule requires a small practice that bills health plans electronically to protect the patient information it keeps on computers and sends over networks. In practice that means a written risk analysis, a named security official, administrative, physical and technical safeguards chosen to fit the practice, a signed agreement with every vendor that handles that information, and six years of written records. Some safeguards are required outright; others are "addressable," which means you either put them in place or write down why you chose something else. For a small practice, size changes how you meet the HIPAA Security Rule, not whether you have to.

The rule's full name is the Security Standards for the Protection of Electronic Protected Health Information, and it sits in 45 CFR Part 164, Subpart C. The HHS Office for Civil Rights (OCR) enforces it and publishes a plain summary, the Summary of the HIPAA Security Rule. This guide goes through each part for a dental or medical office with a handful of computers and nobody whose job is IT.

Does the HIPAA Security Rule apply to a small practice?

The rule applies to covered entities and their business associates (45 CFR 164.302). A covered entity is a health plan, a health care clearinghouse, or "a health care provider who transmits any health information in electronic form in connection with a transaction" covered by HIPAA (45 CFR 160.103). Sending claims, eligibility checks or payment information to insurers electronically is what usually makes a dental, medical, therapy or chiropractic office a covered entity.

A practice that never conducts those transactions electronically may fall outside the rule. The line is technical, so check it rather than assume. CMS publishes a covered entity decision chart for checking. If you think you are not covered, confirm it with your attorney before acting on it.

There is no small-practice exemption. A solo dentist and a hospital follow the same standards. What the rule does allow is scaling: when choosing security measures, a practice must weigh its size, complexity and capabilities, its technical setup, the cost of the measures, and the probability and criticality of the risks (45 CFR 164.306(b)). A four-person office is not expected to buy what a health system buys. It is expected to think it through and write the reasoning down.

Business associates are covered too. Since the HITECH Act and the 2013 Omnibus Rule, the vendors that handle patient information for you answer to OCR directly for their own Security Rule compliance, as HHS's summary explains. More on them below.

What information the rule protects

The Security Rule protects electronic protected health information, or ePHI: health information that identifies a patient and is kept in or sent through electronic media. In a small office that includes the practice management or EHR database, digital X-rays and imaging, scanned intake forms and insurance cards, appointment reminders, email with patient details, and the backups of all of it.

Paper is outside this rule. HHS's summary says plainly that the Security Rule "does not apply to PHI that is maintained or transmitted on paper or verbally." Paper charts and phone calls fall under the separate HIPAA Privacy Rule instead.

The rule's general duties are in 164.306(a): ensure the confidentiality, integrity and availability of all ePHI you create, receive, maintain or transmit; protect against reasonably anticipated threats and against uses or disclosures the Privacy Rule doesn't allow; and make sure your workforce complies. Availability matters as much as secrecy. A ransomware attack that locks the schedule for a week is a Security Rule problem even if no record leaves the building.

Required and addressable implementation specifications

The safeguards are organized as standards, and most standards have implementation specifications under them. Each specification is labeled in the rule text as "Required" or "Addressable" (45 CFR 164.306(d)).

  • Required means you implement it.
  • Addressable means you assess whether it is reasonable and appropriate for your practice. If it is, you implement it. If it isn't, you document why and implement an equivalent alternative if one is reasonable and appropriate.

Addressable does not mean optional. HHS's risk analysis guidance says so in those words, and the decision has to be written down either way.

On October 14, 2026 we read the three safeguard sections on law.cornell.edu and counted every standard and specification. Here is what the rule contains:

Section Standards Required specifications Addressable specifications
Administrative, 164.308 9 10 11
Physical, 164.310 4 2 6
Technical, 164.312 5 2 5
Total 18 14 22

Three details from that count matter to a small practice. First, six of the 18 standards have no specifications under them at all: assigned security responsibility, evaluation, workstation use, workstation security, audit controls, and person or entity authentication. For those, the standard itself is the requirement, and the matrix in Appendix A to Subpart C marks each one "(R)". Second, one of the 14 required specifications, isolating health care clearinghouse functions, only applies to a clearinghouse inside a larger organization, so a practice has 13. Third, encryption appears twice, once for stored data and once for data in transit, and both are addressable. That does not mean a practice can skip encryption without a reason. It means the practice must decide, and a written decision not to encrypt laptops that hold patient data is hard to defend after one is stolen.

Administrative safeguards

Administrative safeguards are the policies, people and processes side of the rule (164.308). They make up more than half of the specifications. Here is what each standard means for an office with no IT staff.

Security management process

Four required pieces: a risk analysis, risk management (security measures that bring the risks down to a reasonable level), a sanction policy for staff who break the security rules, and a regular review of system activity records such as audit logs, access reports and incident reports. The risk analysis gets its own section below. Risk management is the follow-through: each risk the analysis finds becomes a task with an owner and a date.

Assigned security responsibility

Name one security official responsible for the policies and procedures. In a small practice this is usually the owner dentist or physician, or the office manager. Write the name down.

Workforce security and information access management

Make sure each person reaches only the ePHI their job needs, and that people without access can't get it. The addressable specifications cover authorizing and supervising staff, checking that each person's access is appropriate, and ending access when someone leaves. For a small office, that means separate accounts for every person, no shared front-desk login, practice software roles that match job duties, and a same-day process for departures. The employee offboarding checklist covers that last part step by step.

Security awareness and training

Train every workforce member, including the doctors. The addressable specifications are periodic security reminders, protection from malicious software, log-in monitoring, and password management. Keep a record of who was trained and when. Make sure every person knows what to do after clicking a phishing link, and who to tell.

Security incident procedures

Required: identify and respond to suspected or known security incidents, limit the harm where you can, and document each incident and its outcome. A one-page plan that says who to call first (your cyber insurer's breach line, your attorney, whoever runs your computers) and what not to do (don't wipe or switch off the affected machine) covers most of what a small practice needs at 8 a.m. on a bad Monday.

Contingency plan

Three required specifications: a data backup plan that creates "retrievable exact copies" of ePHI, a disaster recovery plan to restore lost data, and an emergency mode operation plan for keeping critical work going while systems are down. Testing the plans and ranking which systems matter most are addressable. For a practice, emergency mode usually means paper schedules and charting until the server is back. Backups only count if they can be restored, and if ransomware can't delete them. The guide to protecting backups from ransomware explains what to look for.

Evaluation

Periodically evaluate, technically and non-technically, how well your policies and procedures meet the rule, and do it again after changes that affect ePHI security. For a small office, a dated yearly review signed by the security official is a reasonable way to do it.

Business associate contracts

Required: a written agreement with each vendor that handles ePHI for you. See the section on business associate agreements below.

Physical safeguards

Physical safeguards protect the computers and the building they sit in (164.310).

Facility access controls. Limit physical access to your systems and the rooms that house them. The four specifications are addressable: contingency operations, a facility security plan, access control and validation (including visitors), and maintenance records for security repairs such as locks and doors. In a small office this is a locked closet for the server and network equipment, and a record of who has keys.

Workstation use and workstation security. Set rules for how computers that access ePHI are used and where they sit, and protect them physically. Front desk screens that face the waiting room, an operatory computer left signed in between patients, and a laptop that goes home in a car are what this standard is about.

Device and media controls. Control hardware and media coming in, going out and moving around. Disposal and media re-use are required: remove ePHI before a drive, copier or computer is reused, and decide how retired drives are wiped or destroyed. Keeping a record of equipment movements and backing up data before moving equipment are addressable. When you replace a computer, write down what happened to the old drive and who did it.

Technical safeguards

Technical safeguards are the settings and tools on the computers themselves (164.312). For email and texts to patients, see can you text or email patients under HIPAA.

Access control. Two required specifications: unique user identification (every person signs in with their own name or number) and an emergency access procedure for reaching ePHI during an emergency. Two addressable ones: automatic logoff after a set period of inactivity, and encryption of stored ePHI. A shared front-desk login fails this requirement, and it makes the audit logs useless, since nobody can tell who did what.

Audit controls. Use hardware, software or procedures that record and examine activity in systems holding ePHI. Find out whether your practice software keeps an audit trail and who can read it. Windows keeps its own sign-in records. Someone has to look at both, which ties back to the activity review in the administrative safeguards.

Integrity. Protect ePHI from improper alteration or destruction. The addressable specification is an electronic way to confirm data hasn't been changed without authorization.

Person or entity authentication. Verify that whoever signs in is who they claim to be. The current rule doesn't name multi-factor authentication, which means a code from your phone or a security key on top of the password. Most offices should still turn it on for email and any cloud practice software, because a stolen password alone then isn't enough. The guide to turning on MFA in Microsoft 365 walks through it for offices on Microsoft 365.

Transmission security. Guard ePHI sent over networks. Integrity controls and encryption in transit are both addressable. For most practices this covers email to patients and other offices, remote access to the server, and connections to cloud software.

Crashcart, which runs IT for small offices, checks these settings on every computer in a practice under HIPAA. It checks that every account has its own password, screens lock after 15 minutes, drives are encrypted and sign-ins are recorded, and every week it checks that email to your domain travels encrypted. Every check and fix goes into an evidence log with the date and the HIPAA section. It signs a business associate agreement with the practice. The practice still decides who should have access, fills in what only it knows in the documents, and signs them. The page for dental and medical practices lists what it does for each part of the rule.

The risk analysis

The risk analysis is required by 164.308(a)(1)(ii)(A): "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity or business associate."

It comes first because every addressable decision depends on it. HHS's Guidance on Risk Analysis says the rule doesn't prescribe a method, but any method must cover all ePHI in every form of electronic media, find where it is stored and sent, identify threats and vulnerabilities, assess current security measures, rate likelihood and impact, assign risk levels, and be documented and kept up to date.

The Office of the National Coordinator for Health IT (ONC) and OCR publish a free Security Risk Assessment Tool aimed at small and medium practices, as a Windows application or an Excel workbook. Using it doesn't guarantee compliance, and the tool's own documentation says it may not catch every risk.

OCR has made this requirement an enforcement focus. It runs a Risk Analysis Initiative, and by June 2026 it had announced its 14th enforcement action under it. One was a small New York neurology practice hit by ransomware, which paid $25,000 and accepted two years of OCR monitoring after OCR found it had never done an accurate and thorough risk analysis.

The step-by-step version, including how to use the SRA Tool and how often to redo it, is in how to do a HIPAA risk analysis for a small practice.

Business associate agreements

Which vendors need a business associate agreement goes vendor by vendor, with HHS's own examples.

A business associate is a person or company, other than your own staff, that creates, receives, maintains or transmits PHI on your behalf, or provides services such as billing, accounting, legal or consulting work that involve your PHI (45 CFR 160.103). For a small practice the list usually includes the cloud practice management or EHR vendor, the billing company or clearinghouse, cloud backup, the email provider if email carries patient information, the imaging vendor with remote access, and whoever runs your IT.

Under 164.308(b), you may let a business associate handle ePHI only after you get "satisfactory assurances" that it will safeguard the information, documented in a written contract. 164.314(a) sets what the contract must say on the security side: the vendor will comply with the Security Rule, will require the same of any subcontractor that handles the ePHI, and will report security incidents to you, including breaches. The Privacy Rule adds its own contract terms, and HHS publishes sample business associate agreement provisions that cover both.

A vendor that only stores encrypted data still counts. HHS's cloud computing guidance says a cloud provider that stores ePHI is a business associate "even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data."

Keep a list of every vendor that touches patient data, whether each has signed an agreement, and where the signed copy is. Ask for the agreement before you sign up with a new vendor, not after.

Breach notification in brief

The Breach Notification Rule (45 CFR 164.400 to 164.414) is separate from the Security Rule but follows directly from it. A breach is an impermissible use or disclosure of PHI that compromises its security or privacy. Any impermissible use or disclosure is presumed to be a breach unless a risk assessment of four factors shows a low probability that the information was compromised: what information was involved, who got it, whether anyone acquired or viewed it, and how far the risk has been mitigated (164.402). HIPAA breach notification rules for small practices has the full steps and deadlines.

If a breach of unsecured PHI happens:

  • Patients. Notify each affected person without unreasonable delay and no later than 60 calendar days after discovery (164.404). The clock starts when anyone on your staff other than the person who caused it knew, or should have known with reasonable diligence.
  • HHS. For 500 or more people, notify HHS at the same time as the patients. For fewer than 500, log the breach and report it to HHS within 60 days after the end of the calendar year (164.408).
  • Media. For more than 500 residents of one state or jurisdiction, notify prominent media outlets there within the same 60 days (164.406).
  • Business associates must tell you within 60 days of discovering a breach on their side (164.410).

The practice carries the burden of proving it sent every notice or that no breach occurred (164.414), so document the four-factor assessment even when you decide not to notify. Encryption that meets HHS's guidance on unsecured PHI makes data "secured," and a lost device holding only secured data doesn't trigger these notices. That is the strongest practical argument for treating the addressable encryption specification as a yes. State breach laws can add their own notices on top.

Documentation and the six-year rule

Every policy and procedure the rule requires must be in writing, electronic is fine, and so must every action, activity or assessment the rule says to document (164.316(b)(1)). That covers the risk analysis, the risk management plan, the reasons behind each addressable decision, training records, incident records, the contingency plan, evaluations and business associate agreements.

Three required specifications govern those documents (164.316(b)(2)):

  • Keep them for 6 years from the date created or the date last in effect, whichever is later. A policy written in 2026 and replaced in 2029 must be kept until 2035.
  • Make them available to the people responsible for carrying them out.
  • Review them periodically and update them when changes in your environment or operations affect ePHI security.

The six years apply to Security Rule documentation, not to patient charts. HHS says HIPAA has no medical record retention period; state law generally sets that.

Keep old versions when you update a document. An investigator looking at a 2024 breach will ask what your policies said in 2024.

Proposed changes to the Security Rule

On December 27, 2024, OCR issued a proposed rule to update the Security Rule, published in the Federal Register on January 6, 2025 as 90 FR 898. As of October 14, 2026, it is still a proposal. We searched the Federal Register for the rule's regulation number (RIN 0945-AA22) that day and found no final rule. HHS's page says "the current Security Rule remains in effect."

According to HHS's fact sheet, the proposal would, among other things:

  • remove the difference between required and addressable specifications, with limited exceptions
  • require encryption of ePHI at rest and in transit, and multi-factor authentication, each with limited exceptions
  • require a written technology asset inventory and a network map, updated at least every 12 months
  • require written procedures to restore certain systems and data within 72 hours
  • require vulnerability scanning at least every six months and a penetration test at least every 12 months
  • require a compliance audit at least every 12 months

None of these is required today. Several are good practice anyway, and a practice that already encrypts, uses multi-factor authentication and keeps an inventory will have less to change if a final rule arrives.

A starting checklist for a small practice

  1. Confirm the practice is a covered entity, and write down why.
  2. Name the security official.
  3. List every computer, server, phone, cloud service and vendor that holds or touches ePHI.
  4. Do the risk analysis, rating each risk by likelihood and impact.
  5. Turn each risk into a task with an owner and a date.
  6. Give every person their own login, and end access the day someone leaves.
  7. Turn on screen locks, disk encryption and multi-factor authentication, or document why not.
  8. Back up every system that holds ePHI, test a restore, and write the contingency plan.
  9. Write a one-page incident plan with your insurer's breach line and your attorney's number.
  10. Get a signed business associate agreement from every vendor on the list.
  11. Train staff and record who completed it.
  12. Write down each addressable decision and the reason.
  13. Keep every version of every document for six years.
  14. Review everything at least once a year and after any big change.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.