All resources
CPOM Compliance Insights

Navigating HIPAA Compliance: A Guide for Healthcare Companies

Originally published: February 20, 2025Last reviewed: June 20, 2026By MedPath Compliance Group

The Health Insurance Portability and Accountability Act (HIPAA), enacted in 1996, sets the national baseline for protecting sensitive patient health information. For healthcare and digital health companies expanding their services, understanding and maintaining HIPAA compliance is essential — both to preserve patient trust and to avoid significant legal and financial exposure. This guide covers HIPAA's core components, the steps that matter most, and the federal and state developments reshaping the landscape in 2026.

1. HIPAA's Core Components

Privacy Rule. Sets national standards for protecting individually identifiable health information, requiring appropriate safeguards and defining when protected health information (PHI) may be used or disclosed without patient authorization.

Security Rule. Focuses on electronic PHI (ePHI), requiring administrative, physical, and technical safeguards to protect its confidentiality, integrity, and availability.

Breach Notification Rule. Requires covered entities to notify affected individuals, the Department of Health and Human Services (HHS), and in some cases the media, following a breach of unsecured PHI.

2. Steps to Achieve and Maintain Compliance

  • Conduct regular risk analyses. Identify where ePHI is stored, received, maintained, or transmitted, and assess the threats to it. A current, documented risk analysis is the single control OCR cites most often in enforcement actions — make it a standing priority, not a one-time exercise.
  • Implement the three safeguard categories. Administrative: policies, a designated security official, and regular workforce training. Physical: controlled access to facilities, workstations, and devices that handle ePHI. Technical: encryption, strong authentication, and audit controls that monitor access to ePHI.
  • Write and enforce policies and procedures. Establish clear rules for access, use, disclosure, and breach response — and review them as threats and regulations change.
  • Train your workforce continuously. Ongoing training builds a culture of compliance and prevents the inadvertent violations that drive many breaches.
  • Maintain a breach response plan. A tested plan with clear notification timelines and mitigation steps materially reduces the damage a breach causes.

3. Why Compliance Gets Harder as You Scale

As a company expands across states, payers, and vendors, HIPAA compliance grows more complex — more systems touch ePHI, more business associates enter the picture, and more state laws apply. A robust compliance program doesn't just reduce legal risk; it improves operational discipline and patient confidence, which is exactly what positions a company for durable growth.

4. The Proposed 2026 Security Rule Update — Status and What to Do Now

In December 2024, OCR proposed the most significant update to the HIPAA Security Rule since the 2013 Omnibus Rule, with the Notice of Proposed Rulemaking published in the Federal Register on January 6, 2025. The proposal would, among other things, make currently "addressable" safeguards mandatory and add specific controls such as multifactor authentication, encryption of ePHI at rest and in transit, network segmentation, asset inventories, and documented risk analyses.

Current status (as of mid-2026): this remains a proposed rule, not final law. The comment period closed in March 2025, OCR is still reviewing thousands of public comments, and the original spring-2026 finalization target has passed with no final rule published. A coalition of more than 100 hospital and provider organizations has asked HHS to withdraw the proposal, and under the current administration's deregulatory posture, the rule could still be finalized as written, narrowed, delayed, or withdrawn. Its final form and timing are genuinely uncertain.

The practical takeaway: don't over-build for requirements that may change, but recognize that most of the proposed controls — MFA, encryption, a current asset inventory, and a documented risk analysis — already reflect reasonable security in 2026, and OCR continues to enforce the existing Security Rule in the meantime. The no-regret moves are worth making regardless of how the rulemaking resolves.

5. State Laws Now Reach Beyond HIPAA

HIPAA is a floor, not a ceiling. A growing number of states regulate consumer health data more broadly than HIPAA does — sometimes covering data that falls outside HIPAA entirely. Examples include California's Confidentiality of Medical Information Act (CMIA), Washington's My Health My Data Act, Nevada's SB 370, and Connecticut's Data Privacy Act. These laws can require explicit consent before collecting consumer health data, mandate specific privacy disclosures, and grant consumers distinct rights. The list keeps growing, so any company handling health data across state lines should map the specific states it touches rather than assuming HIPAA compliance is sufficient on its own.

Conclusion

HIPAA compliance is a continuous, multi-layered effort — risk analysis, safeguards, training, breach readiness, and an eye on both federal rulemaking and a fast-expanding set of state laws. Many healthcare and digital health companies benefit from working with compliance specialists who understand both HIPAA and the Corporate Practice of Medicine (CPOM) framework, and who can help build tailored programs, risk assessments, and breach-response plans — so the team can focus on patient care with the data-protection foundation in place.

Need compliance guidance? If you're a healthcare startup — or you know a digital health founder who could use a hand — reach out to schedule a complimentary compliance strategy call. We'll talk through your compliance posture and how to align it with the current federal and state landscape.

Book a Strategy Call

This article is for general informational purposes regarding HIPAA and healthcare compliance. While MedPath offers compliance and operational guidance, this content is not legal advice. For legal questions specific to your circumstances, consult a licensed attorney.