HIPAA Privacy Rules That Apply to Self-Insured Employer Health Plans
Self-insured employer plans carry direct HIPAA obligations that vendors cannot assume.

Self-insured employer health plans have direct HIPAA privacy, security, and documentation obligations that cannot be transferred to a third-party administrator. Automated benefits compliance monitoring across a multi-jurisdiction workforce can help track regulatory changes, notices, vendor agreements, and review deadlines, but it does not replace the plan’s accountability. Effective compliance combines that monitoring with clear ownership of protected health information and the decisions governing its use.
Why employers who sponsor self-insured plans are HIPAA covered entities — and why most don't realize it
A tech company that has never considered itself part of healthcare can nevertheless operate a HIPAA covered entity through its self-insured health plan. The distinction is between the business and the plan. The group health plan is the covered entity. When the employer receives protected health information, or PHI, to administer that plan, HIPAA governs those activities under 45 CFR 164.504(f).
That access depends on a formal separation of functions. The employer must amend plan documents, certify that it will safeguard PHI, and establish a firewall between plan administration and employment decisions. Without those steps, it may receive only enrollment information or de-identified summary data. The information’s purpose also determines its status. A drug test result or FMLA medical certification collected by the employer for employment purposes is not PHI, while the same type of information flowing through the plan is.
Self-insured dental, vision, Healthcare FSAs, and HRAs are subject to the same framework, and level-funded plans are typically treated as self-funded for HIPAA compliance purposes. One narrow exemption applies to plans with fewer than 50 participants administered solely by the employer. Once a vendor performs plan administration involving PHI, that exemption no longer applies.
Three rules that apply simultaneously once a plan qualifies as a covered entity
Covered-entity status activates three parallel compliance tracks. The Privacy Rule governs permitted uses and disclosures of PHI, the minimum-necessary standard, and participants’ rights to access, amendment, accounting of disclosures, and restriction requests. The Security Rule applies specifically to electronic PHI, or ePHI, and requires administrative, technical, and physical safeguards, risk analysis, and ongoing risk management. The Breach Notification Rule governs investigation and notice when unsecured PHI is impermissibly used or disclosed. Such an event is presumed to be a breach unless the plan demonstrates a low probability of compromise.
These rules overlap without substituting for one another. A plan needs controls over whether information may be disclosed, safeguards for the systems holding it, and procedures for responding when disclosure goes wrong. Most private-sector employers must also follow ERISA rules for how they run their plans. The Department of Labor has made clear that ERISA’s duties of prudence and loyalty extend to cybersecurity risk, including vendor selection, monitoring, and incident response.
The resulting exposure is not limited to HIPAA. HIPAA breach penalties can reach substantial per-violation amounts up to a calendar-year maximum, while ERISA penalties for missing documents accrue per day per participant. COBRA penalties add up each day for each qualified beneficiary. These different penalties make it important to oversee all aspects of the plan, even when a vendor handles day-to-day claims administration.
The April 2026 enforcement action that confirmed self-funded plans face direct, independent liability
The Office for Civil Rights announced an enforcement action against a self-funded employee benefit plan on April 23, 2026, following a ransomware attack that compromised its ePHI. OCR found impermissible PHI disclosure and an inadequate risk analysis. The employer/sponsor faced a significant payment and a Corrective Action Plan, or CAP. The employer’s business was entirely outside the healthcare industry.
The CAP required a comprehensive analysis of risks and vulnerabilities to the confidentiality, integrity, and availability of the plan’s ePHI. It separately required a complete inventory of facilities, electronic equipment, data systems, and applications containing or storing ePHI for incorporation into that analysis. The responsibility rested with the plan itself. Delegating compliance work to a third-party administrator, or TPA, did not transfer the plan’s covered-entity obligations or create a regulatory exception for its sponsor.
The eight operational obligations a self-insured plan sponsor must own directly
The first obligation is PHI mapping. The sponsor must document where PHI enters the organization, where it flows, and how it is used. Common records include claims files, eligibility data, explanations of benefits, case management records, and appeals. This establishes the scope of the compliance program. The exemption analysis should also be documented, including whether the small-plan exemption or any relevant excepted-benefit provisions apply, even when the conclusion is that no exemption is available.
The second obligation is independent written Privacy and Security policies when the employer receives PHI from the plan. The TPA’s policies are not a substitute. The sponsor’s policies must cover minimum-necessary standards, permitted uses and disclosures, and the firewall separating plan administration from employment decisions. Written sanctions must address noncompliance, and documentation must be retained for at least six years.
The third obligation is a designated HIPAA Compliance Officer with named responsibility. Ownership cannot remain implicit within the HR function. Depending on organization size, the role may be combined with Privacy Officer or Security Officer responsibilities. Participants must be able to reach the responsible person with privacy complaints.
The fourth obligation is the Notice of Privacy Practices, or NPP. The plan must maintain and distribute it at initial enrollment and upon material revision. Participants also need a notice at least every three years explaining that the NPP is available and how to obtain it. A benefits website creates another publication obligation. If the plan has one, the NPP must be posted there.
The fifth obligation is to sign Business Associate Agreements, or BAAs, before vendors handle PHI on the plan’s behalf. Relevant vendors include TPAs, pharmacy benefit managers, COBRA administrators, wellness and disease management firms, mail-house and print vendors, and cloud hosting providers. A stop-loss carrier’s status depends on how data actually flows to and from it, regardless of what it is called. BAAs must address permitted uses and disclosures, safeguards, breach reporting timelines, subcontractor flow-down, and termination rights, with annual review and documented follow-up on gaps.
The sixth obligation is to put breach notification procedures in writing. An impermissible use or disclosure of unsecured PHI is presumed to be a breach unless a four-factor risk assessment demonstrates a low probability of compromise. People affected by a breach must receive notice within 60 days of its discovery. Larger breaches require notice to HHS OCR within the applicable discovery-based period, while smaller breaches are logged and reported annually.
The seventh obligation is to make the needed amendments to the plan documents. For ERISA plans, the documents must address both ERISA governance and HIPAA privacy obligations. When the employer accesses PHI for plan administration, the documents must limit its use and disclosure and establish the required safeguards and certifications.
The eighth obligation is Security Rule compliance supported by comprehensive risk analysis. The assessment should identify threats, vulnerabilities, likelihood, and impact, followed by a prioritized risk management plan reviewed at least annually and after significant system, vendor, or migration changes. Administrative measures include role-based access, workforce training with phishing awareness, and contingency and disaster recovery planning. Technical and physical measures include unique user IDs, multi-factor authentication, automatic logoff, centralized audit logging, encrypted transmission, facility and workstation controls, and secure disposal and media re-use controls.
The February 16, 2026 NPP deadline and what it required self-insured plans to change
The February 16, 2026 NPP deadline required changes in two directions. Plans needed new language addressing substance use disorder treatment records, but some also needed to remove or revise reproductive-health language they had previously added. Adding text alone was not necessarily sufficient. The notice had to describe the law accurately, including provisions no longer in force.
HHS issued final regulations on February 16, 2024, aligning the federal confidentiality framework for substance use disorder records under 42 C.F.R. Part 2 with HIPAA. Those regulations took effect April 16, 2024, and plans had to comply by February 16, 2026. Group health plans can receive protected records through claims appeals, utilization management, care coordination, behavioral health carve-outs, EAPs, and case management. Special restrictions on use and redisclosure may follow those records after lawful disclosure to a HIPAA covered entity.
Self-insured sponsors, including sponsors of Medical FSAs and HRAs, must therefore meet the NPP obligation, while fully insured group health plans generally do not have to meet it. Purl v. HHS, decided June 18, 2025, made clear that covered entities do not have to put the now-vacated reproductive-health Privacy Rule provisions in place. Reproductive-health-specific descriptions already added to an NPP must be removed or revised to reflect current law. A notice that gets the law wrong can lead to regulatory action, problems during audits, complaints from participants, and lawsuits.
The proposed Security Rule overhaul and what self-insured plans should do before it is finalized
The proposed Security Rule overhaul is not current law. As of the available source material, OCR has not issued a final rule, and final action has been postponed until 2027. OMB’s Unified Agenda targets July 2027 as a planning estimate. The requirements and timing could still change, face further delay, or be withdrawn.
The proposal would require encryption of ePHI at rest and in transit, multi-factor authentication for all systems accessing ePHI, 72-hour incident reporting, annual penetration testing, and enhanced business associate oversight. Its largest structural change concerns implementation specifications. The distinction between “required” and “addressable” specifications would disappear, making safeguards mandatory with limited exceptions. That would reduce the discretion plans currently exercise over addressable safeguards.
The practical recommendation is to use the proposal as a gap-assessment framework before finalization. Sponsors should compare current safeguard choices with full implementation and identify where remediation would be needed if the proposal proceeds. Early work can reduce future remediation costs and strengthen audit readiness. The complete ePHI inventory and comprehensive risk analysis required by the April 2026 CAP already align with the proposal’s direction. Completing that work supports present compliance without treating proposed requirements as enforceable obligations.
How can an AI-native benefits partner keep ongoing HIPAA compliance up to date automatically?
HIPAA compliance requires recurring work throughout the year, including renewal season. PHI mapping, risk analysis, BAA review, NPP revisions, plan document amendments, and breach procedures all need continuing ownership. For employers with workers across states and countries, automated alerts about the rules in each jurisdiction can help with that work so HR does not have to track every change by hand. This is a monitoring capability. HIPAA obligations remain attached to the plan and its administration.
The commissions traditional brokers earn favor renewal over renegotiating each year and reviewing compliance, so gaps in the documents can go unfilled from one renewal to the next. PEOs bundle compliance support through co-employment, but add per-employee costs and constrain plan design flexibility. An AI-native benefits brokerage can instead add compliance monitoring, automated regulatory alerts, and a dedicated consultant to the HRIS the employer already uses.
Services can be compared on how they help keep the NPP up to date, maintain BAA inventories, schedule risk analysis, and provide alerts for the jurisdictions where employees work. An always-available employee concierge can provide real-time answers about benefits and privacy rights, supporting the access, amendment, and restriction-request obligations described by the Privacy Rule. Answers alone do not discharge those obligations. The plan must still honor participants’ rights within the applicable timeframes.
For tech companies leaving a PEO, this service model addresses a defined gap in the transition. The alternative needs compliance depth without co-employment lock-in or per-employee fees. Automation can reduce the tracking burden, while a dedicated consultant supports the ongoing compliance work. The employer’s task is still to own the safeguards, documents, and decisions that its self-insured plan requires.
Sources
- Important Compliance Deadline for Employer Sponsors of Self-Funded Health Plans: Update and Distribute HIPAA Notice of Privacy Practices by February 16, 2026 - Miller Johnson
- OCR Announces HIPAA Enforcement Against Self-Funded Employee Benefit Plan
- HIPAA Notice of Privacy Practices Refresh for Self-Insured Group Health Plans: What to Change Before February 16, 2026
- Are Small Health Care Plans Exempt From HIPAA Privacy and Security Rules?
- 9 Things to Consider for Self-Insured Health Plan HIPAA Compliance


