The 2026 National Health Care Fraud Takedown named home health as a target sector. The enforcement model has changed.

On June 23, the Justice Department announced the 2026 National Health Care Fraud Takedown: 455 defendants charged — 90 of them physicians and other licensed medical professionals — in connection with more than $6.5 billion in alleged false claims spanning 56 federal districts and 45 states and territories. All 50 state Medicaid Fraud Control Units participated, the most in Takedown history. Simultaneously, CMS suspended 1,079 providers and revoked billing privileges for 1,403 others as part of the same coordinated action.

Home health is explicitly named as one of the high-risk service lines the Takedown targeted, alongside behavioral health, personal care, and adult day care. The primary fraud pattern in those sectors: billing for services that were never rendered.

The enforcement model is materially different now

The 2026 Takedown is anchored to new enforcement infrastructure. The DOJ's Health Care Fraud Unit is operating a multi-agency Data Fusion Center — staffed jointly by DOJ's Data Analytics Team, HHS-OIG, the FBI, and other agencies — that combines Medicare and Medicaid claims data with financial transaction analysis in a single review environment. A Financial Intelligence Review Team within that infrastructure maps billing patterns to payment flows, identifying mismatches that don't surface in traditional claims review alone.

The practical implication: billing anomalies are now caught by automated systems running against the full national claims dataset, not by a post-audit triggered by a whistleblower or random sampling. The 295 Medicaid-related defendants charged — accounting for $518 million in alleged false claims — represent the largest Medicaid fraud enforcement action in Takedown history. The data pipeline feeds federal and state enforcement simultaneously.

Ohio is the state-level illustration of the same model

Ohio's June enforcement timeline shows how quickly state-level action follows federal data-sharing. Using newly deployed data analytics tools authorized by Governor DeWine's Executive Order 2026-02D, Ohio Medicaid announced on June 4 that it had suspended payments to 49 home health providers whose billing patterns flagged as high-risk. On June 16, eight additional providers and associated workers were suspended in connection with the same enforcement action — 57 suspensions in total, out of 87 providers identified for further review. The enforcement package also includes a six-month moratorium on new Medicaid enrollments for high-risk provider categories, more frequent revalidation, and accelerated GPS-based EVV implementation for covered services.

Ohio acted faster because the executive order authorization was already in place. Other states in the MFCU network — all 50 of which participated in the June 23 Takedown — are now working from the same data-sharing pipeline. Ohio is a leading indicator of what follows in other states, not an exception.

What the flagged billing patterns look like

Across Takedown enforcement communications, the data systems are flagging specific pattern types that are directly relevant to home health operations:

• Service dates during a patient's facility admission. A skilled nursing or aide visit billed for a date the patient was in an acute hospital or SNF is the most tractable cross-reference — claims data and admission records already overlap in CMS databases. This was the pattern that drove the Minnesota $3.8M Medicaid case earlier this year.
• Visit frequency outliers relative to HIPPS group. High visit counts on low-complexity HHRGs, or LUPA-threshold clustering, surface in outlier analysis as billing-pattern-driven rather than clinically driven.
• Missing EVV records alongside submitted claims. Billed visits without a corresponding GPS-verified EVV record are a data gap the enforcement infrastructure identifies before the claim settles — Ohio's enforcement package explicitly accelerates EVV to close this audit layer.
• Financial flows from provider accounts to referral sources. The Financial Intelligence Review Team maps payment transaction data alongside claims. CashApp, Venmo, and check payments to individuals who also refer patients don't disappear from the financial record.

What an agency should do now

1. Run a hospitalization overlap check on the trailing 90 days. Pull your billed service dates against any facility admission records you have. A visit billed on a day a patient was admitted to an acute facility is the most direct trigger for the data cross-reference the enforcement systems run.
2. Review your EVV exception rate by discipline. Therapy disciplines typically post lower EVV capture rates than aide visits. Every unverified visit billed is a gap the data pipeline will find before your AR aging review does.
3. Audit financial flows from your agency accounts. Any payment — from any account — to an individual who also refers patients needs documented Anti-Kickback safe-harbor analysis. The Financial Intelligence review maps transactions to claims; your documentation is the only counterweight.
4. Know your billing-pattern outliers against your HIPPS profile. Your billing data is the same dataset the Data Fusion Center is reviewing. If your visit frequency is an outlier relative to your case mix, you need to identify it before a data query does — not after a suspension letter arrives.

What we built for this

Carelytic's billing pipeline cross-references every claim date against HETS eligibility status and flags visits where the patient's Medicare or Medicaid coverage was suspended, terminated, or where the claim date falls within a known facility admission window. The EVV module ties GPS check-in data to each visit record — unverified visits surface in the exception report before submission, not after a suspension notice. Every record access and modification carries an immutable timestamp and responsible user ID. In an enforcement environment where the government's data systems are running the same cross-references against the full national claims dataset, the audit trail is not a reporting feature. It is what the agency presents when documentation is requested.