A physician's office in South Texas billed Medicare for 23 hours of services in a single day. Not once — for months. When investigators unraveled the scheme, they didn't just find fraud. They found unsecured patient records used to fabricate claims, PHI shared with unauthorized billing staff, and zero workforce training on either fraud prevention or HIPAA. That's the intersection most compliance officers miss: FWA in healthcare doesn't just drain money. It exposes protected health information in ways that trigger federal enforcement from multiple directions at once.

If you run compliance at a covered entity, a health plan, or a billing company, this overlap is your problem. Here's how to understand it, spot it, and build defenses that actually work.

What FWA in Healthcare Actually Means

FWA stands for fraud, waste, and abuse. These three terms get lumped together so often that people treat them as interchangeable. They aren't.

Fraud is intentional deception for unauthorized benefit. Think fake diagnoses, phantom billing, or kickback schemes. Waste is overutilization of services or spending that doesn't result in value — not necessarily intentional, but costly. Abuse falls in between: practices inconsistent with accepted standards that result in unnecessary costs, but without the clear intent required for fraud.

The Department of Health and Human Services estimates that healthcare fraud alone costs the U.S. tens of billions of dollars annually. HHS and its Office of Inspector General (OIG) maintain an active work plan targeting these schemes across Medicare, Medicaid, and private payers.

The HIPAA Connection Most People Overlook

Here's what I've seen over and over: organizations treat FWA compliance and HIPAA compliance as completely separate tracks. Different training modules. Different staff. Different committees. That's a mistake.

Fraud schemes almost always involve PHI. To submit a false claim, someone needs a patient's name, date of birth, diagnosis codes, insurance information — all of which qualify as protected health information under HIPAA. When PHI gets misused to commit fraud, you don't just have an FWA problem. You have a potential HIPAA breach.

Consider this sequence: A billing clerk accesses ePHI they have no legitimate reason to view. They use that data to submit inflated claims. The access itself violates the HIPAA minimum necessary standard. The submission constitutes fraud. And if the organization never audited access logs, it also reflects a Security Rule failure.

OCR doesn't look the other way when fraud is the motive. Unauthorized access to PHI is unauthorized access, regardless of why it happened.

Real Enforcement That Proves the Point

In 2018, OCR settled with Anthem Inc. for $16 million following a breach that exposed the ePHI of nearly 79 million people. While that case centered on a cyberattack rather than internal fraud, the underlying lesson was the same: insufficient access controls and audit mechanisms left PHI vulnerable. Organizations that can't track who accesses what — and why — are sitting targets for both external attackers and internal bad actors committing FWA.

You can review OCR's enforcement actions and resolution agreements on the HHS breach resolution page.

The Five Warning Signs Your Organization Has an FWA Gap

In my experience, organizations with FWA problems share a common set of symptoms. Look for these:

  • No access audits. If you aren't reviewing who accesses PHI and correlating that against job duties, you're blind to both fraud and HIPAA violations.
  • Billing staff with unrestricted EHR access. The minimum necessary rule exists for a reason. If your coders can see clinical notes for patients they're not coding, that's a problem.
  • Workforce training that separates FWA from HIPAA. Your staff needs to understand how these two frameworks connect. Siloed training creates siloed thinking.
  • No anonymous reporting mechanism. The OIG has found repeatedly that tips are the number one way fraud gets detected. If your staff can't report concerns safely, you won't catch schemes early.
  • Outdated or missing compliance plans. CMS requires Medicare Advantage and Part D sponsors to have comprehensive FWA programs. If yours hasn't been updated recently, it probably doesn't reflect current risk.

How Do Fraud, Waste, and Abuse Relate to HIPAA?

FWA in healthcare relates to HIPAA in three direct ways. First, most fraud schemes require unauthorized use or disclosure of PHI, which violates the Privacy Rule. Second, weak access controls that allow FWA also violate the Security Rule's requirements for audit controls, access management, and workforce clearance procedures. Third, when fraud involves a breach of unsecured PHI, the Breach Notification Rule kicks in — meaning your organization must notify affected individuals, HHS, and potentially the media.

Put simply: if your FWA prevention program is weak, your HIPAA compliance program is also weak. They share the same infrastructure of access controls, audits, training, and accountability.

Building a Combined Defense That Actually Works

Start With Integrated Training

The single most effective step I recommend to clients is merging FWA and HIPAA workforce training. Not combining them into one bloated slide deck — integrating the concepts so staff understand the relationship. When a billing specialist learns about upcoding, they should simultaneously learn that accessing patient records without authorization to do it violates HIPAA.

Our HIPAA training catalog includes courses designed for covered entities and business associates that address this overlap directly. Training isn't a checkbox exercise. It's the foundation of a culture where staff recognize — and report — suspicious activity.

Implement Role-Based Access Controls

This is Security Rule 101, but I still walk into organizations where every employee has the same level of EHR access. Role-based access controls limit PHI exposure to what each person needs for their specific job function. This directly reduces both HIPAA risk and FWA opportunity.

If a front-desk scheduler can pull up a patient's full billing history and clinical notes, you've created a vulnerability that serves neither compliance framework.

Audit Relentlessly

Audit logs aren't just a HIPAA Security Rule requirement under 45 CFR § 164.312(b). They're your FWA early warning system. Regular audits of EHR access, billing patterns, and claims submissions can surface anomalies before they become full-blown fraud cases.

Look for patterns: unusual after-hours access, spikes in high-reimbursement codes, and staff accessing records of patients they don't serve. These red flags are cheap to detect and expensive to ignore.

Establish a Compliance Hotline

The OIG's guidance on compliance programs for individual and small group physician practices — still one of the most practical federal documents on the topic — recommends anonymous reporting mechanisms. Tips from employees, patients, and vendors remain the most common way fraud is initially detected.

You can find the OIG's compliance guidance at oig.hhs.gov/compliance/compliance-guidance.

The Cost of Getting This Wrong

FWA in healthcare doesn't just mean fines. It means exclusion from federal healthcare programs, criminal prosecution, civil monetary penalties, and — when HIPAA is implicated — OCR enforcement actions that carry their own six- and seven-figure settlements.

The False Claims Act allows qui tam lawsuits where whistleblowers share in recovered funds. That billing clerk you never trained? They might be the one filing the lawsuit. And when investigators come in, they won't just look at your billing practices. They'll look at your HIPAA compliance program, your access controls, your training records, and your incident response history.

Everything connects. Your defense has to connect, too.

What You Should Do This Week

Pull your last three months of EHR access logs and compare them against your current role-based access policies. If you don't have role-based access policies, that's your first action item.

Then review your workforce training records. Is every member of your staff — clinical, administrative, and executive — trained on both HIPAA and FWA? If you're running separate programs, or worse, running nothing at all, explore our comprehensive HIPAA training options designed for organizations that take compliance seriously.

FWA in healthcare isn't someone else's problem. It's a compliance risk that shares DNA with every HIPAA obligation you already have. The organizations that treat them as one integrated challenge are the ones that stay out of the headlines — and out of settlement negotiations.