HIPAA IT Compliance Requirements for Medical Practices
Published · Last updated · 11 min read

HIPAA IT compliance means meeting the Security Rule at 45 CFR Part 164, Subpart C: a documented risk analysis, risk management, and administrative, physical and technical safeguards for electronic protected health information (ePHI). It applies to every covered entity and business associate, including small medical practices. The rule is flexible on how, but not on whether, each safeguard is addressed and documented.
Key takeaways
- The HIPAA Security Rule applies to covered entities and business associates of every size; small practices get flexibility in how they comply, not an exemption.
- Safeguards fall into administrative, physical and technical categories, plus organizational requirements such as business associate agreements and documentation rules.
- "Addressable" does not mean optional: you must assess each addressable specification, implement it if reasonable, or document why and what you did instead.
- The written risk analysis is the requirement OCR cites most often in recent settlements, including the $800,000 Lehigh Valley Health Network ransomware settlement announced October 29, 2026.
- The January 2025 proposal to make encryption and MFA mandatory is not final; HHS lists July 2027 as its target for final action, and the current rule remains in force.
What is HIPAA IT compliance and who does it apply to?
HIPAA IT compliance is the part of HIPAA that governs how electronic protected health information is created, received, stored and transmitted. The Security Rule applies to covered entities (health plans, clearinghouses and providers who bill electronically, which includes nearly every medical practice) and to business associates that handle ePHI on their behalf, such as billing companies, cloud hosts and IT providers.
The Privacy Rule controls who may use and disclose protected health information in any form. The Security Rule focuses on ePHI and asks three things: protect its confidentiality, integrity and availability; guard against reasonably anticipated threats; and make sure your workforce follows the rules. The Breach Notification Rule then sets what happens when unsecured protected health information is compromised.
The rule is written to scale. Under 45 CFR 164.306(b), a practice may consider its size, complexity, technical infrastructure, costs and the likelihood and impact of risks when deciding how to meet each standard. A three-provider clinic and a hospital system have the same obligations, but they will meet them in very different ways.
What are the three categories of HIPAA safeguards?
The Security Rule organizes its standards into three safeguard categories, plus organizational and documentation requirements.
- Administrative safeguards (45 CFR 164.308). Risk analysis and risk management, a named security official, workforce security and access management, security awareness training, security incident procedures, a contingency plan with data backup and disaster recovery, periodic evaluation and business associate contracts.
- Physical safeguards (45 CFR 164.310). Facility access controls, workstation use and security, and device and media controls, including how you dispose of or reuse drives and laptops that held ePHI.
- Technical safeguards (45 CFR 164.312). Unique user IDs, emergency access procedures, automatic logoff, encryption and decryption, audit controls, integrity controls, person or entity authentication and transmission security.
- Organizational and documentation requirements (45 CFR 164.314 and 164.316). Business associate agreements, written policies and procedures, and keeping required documentation for six years from creation or last effective date.
In practice, most findings come from the administrative side. A practice can own good technology and still fail an investigation because it never analyzed its risks, never reviewed system activity or cannot show what it did.
What is the difference between required and addressable specifications?
Some implementation specifications are "required" and must be implemented as written. Others are "addressable." For an addressable specification, a practice must assess whether it is reasonable and appropriate in its environment. If it is, implement it. If it is not, document why and implement an equivalent alternative measure if one is reasonable.
Encryption of ePHI at rest and in transit is the best-known addressable specification. Very few practices can credibly document that encrypting laptops, mobile devices and email containing patient data is unreasonable today. Encryption also has a direct payoff: under the Breach Notification Rule, protected health information encrypted according to HHS guidance is not "unsecured," so a lost encrypted laptop generally does not trigger breach notification.
Multi-factor authentication is not named as a specification in the current rule, but the person or entity authentication standard and the risk analysis lead most practices to it, especially for email, remote access, the EHR and administrator accounts. Cyber insurers now commonly ask about MFA as well.
Why is the security risk analysis the most enforced requirement?
The risk analysis at 45 CFR 164.308(a)(1)(ii)(A) requires an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of all ePHI you hold. Everything else in the Security Rule depends on it, because your safeguards are supposed to respond to the risks you found.
OCR has made this its priority. Its Risk Analysis Initiative began in late 2024, and its resolution agreements through 2025 and 2026 repeatedly cite the same failure. In the Lehigh Valley Health Network settlement announced October 29, 2026, OCR cited the lack of an accurate and thorough risk analysis, no regular review of information system activity and late breach notification after a ransomware attack affecting 248,359 people. The health system paid $800,000 and accepted a three-year corrective action plan.
A defensible risk analysis covers every system that touches ePHI: the EHR, practice management and billing software, email, file shares, imaging, phones and fax, backups, laptops and mobile devices, and the business associates that host or support them. Our HIPAA risk assessment guide walks through the steps, and NorthStar offers a cybersecurity risk assessment built around the Security Rule.
What do business associate agreements need to include?
Any vendor that creates, receives, maintains or transmits ePHI for your practice is a business associate, and you need a written business associate agreement (BAA) before it handles that data. That includes EHR and billing vendors, cloud email and file storage, backup providers, IT support firms with access to your systems and shredding companies.
Under 45 CFR 164.314(a) and 164.504(e), the agreement must, among other things, limit how the business associate uses and discloses the information, require it to apply Security Rule safeguards, require it to report security incidents and breaches to you, require it to flow the same terms down to its own subcontractors, and require return or destruction of the information at the end of the contract.
HHS guidance on cloud computing makes one point practices often miss: a cloud provider that stores ePHI is a business associate even if the data is encrypted and the provider does not hold the key. Keep a current list of every business associate, where its BAA is filed, and when you last reviewed its security.
How does HIPAA apply to cloud services, EHRs and telehealth?
Moving systems to the cloud does not move the responsibility. The practice still owns its risk analysis, its access controls and its decisions about which services may hold ePHI. A hosted EHR shifts server management to the vendor, but your practice still controls who has accounts, how they sign in, whether former staff are removed and how data exported from the system is protected.
Telehealth follows the same rules. The temporary enforcement discretion OCR granted for telehealth during the COVID-19 public health emergency ended with the emergency on May 11, 2023, followed by a 90-day transition that closed August 9, 2023. Telehealth platforms that handle ePHI now need a BAA and must fit within your risk analysis like any other system.
Email deserves special attention. It is the most common entry point in OCR phishing cases, and it often holds years of patient communications. Account protections, encryption for messages that leave your organization and limits on automatic forwarding belong in every practice's plan.
What changes to the HIPAA Security Rule are coming?
On January 6, 2025, HHS published a proposed rule that would substantially rewrite the Security Rule. It would remove the required versus addressable distinction for most specifications, require encryption and MFA with limited exceptions, require a technology asset inventory and network map, set vulnerability scanning and penetration testing intervals, and require restoration of certain systems within 72 hours.
The proposal is not final. The federal government's Unified Agenda lists it under long-term actions with a target of July 2027. Our article on the HIPAA Security Rule delay to 2027 covers the details. The practical advice is the same either way: most of the proposed controls are already the expected result of a good risk analysis, and OCR is enforcing the current rule now.
What is a practical HIPAA IT compliance checklist?
- Name a security official and give that person time and authority to run the program.
- Inventory systems and data flows that create, receive, store or send ePHI, including business associates.
- Complete and document a risk analysis, then a risk management plan with owners and dates.
- Control access: unique accounts, MFA on email, remote access and the EHR, prompt removal of departed staff and periodic access reviews.
- Encrypt laptops, mobile devices, backups and email that leaves the practice.
- Patch and monitor: keep systems updated, collect logs and actually review them.
- Back up and test restores, with at least one copy protected from ransomware, and keep a written contingency plan.
- Train staff at hire and regularly afterward, with phishing practice.
- Sign and track BAAs for every vendor that touches ePHI.
- Keep documentation for six years and review the program whenever your environment changes.
What are the penalties for HIPAA IT non-compliance?
HIPAA civil money penalties are set in four tiers based on culpability, from lack of knowledge to willful neglect that is not corrected, with per-violation amounts and annual caps that HHS adjusts for inflation each year. Most cases end in resolution agreements rather than formal penalties, but those agreements typically combine a payment with a corrective action plan that OCR monitors, often for two or three years.
The costs that hurt small practices most usually come from the incident itself: downtime, restoration, forensic work, patient notification, legal advice and lost revenue. State attorneys general can also enforce HIPAA, and state privacy and breach laws may add requirements.
The HITECH Act was amended in 2021 to require HHS to consider whether a regulated entity had recognized security practices in place for the prior 12 months when it decides fines and audit outcomes. A documented program aligned to the 405(d) practices or the NIST Cybersecurity Framework is therefore worth more than a binder of templates.
How can NorthStar help your practice with HIPAA IT compliance?
NorthStar works with medical practices and outpatient clinics on the technical side of HIPAA: risk analysis, MFA and encryption, monitoring, backup and recovery, vendor reviews and the documentation OCR asks for. See our HIPAA compliance services and healthcare IT services. We help practices meet and document their requirements; responsibility for compliance stays with the practice.
Start with our free security check, review what managed IT costs for medical practices, read our healthcare breach response guide, or browse more healthcare resources.
What else do medical practices ask about HIPAA IT compliance?
Is there an official HIPAA certification for IT systems?
No. HHS does not certify software, vendors or practices as HIPAA compliant. Compliance depends on how a practice configures, uses and documents its systems.
Do small practices have to follow the Security Rule?
Yes. The rule has no size exemption. It lets smaller practices choose reasonable and appropriate measures based on their size, resources and risks, and document those choices.
How long do we keep HIPAA security documentation?
Six years from the date it was created or last in effect, whichever is later, under 45 CFR 164.316(b)(2).
Is encryption mandatory under HIPAA today?
It is an addressable specification under the current rule, so you must implement it or document why an alternative is reasonable. The 2025 proposal would make it required with limited exceptions, but that rule is not final.
Sources
- 45 CFR Part 164, Subpart C: Security Standards for the Protection of ePHI
- HHS: The Security Rule
- HHS: Guidance on Risk Analysis
- HHS: OCR settles ransomware investigation of Lehigh Valley Health Network (October 29, 2026)
- Federal Register: HIPAA Security Rule NPRM (January 6, 2025)
- HHS 405(d) Program: Health Industry Cybersecurity Practices
Industry Resources
Healthcare IT & HIPAA Support
NorthStar helps medical practices run risk analyses, close technical gaps and keep the documentation HIPAA expects.
Learn More →About the author

Ken Satkunam, CISM
President & Founder, NorthStar Technology Group
Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.