HIPAA Omnibus Rule Requirements: Privacy, Security, and Enforcement Impacts for Organizations

Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Omnibus Rule Requirements: Privacy, Security, and Enforcement Impacts for Organizations

Kevin Henry

HIPAA

February 14, 2025

7 minutes read
Share this article
HIPAA Omnibus Rule Requirements: Privacy, Security, and Enforcement Impacts for Organizations

The HIPAA Omnibus Rule requirements unify and expand privacy, security, and enforcement provisions so you can safeguard Protected Health Information (PHI) and Electronic Protected Health Information (ePHI) end to end. The rule clarifies duties for covered entities and extends direct liability to business associates, strengthening accountability across the data lifecycle.

This guide explains what the rule demands in practice—how to tighten privacy controls, implement risk-based security, manage breach response under the Breach Notification Rule, and prepare for HIPAA enforcement actions and Office for Civil Rights (OCR) audits.

Expanded Privacy Protections

Authorization and marketing limits

  • Obtain written authorization before using or disclosing PHI for marketing unrelated to care and before any “sale of PHI.”
  • Allow patients to opt out of fundraising; only limited demographic and encounter details may be used for fundraising outreach.

Minimum necessary and data segmentation

  • Apply the “minimum necessary” standard to routine disclosures and internal access, using role-based rules and data masking where feasible.
  • Segment sensitive categories (for example, substance use disorder or reproductive health data where applicable) to reduce unwarranted exposure.

Genetic information and underwriting

  • Treat genetic information as PHI and prohibit its use for health plan underwriting.

Practical steps

  • Map PHI data flows, including disclosures to vendors and downstream subcontractors.
  • Update consent/authorization forms and standard operating procedures to reflect Omnibus restrictions.

Strengthened Security Requirements

Risk-based security for ePHI

  • Conduct enterprise-wide Risk Assessment Protocols covering threats, vulnerabilities, likelihood, impact, and control effectiveness for ePHI.
  • Use the results to drive a living risk management plan with named owners, milestones, and metrics.

Technical and administrative safeguards

  • Access controls: unique IDs, least-privilege roles, multi-factor authentication for remote and privileged access.
  • Audit controls: centralized logging, immutable audit trails, and routine review for anomalous access to ePHI.
  • Integrity and transmission security: encryption of ePHI at rest and in transit, secure APIs, and key management.
  • Device/media controls: secure disposal, encryption of portable media, and automated mobile device management.
  • Workforce safeguards: pre-employment screening, role-based training, and sanctions for violations.

Business Associate Agreements (BAA)

  • Execute BAAs that obligate vendors to Security Rule controls, breach reporting, and downstream flow-down terms for subcontractors.
  • Evaluate vendors’ security posture before contracting and at renewal; require remediation of gaps.

Increased Penalties for Non-Compliance

Four-tier penalty structure

HIPAA enforcement uses four tiers based on culpability: (1) no knowledge, (2) reasonable cause, (3) willful neglect corrected, and (4) willful neglect not corrected. Per-violation amounts and annual caps escalate by tier, with the highest tier reserved for uncorrected willful neglect.

When investigations become mandatory

Findings of willful neglect trigger mandatory investigation and can lead to civil monetary penalties and corrective action plans. Each day a violation persists can count separately, multiplying exposure.

Aggravating and mitigating factors

  • OCR weighs harm, scope, duration, organization size, prior history, and the timeliness and completeness of remediation.
  • Demonstrated governance—documented risk analysis, training, BA oversight, and testing—mitigates penalties.

Readiness for OCR audits and HIPAA enforcement actions

  • Maintain current policies, risk analyses, security risk management plans, training records, incident logs, and BAA inventory for OCR audits.
  • Practice “audit readiness” with tabletop exercises, evidence checklists, and executive briefings.

Breach Notification Requirements

Presumption of breach and risk assessment

Any impermissible use or disclosure of unsecured PHI is presumed a breach unless you document, via a risk assessment, a low probability that PHI was compromised. Evaluate the nature/extent of PHI, the unauthorized recipient, whether PHI was actually acquired or viewed, and the degree of mitigation.

Timelines and recipients

  • Notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery.
  • Notify HHS: within 60 days if 500+ individuals are affected; for fewer than 500, report annually.
  • Notify prominent media when a breach affects more than 500 residents of a state or jurisdiction.

Content of notices and documentation

  • Explain what happened, what information was involved, steps individuals should take, what you are doing to mitigate/avoid future harm, and contact methods.
  • Retain breach documentation, your risk assessment, and evidence of notifications under the Breach Notification Rule.

Encryption and safe harbor

Incidents involving PHI that is encrypted or otherwise rendered unusable, unreadable, or indecipherable generally fall outside breach notification obligations, provided your method meets recognized standards.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Direct Liability for Business Associates

Who is a business associate?

A business associate (BA) creates, receives, maintains, or transmits PHI on your behalf (for example, cloud hosting, billing, analytics, and e-prescribing vendors). Subcontractors handling PHI are treated as BAs.

Direct obligations and BAAs

  • BAs must comply with the Security Rule, certain Privacy Rule provisions, and the Breach Notification Rule—independently of covered entities.
  • BAAs must define permitted uses/disclosures, safeguard requirements, breach reporting, and flow-down duties to subcontractors.
  • BAs face HIPAA enforcement actions, including penalties, for their own violations.

What you should do

  • Inventory all vendors and subcontractors handling PHI/ePHI; execute and regularly refresh BAAs.
  • Require third-party risk assessments, security attestations, and right-to-audit clauses.

Enhanced Patient Rights

Right of access to ePHI

  • Provide individuals with timely access to their PHI, including electronic copies of ePHI in the requested form and format when readily producible.
  • Allow individuals to direct their PHI to a designated third party at their written request.

Restrictions and confidential communications

  • Honor an individual’s request to restrict disclosure to a health plan for a specific service when the individual pays in full out of pocket.
  • Accommodate reasonable requests for communications at alternative locations or via alternative means.

Transparency and choice

  • Offer opt-out for fundraising communications and honor marketing/authorization preferences.

Updated Privacy Notices

Notice of Privacy Practices (NPP) content

  • Explain uses/disclosures requiring authorization (marketing, sale of PHI) and the right to opt out of fundraising.
  • Describe the duty to notify affected individuals of a breach.
  • Inform individuals of their right to restrict disclosures to health plans for self-paid services and their right to access ePHI.

Distribution and maintenance

  • Post the current NPP prominently at service locations and on your website; provide copies upon request and at first service delivery.
  • Update the NPP when material changes occur and maintain prior versions as required.

Conclusion

The HIPAA Omnibus Rule elevates privacy controls, mandates risk-based safeguards for ePHI, expands patient rights, and empowers OCR with stronger enforcement. By hardening security, tightening BA oversight, perfecting breach response, and modernizing your NPP, you reduce risk, improve compliance, and earn patient trust.

FAQs

What HIPAA rule incorporated privacy and security provisions?

The HIPAA Omnibus Rule integrated and strengthened existing Privacy, Security, Breach Notification, and Enforcement provisions, aligning them and extending key requirements—especially for vendors handling PHI/ePHI.

How does the Omnibus Rule affect business associates?

Business associates and their subcontractors are directly liable for complying with the Security Rule, certain Privacy Rule provisions, and the Breach Notification Rule. They must sign and follow Business Associate Agreements (BAA) and can face independent HIPAA enforcement actions.

What are the penalty tiers under HIPAA enforcement?

There are four tiers based on the level of culpability: no knowledge, reasonable cause, willful neglect corrected, and willful neglect not corrected. Penalties increase by tier, with per‑violation amounts and annual caps that can reach the highest levels for uncorrected willful neglect.

What are the breach notification obligations?

You must assess any impermissible use or disclosure of unsecured PHI, and if a breach occurred, notify affected individuals without unreasonable delay (no later than 60 days), notify HHS within required timeframes, and notify the media when 500+ residents are impacted. Notices must explain what happened, what data was involved, recommended protective steps, and your remediation actions.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles