For many healthcare professionals, today’s conversations surrounding Medicare Advantage risk adjustment are increasingly shaped by a news cycle of RADV audits, Department of Justice (DOJ) settlements, Office of Inspector General (OIG) findings, and heightened Centers for Medicare & Medicaid Services (CMS) oversight. Read enough headlines, and it’s easy to conclude that risk adjustment has become little more than a hunt for overpayments.
I Would Argue That Perspective Misses the Larger Story
Risk adjustment was designed to account for differences in disease burden because patients with greater healthcare needs often require more intensive management, closer monitoring, and greater coordination of care.
Diagnoses submitted to CMS become part of the clinical picture used to describe a population’s chronic disease burden. Hierarchical Condition Categories (HCCs) are the mechanism through which qualifying diagnoses are incorporated into the risk-adjustment model, contributing to risk scores used in risk-adjusted payment. The code, then, is not the endpoint. It becomes data, and that data is a representation of the population being served.
Therefore, Payment Integrity Must Run in Both Directions
Much of today’s regulatory attention and compliance infrastructure surrounding risk adjustment is conditioned to detect unsupported diagnoses and disproportionately focuses on the risk of overpayment. An unsupported diagnosis may overstate disease burden, while a clinically supported condition that is missed, inadequately documented, or reported without sufficient specificity may understate it. In either direction, the data may no longer accurately represent the patient’s health status and expected healthcare needs that the model is intended to reflect.
If we’re serious about Medicare risk-adjustment program integrity, it has to mean more than finding money that shouldn’t have been paid.
For coding professionals, technical proficiency has always been the floor, but this broader perspective expands the lens from coding accuracy to documentation integrity.

Technically Accurate Coding Can Coexist with Incomplete Documentation
A provider may document, “Patient in today for follow-up of chronic kidney disease.”
A coder focused solely on code assignment may report N18.9, chronic kidney disease, unspecified, as documented. On that statement alone, the assignment is accurate.
Now consider that the record also contains an eGFR consistent with advanced renal disease. Although coders cannot independently interpret laboratory values and assign a CKD stage, we can recognize the opportunity for greater specificity and query the provider for clarification when clinically appropriate.
Without that clarification, the severity reflected elsewhere in the chart may never be represented in the diagnosis reported to CMS. Under CMS-HCC V28, N18.9, chronic kidney disease, unspecified, does not map to an HCC. Greater diagnostic specificity, when clinically supported and documented by the provider, can materially change how the patient’s CKD is represented within the risk-adjustment model and ultimately affect risk-adjusted payment. Nothing was necessarily coded incorrectly, yet the data leaving the encounter may still describe a less complex patient than the record itself suggests.
Consequences That Have Teeth
In May 2026, the OIG reported that CMS potentially overpaid Medicare Advantage organizations $462 million based on certain unsupported acute stroke diagnosis codes reported during the 2020 service year. The finding illustrates the opposite failure: instead of clinically supported complexity being insufficiently represented, diagnoses were reported
without corresponding evidence in the medical record. The direction of the error is different, but the integrity standard remains the same: the data should not represent patients as sicker or healthier than the medical record supports.
For organizations developing coding teams in this environment, that standard should influence how we educate, audit, and measure performance:
- Teach beyond the guideline. Risk adjustment coding professionals should understand what happens after a diagnosis is coded and reported and be equipped to translate that knowledge into meaningful provider education. Complete and specific documentation does more than support code assignment; it contributes to how the patient is represented within the risk-adjustment model and, ultimately, informs risk-adjusted payment intended to account for differences in expected healthcare costs.
- Audit for what is missing, not only what is wrong. Compliance programs must identify unsupported diagnoses, but documentation integrity also requires attention to clinically supported complexity that the medical record fails to fully communicate.
- Measure more than productivity. Charts per hour and turnaround times matter, but so does a coder’s ability to recognize documentation gaps, query appropriately, and exercise sound judgment when the record warrants a closer look.
Alexis Isom CPC, CPMA, CRC, CHONC, AAPC Approved Instructor
Alexis Isom, CPC, CRC, CPMA, CHONC, is an experienced healthcare professional specializing in medical coding, risk adjustment, auditing, compliance, and hematology and oncology coding. Her broad range of expertise gives her a well-rounded perspective on the relationship between clinical documentation, accurate code assignment, regulatory requirements, and reimbursement.