Overview
A suspect condition is a diagnosis that a risk-adjustment program has reason to believe is clinically present for a patient but is not yet coded on the current year's claims. Suspects drive prospective and concurrent review workflows: the provider receives a list of suspects before or during the visit, evaluates each one, and documents the current clinical status in the progress note.
Suspects are derived from multiple data sources. The most common is prior-year HCC history — chronic conditions coded in the prior year that, by nature of the condition (diabetes, CKD, CHF, dementia), will almost certainly still be present and should be re-evaluated in the current year. Pharmacy data is a second source; a refill for levothyroxine suggests hypothyroidism, a GLP-1 refill suggests diabetes or obesity. Lab data is a third; an A1c of 9.5 suggests uncontrolled diabetes, an eGFR of 30 suggests CKD stage 4. Prior-authorization records, claims data from specialty encounters, and hospital discharge summaries all contribute. Some programs layer predictive machine-learning models on top of the rule-based suspects to flag less obvious conditions.
Critical governance principle: a suspect is a hypothesis, not a coding instruction. The provider must independently evaluate the condition during the encounter and document MEAT — monitoring, evaluation, assessment, and/or treatment — in the progress note. If the condition is not present, the provider documents that ("resolved," "no longer active," "ruled out"). If present, the provider documents clinical status and any care actions. Only then is the condition coded on the claim.
Auto-coding from suspect lists without independent evaluation is a compliance failure that has been the subject of DOJ and OIG enforcement. Programs that push providers to sign off on suspects without review, or that add diagnoses to claims based on suspect-list match alone, expose the organization to RADV recoupment and False Claims Act liability. Compliant programs treat suspect lists as clinical decision-support for the provider, not as coding shortcuts.
Presentation format for suspects varies by program. Best-in-class programs embed suspects into the EHR huddle workflow and the progress note template, making it easy for the provider to address each one with a single click. Weaker programs deliver suspects via email or PDF outside the EHR, which reduces clinical engagement and increases the likelihood that suspects go unaddressed.
Suspect-list accuracy matters. Lists that are too noisy (low precision) fatigue providers and are ignored; lists that are too conservative (low recall) miss legitimate captures. CRC-led curation — filtering suspects by MEAT sufficiency, clinical plausibility, and prior-year recency — is the operational discipline that makes suspect programs effective.
Industry benchmark
Well-curated suspect lists achieve 50–70% confirmation rates at the point of care. Lists below 30% confirmation are typically over-inclusive; lists above 85% are typically under-inclusive.
Worked example
A primary-care panel of 1,800 MA members generates 420 suspect conditions for the upcoming quarter. Providers confirm 250, rule out 110, and defer 60 pending further evaluation. The 250 confirmed conditions lift panel-level RAF by 0.06 points and produce approximately $1.9M of incremental risk-adjusted revenue for the payment year.
Frequently asked questions — Suspect Condition
Who curates the suspect list?
Typically a CRC-credentialed coder or a vendor's risk-adjustment analytics team. Clinical pharmacists and care managers sometimes contribute for medication-derived suspects.
Can a suspect be coded without provider evaluation?
No. Auto-coding from suspects without provider evaluation and MEAT documentation is a compliance failure. Suspects are clinical decision-support, not coding authority.
What happens when a provider rules out a suspect?
The rule-out is documented in the progress note, the condition is not coded for the current year, and the suspect-list engine removes it from future cycles until new signals reappear. Good governance tracks rule-outs as data quality indicators.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.