A $541.5 Million Settlement Put One Question Above Every Diagnosis Code: Who Approved the Chart?

On August 26, 2026, the U.S. Department of Justice announced that The Villages Health System had agreed to a $541.5 million settlement resolving self-disclosed False Claims Act allegations involving diagnosis codes submitted to Medicare Advantage organizations from 2020 through 2024. The bankruptcy court approved the agreement the day before. The amount is an allowed, nondischargeable claim against the bankruptcy estate, not proof that $541.5 million was paid immediately. The government also states that the settlement resolves allegations only and that there has been no determination of liability.

Those qualifications matter. So does the specific conduct the government described. DOJ alleged that diagnosis codes increased payments from the Centers for Medicare & Medicaid Services to Medicare Advantage organizations and, through the provider's arrangements with those organizations, increased payments to the provider group. The codes were alleged to lack adequate medical-record support or to rely on amendments that were not initiated by the rendering provider, were not timely, or were not approved by that provider.

This is not a warning against complete diagnosis capture, and it is not a reason to avoid correcting a legitimate record. It is a warning about traceability. A revenue-bearing diagnosis needs a defensible path back to the face-to-face encounter, the care delivered, the clinician responsible for the record, and the evidence that existed when the code was submitted.

Independent practices may not have the same risk-sharing arrangements described in this case, and ordinary fee-for-service coding does not automatically create Medicare Advantage risk-adjustment revenue for a practice. But the control lesson travels. Once a diagnosis moves from the chart into a claim, a quality program, a payer file, or a value-based arrangement, the practice must be able to show where it came from and who owned the clinical decision.

The Line Between a Correction and a Revenue-Cycle Risk

Medical records sometimes need legitimate amendments. A clinician may correct an error, clarify a statement, or add information that was inadvertently omitted. The problem begins when the amendment process is treated as a coding tool rather than a clinical-record process.

The DOJ account draws a practical boundary. The diagnosis has to be supported by the medical record from the relevant face-to-face visit and, for an outpatient visit, must have required or affected care, treatment, or management at that encounter. A later reviewer cannot create that clinical fact simply because a code would improve payment.

• The Encounter Comes First: The condition must connect to what the clinician assessed, monitored, evaluated, or treated at the visit. A code search performed later is not a substitute for encounter evidence.
• The Rendering Provider Owns the Clinical Record: Coders and reviewers can identify a question. They should not answer it for the clinician or insert a diagnosis into the record without the clinician's proper involvement.
• Timing Is Part of the Evidence: A correction made close to the encounter is easier to understand and defend than an unexplained change months later. The record should show when the amendment occurred and why.
• Approval Must Be Real, Not Ceremonial: A sign-off is not a safe control if the approving clinician did not render the care, cannot verify the encounter, or is being asked only to confirm a code selected by somebody else.
• The Submission Must Match the Supported Record: The final diagnosis file, claim, or payer submission should be reconcilable to the version of the chart that supports it.

Where the Risk Enters an Independent Practice

Most practices do not set out to create unsupported codes. The risk enters through ordinary pressure: a backlog, a payer request, a gap-closing project, a year-end coding review, or an outside team paid to find diagnoses that were missed. Each step can be legitimate. The danger is a handoff that separates revenue work from clinical ownership.

• A Retrospective List With No Encounter Link: A reviewer finds a historical diagnosis but cannot identify the visit where the condition affected care. The code is treated as reusable because it appeared somewhere in the chart.
• A Query That Supplies Its Own Answer: The clinician receives a request framed around one desired diagnosis instead of a neutral question about the documented condition and care.
• A Late Amendment With No Reason: The chart changes, but the record does not explain what was corrected, when it was corrected, or what evidence supports the change.
• A Substitute Approver: A manager or another clinician approves an amendment without first-hand knowledge of the encounter and without a documented basis for doing so.
• No Reconciliation Before Submission: The payer file contains codes that no one compares back to the final signed record. A mismatch becomes visible only during an audit or repayment review.

These are governance failures before they are coding failures. The coder may be accurate, the clinician may be acting in good faith, and the payer file may still contain a diagnosis the practice cannot reconstruct two years later.

Five Controls to Put in Place Now

A practice does not need a large compliance department to build a defensible chain. It needs a short set of controls that everyone follows the same way.

• Tie Every Diagnosis to a Source Encounter: Keep the date of service, rendering provider, supporting note location, and reason the condition affected care with the coding decision.
• Separate the Question From the Approval: A coder or reviewer may raise a neutral clarification. Only the appropriate clinician determines whether the record should be amended and what the clinical statement should say.
• Use a Dated Amendment Standard: Preserve the original entry, identify the person making the change, record the date and reason, and follow the practice's legal, payer, and clinical documentation requirements.
• Create an Exception Queue Before Submission: Unsupported, late, unclear, or substitute-approved items stop in a named queue. They do not move forward because a deadline is close or the financial effect is large.
• Sample the Chain, Not Only the Code: Audit a focused set of high-impact diagnoses from submission back to the encounter. Confirm that another person can reconstruct the entire decision without relying on somebody's memory.

If a review identifies a possible overpayment or disclosure question, the decision belongs with qualified legal and compliance advisers. The revenue-cycle team should preserve the facts, stop further unsupported submissions, and avoid guessing about repayment or self-disclosure obligations.

The VOSKPO Approach: Make the Diagnosis Traceable Before It Travels

VOSKPO treats diagnosis capture as a controlled chain, not as a search for codes that increase payment. The goal is complete, accurate billing that can survive review because the evidence and ownership are visible from the beginning.

• Encounter-to-Code Reconciliation: We connect the diagnosis selected for submission to the relevant visit, documentation, rendering provider, and final signed record.
• Neutral Clarification Workflows: Documentation questions return to the clinician without steering the answer. The clinical decision stays with the person qualified to make it.
• Pre-Submission Exception Handling: Codes with missing support, unclear timing, or incomplete approval stop before they enter a payer file. Each exception has an owner, a due date, and a recorded outcome.
• Targeted Audit Samples: We test the diagnoses most likely to affect payment or attract scrutiny and show the practice where the chain breaks by provider, workflow, payer, or source.
• Correction and Escalation Paths: When a mismatch is found, the practice can correct the operating process quickly and route legal or repayment questions to the right adviser with the evidence already organized.

The lesson is not to code less. It is to make every revenue-bearing diagnosis traceable. Complete coding and defensible coding are the same discipline when the workflow is designed properly.

The KPO Layer: Keep the Rules Usable and Current

A policy binder does not control a live coding workflow. Knowledge Process Outsourcing turns changing Medicare Advantage, payer, coding, and documentation requirements into instructions that clinicians, coders, and managers can use while the work is happening.

• Maintain the Source Rules: Keep the current CMS, payer, coding, and documentation sources linked to their effective dates and the workflows they affect.
• Translate Policy Into Short Instructions: Build separate checklists for the clinician, coder, reviewer, and approver so each person knows what they own and what they must not do.
• Monitor Change: Update the workflow when a payer changes a risk-adjustment rule, documentation standard, file specification, or audit focus.
• Train From Exceptions: Use de-identified workflow examples and audit findings to improve the checklist without exposing patient information or turning one incident into an unsupported general rule.
• Preserve the Decision Trail: Record which source was used, what changed, who approved the operating instruction, and when the next review is due.

That combination gives an independent practice something a policy document cannot: a current, repeatable way to protect revenue without separating the code from the care that supports it.

Start with one test. Select ten high-impact diagnoses submitted in the last quarter and trace each one back to the encounter, the signed record, and any amendment. If the path depends on memory, the control is not finished. VOSKPO can include that diagnosis-to-documentation chain in a Free Revenue Review and show where coding, billing, compliance, and follow-up need to connect.