The HIPAA Security Rule requires medical and dental practices, and the IT vendors that handle their patient data, to protect electronic protected health information with administrative, physical and technical safeguards. For a small practice the core HIPAA IT requirements are a documented risk analysis, business associate agreements with vendors, access and audit controls, a contingency plan with tested backups, workforce training and written policies. HHS proposed major Security Rule changes in January 2025, but as of November 2026 the current rule remains in effect. This is general information, not legal advice.
HIPAA IT requirements come from the HIPAA Security Rule, which requires medical and dental practices, and the vendors that handle their patient data, to protect electronic protected health information (ePHI) with administrative, physical and technical safeguards. For a small practice, that boils down to a documented risk analysis, business associate agreements with IT vendors, access and audit controls, encryption where reasonable, a tested contingency plan, workforce training and written policies. The rule scales to your size, but none of those pieces is optional.
This guide explains each requirement in IT terms, the status of the proposed Security Rule changes as of November 2026, and what a small practice can do this quarter. It is general information, not legal advice; confirm your obligations with your attorney or compliance advisor.
Who HIPAA IT requirements apply to
According to the HHS summary of the Security Rule, the rule applies to health plans, health care clearinghouses, health care providers that transmit health information electronically in connection with transactions HHS has adopted standards for (such as electronic claims), and their business associates. Almost every medical, dental, therapy and chiropractic practice that bills insurance electronically is a covered entity.
The Security Rule protects ePHI: protected health information maintained in or transmitted by electronic media. Paper charts and phone conversations fall under the Privacy Rule, not the Security Rule. In a modern practice, though, almost everything is electronic: the EHR, the practice management system, imaging, email, scanned intake forms, the billing service, text reminders and backups.
HHS describes the rule as flexible, scalable and technology neutral. It does not name specific products. Instead it asks each practice to choose measures based on its size, complexity and capabilities, its technical infrastructure, the cost of security measures, and the probability and criticality of risks to ePHI. That flexibility is real, but it comes with a documentation burden: you have to be able to explain your choices.
HIPAA security rule requirements at a glance
| Safeguard area | What it requires | What it usually means in IT terms |
|---|---|---|
| Security management process | Risk analysis, risk management, sanction policy, information system activity review | A written risk analysis, a remediation plan, regular log and access reviews |
| Assigned security responsibility | A named security official | One person accountable, even if an MSP does the technical work |
| Workforce security and access management | Appropriate authorization and access based on role | Role-based EHR permissions, prompt removal of departed staff |
| Security awareness and training | Training for all workforce members | Onboarding training, phishing simulations, records of attendance |
| Security incident procedures | Identify, respond to, mitigate and document incidents | An incident response plan and a log of incidents |
| Contingency plan | Data backup, disaster recovery, emergency mode operations | Tested backups, a recovery plan, a way to see patients if systems are down |
| Evaluation | Periodic technical and nontechnical assessment | An annual review of how well safeguards are working |
| Business associate contracts | BAAs before vendors handle ePHI | BAAs with your EHR, IT provider, cloud backup, email and billing vendors |
| Facility access and workstation security | Limit physical access, secure workstations | Locked server closet, screen locks, privacy screens at the front desk |
| Device and media controls | Track and properly dispose of hardware and media | Asset inventory, secure wiping before reuse or disposal |
| Access control | Unique user IDs, emergency access, automatic logoff, encryption (addressable) | No shared logins, timeouts, encrypted laptops |
| Audit controls | Record and examine activity in systems with ePHI | EHR audit logs, Microsoft 365 logs, someone who reviews them |
| Integrity and authentication | Protect ePHI from improper alteration; verify users | MFA, file integrity protections, EDR |
| Transmission security | Guard ePHI sent over networks; encryption (addressable) | Encrypted email or portals, VPN, encrypted WiFi |
Documentation of policies, procedures and required assessments must be kept for six years from the date of creation or the date it was last in effect, whichever is later, and reviewed periodically.
The HIPAA risk analysis comes first
The administrative safeguards in 45 CFR 164.308 list risk analysis as a required implementation specification. HHS describes it as an "accurate and thorough assessment" of potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI. Everything else in the rule flows from it, because the risk analysis is how you decide which safeguards are reasonable and appropriate for your practice.
A useful HIPAA risk analysis for a small practice:
- Lists every place ePHI lives or travels: EHR, imaging, email, file shares, laptops, phones, backups, the billing company, patient portals, fax-to-email services.
- Identifies realistic threats to each (phishing, ransomware, stolen laptop, former employee access, vendor breach, flood or fire).
- Notes existing safeguards and gaps.
- Rates likelihood and impact.
- Produces a risk management plan with owners and dates.
- Gets updated when something material changes.
The free Security Risk Assessment Tool from ONC, developed in collaboration with OCR, is aimed at small and medium providers. The current version is 3.7, available as a Windows application and an Excel workbook. For the Windows application, the page says information entered is stored locally and HHS does not collect it. Its disclaimer says using it is neither required by nor a guarantee of compliance with the law, and the tool itself reminds users that the survey alone may not identify every risk. Treat it as a structured starting point.
OCR treats a missing or shallow risk analysis as a serious failure. In a February 19, 2026 settlement, OCR announced that Top of the World Ranch Treatment Center, an Illinois substance use disorder treatment provider, paid $103,000 and agreed to a two-year corrective action plan. The investigation followed a phishing attack on a workforce member's email account that compromised ePHI for 1,980 patients, and OCR found evidence the provider had not conducted an accurate and thorough risk analysis. HHS called it the 11th enforcement action in OCR's Risk Analysis Initiative.
Business associate agreements with IT vendors
A business associate is a person or company, other than your own workforce, that creates, receives, maintains or transmits PHI on your behalf. Your EHR vendor, cloud backup provider, email host, billing service and outsourced IT provider usually qualify.
The Security Rule requires a written business associate agreement before a business associate handles your ePHI. According to HHS, the BAA must document the vendor's assurances, require it to comply with the Security Rule, require it to pass the same obligations to subcontractors, and require it to report security incidents and breaches to you.
HHS's cloud computing guidance settles a common argument: a cloud service provider that stores ePHI is a business associate "even if the CSP processes or stores only encrypted ePHI and lacks an encryption key." The same logic applies to IT vendors. If your managed IT provider runs your server, backups or Microsoft 365 tenant, it needs a HIPAA business associate agreement as an IT vendor, and so do the cloud services it puts your data into.
Keep a BAA list with vendor name, what ePHI they touch, BAA date and renewal date. Missing BAAs are one of the easiest gaps to close.
Encryption is addressable, which is not the same as optional
Under the technical safeguards in 45 CFR 164.312, encryption and decryption of stored ePHI and encryption of transmitted ePHI are both labeled addressable. HHS explains that addressable means you must implement the specification if it is reasonable and appropriate. If it is not, you must document why and adopt an alternative measure that achieves the same purpose, if that alternative is reasonable and appropriate.
For a small practice in 2026, it is hard to write a convincing explanation of why laptops should not be encrypted. Windows Pro and macOS include full-disk encryption (BitLocker and FileVault). Encrypted email and patient portals are widely available. Our view: encrypt every laptop, phone and portable drive that might hold ePHI, use encrypted channels for sending patient data, and document it.
Encryption also matters after an incident. HIPAA's breach notification rules apply to unsecured PHI, and HHS guidance says ePHI encrypted to its standard, with the key not breached, is not unsecured. HHS adds that decryption keys should be kept on a separate device or location from the data. The Massachusetts data breach notification law has its own encryption definition. Your attorney makes the call after an incident, but encryption gives them something to work with.
Audit controls and activity review
Audit controls are a standard in 164.312: practices must implement mechanisms that record and examine activity in information systems containing ePHI. Information system activity review, under the security management process, requires regularly reviewing records such as audit logs, access reports and security incident tracking reports.
In practice:
- Turn on EHR audit logging and know how to pull a report of who opened a given chart.
- Turn on and retain Microsoft 365 or Google Workspace audit logs.
- Send firewall and EDR alerts to someone who actually reads them.
- Put a monthly or quarterly access review on the calendar and record that it happened.
Logs nobody reviews satisfy half the requirement at best.
Contingency plan: backups, recovery and emergency mode
The contingency plan standard in 164.308(a)(7) includes three required specifications (a data backup plan, a disaster recovery plan and an emergency mode operation plan) and two addressable ones (testing and revision procedures, and an applications and data criticality analysis).
For a practice, that means answering some uncomfortable questions in advance. If ransomware encrypts the EHR server on a Monday morning, how do you see today's patients? How long until you can restore? When did anyone last test a full restore?
A workable contingency plan covers:
- Backups of every system holding ePHI, with at least one copy offline or immutable so ransomware cannot reach it
- Regular restore tests, documented
- A ranked list of systems to bring back first
- Paper or downtime procedures for scheduling, charting and prescriptions
- Contact lists that live outside your email
Our data backup and disaster recovery service is built around those steps, and the decisions behind them are covered in our post on backup vs disaster recovery.
Workforce training
Security awareness and training is a required standard for all workforce members, including the front desk, hygienists, billers and part-time staff. Its implementation specifications (security reminders, protection from malicious software, log-in monitoring and password management) are addressable, but the standard itself is not.
Phishing was the way in for the OCR settlement described above, and it is the threat training addresses most directly. Short sessions at onboarding, regular simulated phishing tests and a simple way to report suspicious email do more than an annual slideshow. Record who completed what.
HIPAA security rule changes: status as of November 2026
On December 27, 2024, HHS's Office for Civil Rights issued a notice of proposed rulemaking to update the Security Rule for the first time since 2013. It was published in the Federal Register on January 6, 2025. According to the HHS fact sheet, the proposal would, among other changes:
- remove the distinction between required and addressable specifications, with limited exceptions
- require written documentation of all Security Rule policies, procedures, plans and analyses
- require a technology asset inventory and network map, updated at least every 12 months
- require encryption of ePHI at rest and in transit, with limited exceptions
- require multi-factor authentication, with limited exceptions
- require vulnerability scanning at least every six months and penetration testing at least every 12 months
- require written procedures to restore certain systems and data within 72 hours
- require a compliance audit at least every 12 months
- require business associates to verify their technical safeguards to covered entities at least every 12 months
Status as of November 14, 2026: the rule has not been finalized. The Federal Register lists only the January 2025 proposed rule for this rulemaking (RIN 0945-AA22). The most recent Unified Agenda entry on reginfo.gov lists it under Long-Term Actions with a final action date of July 2027; an earlier agenda had targeted May 2026. Agenda dates are planning targets, not commitments, and a final rule could differ from the proposal. HHS states that the current Security Rule remains in effect.
Our advice is not to wait. MFA, encryption, an asset inventory, vulnerability scanning and tested restores are good practice under the current rule, and a thorough risk analysis will usually point to them anyway. If the final rule resembles the proposal, practices that did this work early will have far less to do.
A 90-day plan for a small practice
- Name your security official and write it down.
- Run or update your risk analysis, using the SRA Tool if you do not have another method.
- Collect BAAs from every vendor that touches ePHI.
- Encrypt every laptop and confirm it with a report.
- Turn on MFA for email, remote access, the EHR (if supported) and admin accounts.
- Confirm backups cover every ePHI system, keep one copy offline or immutable, and test a restore.
- Turn on audit logging and schedule access reviews.
- Run phishing training and record attendance.
- Write or update your policies and incident response plan.
- Schedule your next evaluation.
Massachusetts practices should remember that state law applies too. Patient Social Security numbers and payment card data also fall under 201 CMR 17.00, which requires its own written security program.
Our healthcare IT support page explains how we support medical and dental practices, and our cybersecurity services and cloud services pages cover the security and Microsoft 365 pieces in more depth. If your last risk analysis is more than a year old, start there; it will tell you which of the other nine steps matter most for your practice.
Frequently asked questions
What are the HIPAA IT requirements for a small practice?
The Security Rule requires a documented risk analysis and risk management plan, a named security official, workforce access controls and training, security incident procedures, a contingency plan with data backup and disaster recovery, physical safeguards for workstations and devices, technical access controls, audit controls, authentication, transmission security, business associate agreements with vendors, and written policies kept for six years. How you meet each one scales to your size and risks.
Is encryption required under HIPAA?
Under the current Security Rule, encryption of ePHI at rest and in transit is an addressable implementation specification. Addressable does not mean optional. A practice must implement it if reasonable and appropriate, or document why not and adopt an equivalent alternative. In practice, laptops and email are hard to protect without encryption. The 2025 proposed rule would make encryption required with limited exceptions.
Does my IT company need to sign a business associate agreement?
If your IT provider creates, receives, maintains or transmits ePHI on your behalf, including managing servers, backups or cloud systems that hold patient data, it is a business associate and you need a BAA before it starts. HHS guidance says a cloud provider storing only encrypted ePHI without the key is still a business associate. Your attorney should review the agreement.
Has the new HIPAA Security Rule been finalized?
No. HHS published the proposed rule in the Federal Register on January 6, 2025. As of November 14, 2026, the Federal Register lists only the proposed rule for this rulemaking, and the most recent Unified Agenda entry on reginfo.gov lists it under Long-Term Actions with a final action date of July 2027. HHS states the current Security Rule remains in effect.
How often should a practice do a HIPAA risk analysis?
The current rule does not name a fixed interval, but it requires regulated entities to regularly reevaluate risks to ePHI and to review security measures as the environment changes. We recommend updating it at least yearly and after major changes, such as a new EHR, a move, or new remote access. The proposed rule would add specific timeframes, including reviews at least every 12 months.
Sources and references
- HHS: Summary of the HIPAA Security Rule (content last reviewed August 7, 2026)
- eCFR: 45 CFR 164.308, administrative safeguards
- eCFR: 45 CFR 164.312, technical safeguards
- eCFR: 45 CFR 164.404, notification to individuals
- HHS: 2025 HIPAA Security Rule Notice of Proposed Rulemaking
- HHS: HIPAA Security Rule NPRM fact sheet
- Federal Register: HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, January 6, 2025)
- Reginfo.gov: Unified Agenda entry, RIN 0945-AA22
- Reginfo.gov: Spring 2025 Unified Agenda entry, RIN 0945-AA22
- HHS: Guidance to render unsecured PHI unusable, unreadable, or indecipherable
- HealthIT.gov (ONC): Security Risk Assessment Tool
- HHS: Guidance on HIPAA and Cloud Computing
- HHS press release: OCR settles HIPAA Security Rule investigation with Top of the World Ranch Treatment Center (February 19, 2026)