A Defendable Supply Chain
A Defendable Supply ChainIQRP's Firewall Against False Claims Act Exposure
On August 26, DOJ settled with The Villages Health System for $541.5 million. Three Medicare Advantage plans, none of them named as defendants, are now the ones returning the money.
I have spent a decade on the payor side of managed care, and three and a half decades in medicine before that. What this settlement confirms is something IQRP was built around: risk adjustment accuracy is not only a documentation problem inside your own walls. It is a supply chain problem that runs through every provider group in your network.
The Exposure: Risk Adjustment Is a Supply Chain Problem
A health plan's RAF accuracy and Stars performance are only as sound as the weakest documentation practice inside the network feeding it codes. The Villages Health case shows what happens when that chain breaks. The provider group submitted diagnoses over four years, 2020 through 2024. The plans, Humana, UnitedHealthcare, and GuideWell, accepted them under contract, reported them to CMS, and are now the ones unwinding the submissions: deleting codes, restating risk scores, and returning funds under their own agreements with the government.
None of the three plans is alleged to have done anything wrong. That is the point. Contractual exposure does not require plan level misconduct. It only requires plan level acceptance of someone else's data, and every MA organization with a network of provider groups is carrying that same acceptance right now.
The Standard: What DOJ Just Defined as Defendable
DOJ described two categories of invalid codes in the settlement. Some lacked support in the medical record, a familiar documentation failure. The others rested on chart amendments that were not initiated by the rendering provider, not timely, or not approved by the rendering provider.
A chart amendment reads as defendable, or as exposure, based on three questions:
- Who initiated it — the treating clinician, or a retrospective review process acting on its own
- How long after the visit — a same-visit correction versus an addition months or years later
- Whether the treating clinician approved it — documented sign off, not assumed concurrence
A clinician correcting an incomplete note is ordinary medicine. A retrospective review process adding a diagnosis on its own initiative, without the treating provider's approval, is what DOJ put on the wrong side of the line. This is now the operating standard for the industry, whether or not a plan's own programs are named in a settlement.
The Firewall: What IQRP Builds
A firewall does not clean up damage after the fact. It sits between the exposure and the plan, before either DOJ or a RADV auditor comes looking. IQRP's Coding Supply Chain Assurance Program applies that logic to every diagnosis code the way a financial auditor applies it to a transaction: source it, timestamp it, and require sign off before it counts.
Four controls, mapped to DOJ's test
- Amendment origin tracking — every chart addition flagged by who initiated it, so the "who" question is answered automatically instead of reconstructed under pressure.
- Timing controls — diagnoses checked against date of service on scheduled review cycles, so codes landing outside a defendable window surface as outliers before annual reconciliation, not after.
- Physician led sign off — every HCC carries evidence a treating clinician would recognize and affirm, not a coder's inference from the note alone.
- Contractual boundaries — documentation standards and audit rights built into provider agreements, so exposure has a defined edge before it is tested.
The Outcome: What a Plan Can Prove, On Demand
The Villages Health case took roughly two years from self disclosure to settlement, on top of four years of underlying conduct. A plan running IQRP's firewall does not wait for that timeline to play out before finding out what its own network data shows.
It can answer, at any point and without a scramble: which codes in the network carry a defendable amendment trail, which don't, how far outside the timing window any outliers fall, and what a four year retrospective review would find today rather than in a DOJ press release two years from now.
That is the difference between a plan reacting to the next version of this case and a plan that already knows the answer when someone asks. Risk adjustment exposure now runs through the entire provider supply chain, not just the plan's own coding team, and the firewall has to be built there too.
Earl Fredrick, III, MD, MBA, CHCQM, FABQAURP is the Founder and Chief Medical Officer of IQRP, Integrated Quality & Risk Partners. He can be reached at efredrick@iqrp.org. IQRP partners with Medicare Advantage plans, ACOs, D-SNPs, and PACE organizations to close the gap between clinical documentation, risk adjustment accuracy, and audit defensibility.
Key Takeaways
- A $541.5M settlement was paid down by three MA plans, none of them named as defendants
- DOJ's test for a defendable chart amendment: who initiated it, how long after the visit, and whether the treating clinician approved it
- Contractual exposure follows plan level acceptance of network data, not plan level misconduct
- Add-only, untimed, or unapproved amendments are now explicit DOJ enforcement targets
- A defendable supply chain requires amendment origin tracking, timing controls, physician sign off, and contractual audit rights
Request a Coding Supply Chain Assessment
A no-obligation review of your network's amendment origin, timing, and sign off exposure.
Request Assessment →