HCC risk adjustment coding determines Medicare Advantage payment accuracy by translating chronic conditions into revenue impact. When you code diagnoses too vaguely or miss supporting documentation, CMS pays your plan less than the patient's condition severity warrants. This post covers the 5 most common HCC coding errors that drive RADV audit failures and payment takebacks, with compliance-focused fixes for each.
These mistakes aren't abstractions. They're patterns CMS auditors flag first when they review Medicare Advantage charts. You'll see why specificity requirements matter, how documentation gaps create risk, and what to change now before your next audit cycle.
Mistake 1: coding unspecified diabetes codes when documentation supports specificity
Unspecified diabetes codes like E11.9 (Type 2 diabetes without complications) miss condition severity and underpay your plan. CMS doesn't accept vague codes when the medical record contains enough detail to assign a more specific diagnosis.
Many coders default to E11.9 when the provider mentions "diabetes" in an assessment. But if the chart notes retinopathy, nephropathy, neuropathy, or circulatory complications anywhere in the encounter, you're required to code those manifestations.
A 2025 CMS RADV audit report found unspecified diabetes codes in 37% of rejected claims. The documentation supported more specific codes in nearly all cases. The plans paid back millions.
How to fix it
Read the full encounter note, not just the assessment line. Look for complication mentions in the history of present illness, review of systems, physical exam findings, and medication lists. Insulin use alone doesn't prove complications, but metformin plus gabapentin plus atorvastatin suggests neuropathy and cardiovascular involvement.
Query the provider if you see complications documented but not linked to diabetes in the assessment. A 2-sentence query typically clears this up: "You documented peripheral neuropathy and patient has Type 2 diabetes. Is the neuropathy due to diabetes?"
Use combination codes when appropriate. E11.21 (Type 2 diabetes with diabetic nephropathy) captures both the diabetes and the complication in one code, which accurately reflects disease burden and correctly adjusts the RAF score.
Common errors in HCC risk adjustment coding for heart failure
Heart failure coding trips up even experienced coders because specificity requirements changed significantly under ICD-10. You can't code I50.9 (heart failure, unspecified) when the chart differentiates between systolic, diastolic, or combined dysfunction.
CMS expects you to code acuity (acute, chronic, acute on chronic) and type (systolic, diastolic, combined). An echocardiogram report from 3 months ago that shows reduced ejection fraction supports chronic systolic heart failure coding at today's visit, even if the provider doesn't explicitly restate it.
Another gap: coders often miss the connection between heart failure and related conditions. If a patient has chronic kidney disease and heart failure, both diagnoses affect each other's management and both belong in your HCC capture.
Documentation requirements
The provider must document heart failure as a current condition affecting today's visit. "History of heart failure" doesn't count unless the documentation shows ongoing treatment, monitoring, or management during this encounter.
Link supporting test results to the diagnosis. If an echocardiogram shows EF of 35%, that supports systolic heart failure coding. If BNP is elevated and the provider adjusts diuretics, that's active management of current heart failure.
When the chart mentions heart failure but doesn't specify type, and no recent echo is available, you need a provider query. Don't guess. Unspecified codes get rejected in RADV audits when any historical documentation in the health record could have supported specificity.
Missing capture of chronic conditions during wellness visits
Wellness visits generate most HCC capture opportunities for Medicare Advantage plans, but coders routinely miss chronic conditions that affect care but aren't the reason for today's visit.
A patient comes in for an annual physical. The provider refills metformin, checks A1C, discusses blood pressure control, reviews COPD inhaler technique, and orders a lipid panel. You code the wellness visit but forget to capture the diabetes, hypertension, COPD, and hyperlipidemia.
Those diagnoses matter. They drove treatment decisions during this encounter. They affect risk score calculation. They belong on the claim.
CMS requires every chronic condition addressed, monitored, evaluated, assessed, or treated during the encounter to appear on the claim with appropriate specificity. "Addressed" has a broad definition. Refilling a chronic disease medication counts. So does reviewing home glucose logs or adjusting an inhaler dose.
Process improvements that work
Create a chronic condition checklist for wellness visits. Before you finalize coding, scan the medication list, problem list, and assessment for chronic diagnoses. If the provider touched it during this visit, code it.
Train coders to recognize indirect evidence of chronic condition management. Ordering an A1C test implies diabetes monitoring. Discussing sodium restriction implies heart failure or hypertension management. A COPD assessment test score in the vitals section means COPD was evaluated.
Work with your physician query process to get providers comfortable listing all chronic conditions in the assessment, not just the chief complaint. This habit change alone fixes most missed capture problems.
Documentation gaps that invalidate HCC capture
You can't code a condition without documentation that shows it affected this specific encounter. Historical diagnoses don't count unless the provider shows current relevance.
A chart note lists "morbid obesity" in the problem list but never mentions weight, BMI, obesity management, related complications, or treatment during the visit. That code gets rejected in a RADV audit. The condition must be addressed, assessed, evaluated, or treated to be coded.
The same rule applies to behavioral health diagnoses, chronic liver disease, amputations, and every other HCC category. If it's not documented as a current condition affecting today's care, it can't appear on today's claim.
What constitutes valid documentation
CMS requires one of these elements for every diagnosis you code: assessment, treatment, monitoring, or medical decision-making impact. The provider doesn't need to write an essay. A single sentence works if it shows the condition mattered during this encounter.
Examples that satisfy CMS requirements: "COPD stable on current regimen." "Chronic kidney disease stage 3, creatinine monitored." "Depression controlled with sertraline." "BMI 42, discussed bariatric surgery options."
Examples that fail: pulling codes from the problem list with no corresponding mention in the encounter note, coding based on a diagnosis from 18 months ago with no current documentation, or listing a condition the provider never addressed during this visit.
If documentation is thin, query before you code. A quick clarification query prevents a failed audit 3 years later when CMS reviews the chart and finds insufficient support for the RAF score you claimed.
Incorrect hierarchies and code sequencing
HCC coding uses a hierarchy system where more severe manifestations of a condition suppress payment for less severe codes. When you code both the parent and child condition, CMS only pays for the more severe one but your claim can still fail compliance review.
Common example: coding both chronic kidney disease stage 3 (HCC 138) and stage 4 (HCC 137) for the same patient. Stage 4 is more severe and suppresses stage 3 in the risk score calculation. But submitting both codes signals you don't understand HCC hierarchies, which raises audit risk.
Another frequent error: coding diabetes without complications (HCC 19) and diabetes with chronic complications (HCC 18) together. The hierarchy rules eliminate the less severe code from payment, but the coding error itself becomes an audit flag.
How to prevent hierarchy errors
Use certified HCC coding software that flags hierarchy conflicts before claim submission. Most modern encoders show you which codes will suppress others and warn you when you've selected both.
Train coders on the HCC model structure. Understanding that CMS groups conditions by severity helps prevent the mistake in the first place. You can find the current hierarchy mappings in the CMS risk adjustment documentation.
Review rejected claims for hierarchy errors. If CMS is kicking back your submissions for code conflicts, that's a training gap. Most organizations see this pattern disappear within 60 days once coders learn the rules.
How professional coding support reduces risk
These 5 errors account for most HCC coding failures we see in new client audits. They're fixable, but they require consistent processes and trained staff who understand both ICD-10 guidelines and CMS risk adjustment requirements.
Many revenue cycle teams don't have the bandwidth to maintain HCC coding expertise while handling day-to-day claim volume. That's where specialized coding support changes the equation.
Outsourced HCC coders bring current certification, regular CMS compliance training, and quality processes built specifically for risk adjustment work. You get fewer rejected claims, cleaner RADV audits, and accurate RAF scores without adding headcount or training costs.
If your plan is facing RADV audit challenges or you're seeing payment takebacks from unsupported codes, MedCodex Health offers a free HCC coding assessment. We'll review a sample of your charts, identify your highest-risk error patterns, and show you exactly how much revenue you're leaving on the table. No obligation. Just answers.
Frequently asked questions about HCC risk adjustment coding
What is HCC risk adjustment coding?
HCC risk adjustment coding translates patient diagnoses into Hierarchical Condition Categories that determine Medicare Advantage payment rates. Each chronic condition maps to an HCC that carries a specific risk score weight, and CMS uses those weights to calculate how much your plan receives per member. More accurate coding of documented conditions results in payment that better matches patient care costs.
How often do HCC codes need to be documented?
Every chronic condition must be documented at least once per calendar year to count toward that year's risk score calculation. The documentation must show the condition was assessed, evaluated, monitored, or treated during an encounter. Simply copying a problem list without addressing the condition in the visit note doesn't satisfy CMS requirements.
What happens if HCC coding is wrong during a RADV audit?
CMS conducts Risk Adjustment Data Validation audits by pulling a random sample of member charts and verifying that coded diagnoses are fully supported by documentation. If codes fail validation, CMS extrapolates the error rate across your entire book of business and claws back payments, often millions of dollars. Repeat violations can trigger higher audit frequency and compliance plans.
Can you code HCC diagnoses from specialist notes?
Yes, you can code diagnoses from any qualified provider's documentation, including specialists. The specialist must clearly document that they assessed, treated, or monitored the condition during the encounter. Consultant recommendations that a primary care provider should address a condition don't count. The specialist must actually manage the diagnosis during their visit for you to code it from their note.
Do all diabetes codes qualify for HCC capture?
Most diabetes codes map to HCC categories, but specificity determines the risk score weight. Type 2 diabetes without complications (E11.9) maps to HCC 19 with a lower weight. Type 2 diabetes with complications (E11.2x series) maps to HCC 18 with a higher weight. Coding the most specific supported diagnosis directly affects your plan's revenue per member.