Skip to content
Back to CMS Watch
FCA SettlementOctober 2, 2026·4 min read

Independence Blue Cross to pay $22.5M; DOJ alleges one-way MA chart reviews

On September 30, 2026, DOJ announced Independence Blue Cross agreed to pay $22.5 million to resolve False Claims Act allegations that its Medicare Advantage chart reviews added supported diagnoses but failed to withdraw unsupported codes already reported to CMS. That one-way pattern is the compliance line every risk-adjustment desk has to draw.

FCA SettlementMedicare Advantagerisk adjustmentchart reviewDOJ
HCC Buddy

By the HCC Buddy Coding Team

Published October 2, 2026

Wooden gavel beside stacked manila chart folders on a desk, signaling a Medicare Advantage risk-adjustment False Claims Act settlement
Independence Blue Cross agreed to pay $22.5 million to resolve DOJ False Claims Act allegations over Medicare Advantage diagnosis coding for payment years 2017 to 2021. — Illustration: HCC Buddy

Key Takeaways

  • →On September 30, 2026, the Justice Department announced Independence Blue Cross agreed to pay $22.5 million to resolve False Claims Act allegations involving Medicare Advantage diagnosis coding.
  • →DOJ alleges IBX submitted inaccurate diagnosis data to CMS, knowingly failed to withdraw unsupported codes and repay CMS, and falsely certified that the data was accurate and truthful.
  • →For payment years 2017 through 2021, the United States contends IBX ran a nurse chart-review program that added supported diagnoses to CMS submissions but did not delete previously reported codes the same reviews failed to substantiate.
  • →The settlement resolves a qui tam suit, United States ex rel. Crawford v. Independence Blue Cross, No. 20-cv-5818 (E.D. Pa.); the whistleblower, a former IBX employee, is to receive a $3,825,000 share.
  • →DOJ states the claims resolved by the settlement are allegations only and there has been no determination of liability.

On September 30, 2026, the Justice Department announced that Independence Blue Cross (IBX), a Pennsylvania insurer, agreed to pay $22.5 million to resolve False Claims Act allegations that it failed to withdraw inaccurate Medicare Advantage diagnosis codes and improperly retained the resulting overpayments. DOJ's description centers on a chart-review workflow: codes went up when reviews supported them, and stayed on file when reviews did not.

What DOJ announced

According to the DOJ Office of Public Affairs release, IBX agreed to pay $22.5 million to resolve allegations that it violated the False Claims Act by failing to withdraw inaccurate and untruthful diagnosis codes for its Medicare Advantage enrollees. The United States alleges IBX submitted inaccurate patient diagnosis data to CMS that inflated risk-adjustment payments, knowingly failed to withdraw that data and repay CMS, and falsely certified in writing that the data was accurate and truthful.

DOJ states the claims resolved by the settlement are allegations only and there has been no determination of liability.

ItemDOJ release
DefendantIndependence Blue Cross (Pennsylvania)
Amount$22.5 million
ProgramMedicare Advantage (Part C) risk adjustment
Payment years named2017 through 2021
Case*United States ex rel. Crawford v. Independence Blue Cross*, No. 20-cv-5818 (E.D. Pa.)
Relator share$3,825,000
Liability findingAllegations only; no determination of liability

The coding pattern DOJ describes

For payment years 2017 through 2021, the United States contends IBX operated a "chart review" program in which nurse reviewers reviewed medical records and identified medical conditions the charts supported. IBX relied on those results to submit additional diagnosis codes to CMS for more payment.

The government also contends that the same chart reviews did not substantiate some diagnosis codes IBX had previously reported to CMS, and that IBX did not delete or withdraw those codes. Deleting them would have required reimbursing CMS. In DOJ's words, IBX allegedly used chart-review results to find places to seek additional payments while ignoring the same results when they showed IBX was overpaid.

Desk shorthand for that asymmetry is a one-way chart review: add when supported, never delete when not. Two-way review is the compliance opposite: if the record does not support a previously submitted diagnosis, the code comes off.

Why this lands on a risk-adjustment coder's desk

This is not a provider-query case and it is not a named-HCC hit list. The DOJ release does not name specific ICD-10-CM codes or CMS-HCC categories. The operational lesson is the direction of the review.

If your shop runs retrospective chart reviews or vendor chart reviews for Medicare Advantage risk adjustment, the government's theory here is that using review findings only to add codes, while leaving unsupported prior codes in place, can become a False Claims Act problem. The Monday-morning check is simple: when a chart review cannot substantiate a diagnosis already on the MAO's submission file, treat deletion and repayment rules as part of the same workflow as the add.

Use MEAT criteria as the documentation filter before any add stays on a claim, and keep the encoder and ICD-10-to-HCC tools for confirming what the current model actually maps when a diagnosis is legitimately supported.

How the case surfaced

The settlement resolves a lawsuit filed under the False Claims Act's qui tam whistleblower provisions. The case is captioned *United States ex rel. Crawford v. Independence Blue Cross*, No. 20-cv-5818, in the U.S. District Court for the Eastern District of Pennsylvania. DOJ says the whistleblower, a former IBX employee, is to receive a $3,825,000 share of the settlement amount.

The matter was handled by the Justice Department's Civil Division, Commercial Litigation Branch, Fraud Section, and the U.S. Attorney's Office for the Eastern District of Pennsylvania, with HHS-OIG.

What this does not change on the claim

The release does not rewrite ICD-10-CM indexing, does not change CMS-HCC V28 mappings, and does not announce a new RADV schedule. It is an enforcement resolution about alleged diagnosis-data integrity and the duty to withdraw unsupported codes once a plan's own review finds them unsupported.

Related HCC Buddy coverage on MA diagnosis enforcement includes the Villages Health $541.5M settlement coder lessons and the Monogram Health $2.4M HCC coding FCA. Those stories name different defendants and different alleged patterns; do not treat IBX as a rewrite of either.

Where coders should tighten this week

Pull recent retrospective chart-review batches and confirm the shop has a documented path for deletes, not only adds. If a nurse or coder review cannot substantiate a previously submitted diagnosis, escalate through your compliance process for withdrawal and any required repayment steps under your MAO's rules. Do not invent codes or HCCs from this release; the government did not publish a condition list here.

What coders should do now

  1. 1Audit your last retrospective chart-review cycle for one-way behavior: every add path should have a matching delete path when the record does not support a previously submitted diagnosis.
  2. 2Before any chart-review add reaches the MAO submission file, confirm provider-authored support in the encounter using [MEAT criteria](/meat-criteria), not a problem-list carry-forward alone.
  3. 3If a review finds a prior diagnosis unsupported, escalate for withdrawal under your plan's CMS data-correction process rather than leaving the code on file.
  4. 4Do not build an HCC hit list from this settlement. DOJ did not name specific codes or HCCs; focus on the two-way review workflow instead.
  5. 5Brief CDI and vendor chart-review partners that using review findings only to increase risk scores, while ignoring findings that reduce them, is the pattern DOJ described in this case.

Frequently Asked Questions

What did Independence Blue Cross agree to pay in the September 2026 FCA settlement?

According to the Justice Department's September 30, 2026 announcement, Independence Blue Cross agreed to pay $22.5 million to resolve False Claims Act allegations involving Medicare Advantage diagnosis coding. DOJ states the claims resolved are allegations only and there has been no determination of liability.

What coding pattern did DOJ allege in the Independence Blue Cross case?

For payment years 2017 through 2021, the United States contends IBX ran a nurse chart-review program that submitted additional diagnosis codes when reviews supported them, but did not delete previously reported codes that the same reviews failed to substantiate. DOJ alleges IBX used review results to seek more payment while ignoring results that showed overpayment.

Did DOJ name specific HCC or ICD-10 codes in the IBX settlement?

No. The September 30, 2026 DOJ press release does not list specific ICD-10-CM codes or CMS-HCC categories. The allegations focus on inaccurate diagnosis data, failure to withdraw unsupported codes, and false certification of accuracy, not a published code roster.

Is the Independence Blue Cross settlement an admission of liability?

No. The DOJ release states that the claims resolved by the settlement are allegations only and there has been no determination of liability. Write and brief the case as unresolved allegations settled for a payment, not as adjudicated findings.

Who brought the Independence Blue Cross Medicare Advantage FCA case?

The settlement resolves a qui tam lawsuit captioned United States ex rel. Crawford v. Independence Blue Cross, No. 20-cv-5818, in the Eastern District of Pennsylvania. DOJ says the whistleblower, a former IBX employee, is to receive a $3,825,000 share.

Related topics:FCA SettlementMedicare Advantagerisk adjustmentchart reviewDOJ
HCC Buddy

HCC Buddy Coding Team

Editorial

Every HCC Buddy news article is checked against the current CMS-HCC model and the active FY ICD-10-CM tabular release before it publishes.

Get CMS Updates in Your Inbox

RADV news, model changes, and coding guidance — within days of CMS publishing, not quarters.