The Health Insurance Portability and Accountability Act of 1996, a federal law that protects the privacy and security of individually identifiable health information and gives employees the right to continue health coverage when changing jobs.
Key Takeaways
HIPAA is one of the most misunderstood laws in HR. Most people think it prevents employers from asking about employee health. It doesn't. HIPAA regulates how covered entities, which are health plans, healthcare providers, and healthcare clearinghouses, handle protected health information. An employer isn't a covered entity simply because it employs people. However, an employer that sponsors a group health plan does become subject to HIPAA in that specific capacity. The health plan itself is the covered entity, and the employer acting as plan sponsor and administrator has obligations around how it handles PHI received from the plan. This is where HR teams get caught. When a benefits manager receives medical claims data, enrollment information with diagnosis codes, or disability documentation from the group health plan, that information is PHI subject to HIPAA. The same benefits manager can ask an employee directly about their medical condition for ADA accommodation purposes without triggering HIPAA, because the employer isn't acting as a covered entity in that interaction. The distinction matters enormously for compliance.
The Privacy Rule sets limits on who can see protected health information and under what circumstances.
Protected Health Information is any individually identifiable health information that's created, received, maintained, or transmitted by a covered entity. It includes diagnosis codes, treatment records, prescription information, lab results, health plan enrollment data, claims data, and any information that connects health data to a specific person. PHI covers 18 identifiers including names, dates, phone numbers, email addresses, Social Security numbers, and medical record numbers. De-identified data (with all 18 identifiers removed) is not PHI and isn't subject to HIPAA.
Employers most commonly encounter HIPAA when administering self-funded health plans, processing health plan enrollment, handling health plan claims appeals, receiving explanation of benefits (EOB) documents, managing Health Savings Account (HSA) or Flexible Spending Account (FSA) claims, or working with stop-loss insurance carriers. Information obtained outside the health plan context, such as sick leave requests, doctor's notes for FMLA, ADA accommodation requests, or workers' comp claims, generally isn't subject to HIPAA. However, it may be protected under the ADA, state privacy laws, or other regulations.
When accessing PHI for plan administration, employers must limit access to the minimum amount of information necessary to accomplish the intended purpose. A benefits manager processing a dental claim doesn't need to see the employee's mental health records. HR staff not involved in plan administration shouldn't have access to any PHI. This requires role-based access controls, policies defining who can access what, and training on appropriate use.
The Security Rule applies specifically to electronic PHI (ePHI) and requires three types of safeguards.
Risk analysis: identify where ePHI lives, who accesses it, and what threatens it. This isn't a one-time exercise. It must be ongoing. Designate a security official responsible for developing and implementing security policies. Implement workforce training on HIPAA security, with refresher training at least annually. Develop and test contingency plans for data backup, disaster recovery, and emergency mode operations. Sanction policies: employees who violate security policies must face consequences.
Control physical access to facilities where ePHI is stored or accessed. This includes locked server rooms, badge access to areas where PHI is processed, workstation security (auto-lock, privacy screens), and policies for removing ePHI from the facility (encrypted laptops, secure remote access). Device and media controls govern how hardware and electronic media containing ePHI are disposed of, reused, or moved within the organization.
Access controls: unique user IDs, automatic logoff, encryption of ePHI at rest and in transit. Audit controls: hardware, software, and procedural mechanisms to record and examine activity in systems containing ePHI. Integrity controls: mechanisms to protect ePHI from improper alteration or destruction. Transmission security: encrypt ePHI when transmitted over electronic networks (email, file transfers, API connections). The Security Rule is technology-neutral: it doesn't mandate specific technologies but requires "reasonable and appropriate" safeguards based on the organization's size, complexity, and risk environment.
When a breach of unsecured PHI occurs, HIPAA requires notification to affected individuals, HHS, and in some cases, the media.
A breach is the acquisition, access, use, or disclosure of PHI in a manner not permitted by the Privacy Rule that compromises the security or privacy of the information. Not every security incident is a breach. The covered entity must conduct a risk assessment considering four factors: the nature and extent of PHI involved, who accessed it, whether PHI was actually acquired or viewed, and what mitigation steps were taken. There are three exceptions: unintentional access by an authorized person acting in good faith, inadvertent disclosure between authorized persons within the same organization, and disclosures where the recipient couldn't reasonably retain the information.
Individual notice: written notification to each affected person within 60 days of discovering the breach. HHS notification: breaches affecting 500+ individuals must be reported to HHS within 60 days. Breaches affecting fewer than 500 individuals can be reported annually within 60 days of the end of the calendar year. Media notification: breaches affecting 500+ individuals in a single state or jurisdiction require notification to prominent media outlets in that area. HHS maintains a public "Wall of Shame" listing all breaches affecting 500+ individuals. As of 2024, it lists over 6,000 reported breaches.
HR teams and employers face HIPAA risk in several everyday scenarios.
A benefits manager tells a department supervisor that an employee's health plan claims show mental health treatment. A payroll specialist mentions an employee's prescription drug costs at lunch. An HR director shares disability claim details with a manager to explain an employee's absence. All of these violate the Privacy Rule's minimum necessary standard and use/disclosure restrictions. PHI from the health plan can only be used for plan administration, not employment decisions.
Storing enrollment spreadsheets with SSNs and diagnosis codes on unencrypted laptops. Emailing claims data without encryption. Leaving benefits paperwork on desks in open offices. Sharing HRIS login credentials among HR staff. Using a shared email inbox for health plan correspondence without access controls. The most common breach reported to HHS involves email (phishing, misdirected emails), followed by network server incidents and stolen/lost devices.
Any vendor that creates, receives, maintains, or transmits PHI on behalf of the covered entity (the health plan) must sign a Business Associate Agreement (BAA). This includes TPAs, PBMs, wellness program vendors, benefits brokers who access claims data, HRIS vendors storing PHI, IT companies with access to systems containing ePHI, and cloud storage providers. Operating without a BAA is itself a HIPAA violation, regardless of whether a breach occurs.
The HHS Office for Civil Rights (OCR) enforces HIPAA through investigations, corrective action plans, and financial penalties.
| Tier | Knowledge Level | Penalty Per Violation | Annual Cap |
|---|---|---|---|
| Tier 1 | Didn't know and couldn't have known | $141 to $71,162 | $2,134,831 |
| Tier 2 | Reasonable cause, not willful neglect | $1,424 to $71,162 | $2,134,831 |
| Tier 3 | Willful neglect, corrected within 30 days | $14,232 to $71,162 | $2,134,831 |
| Tier 4 | Willful neglect, not corrected | $71,162 to $2,134,831 | $2,134,831 |
HIPAA doesn't exist in isolation. HR teams must consider how it interacts with other federal and state privacy protections.
| Law | What It Covers | How It Relates to HIPAA |
|---|---|---|
| ADA | Disability-related medical information in employment context | ADA restricts employer use of medical information independently of HIPAA. An employer can violate the ADA's confidentiality rules without triggering HIPAA |
| FMLA | Medical certifications for leave | FMLA medical certifications aren't PHI if obtained directly from the employee, not from the health plan |
| GINA | Genetic information in employment and health insurance | GINA prohibits health plans from using genetic information for underwriting. HIPAA Privacy Rule also restricts genetic information disclosure |
| State laws | Varying state health privacy protections | HIPAA sets a federal floor. States can impose stricter protections. California's CCPA/CPRA, for example, adds consumer health data rights beyond HIPAA |
These steps cover the most critical HIPAA obligations for employers that sponsor group health plans.
Data showing the scale of HIPAA enforcement and the growing frequency of healthcare data breaches.