Drug-to-Diagnosis Lookup for Missed HCC Opportunities

The Quick Answer

A drug-to-diagnosis lookup is a reverse-lookup tool that takes a medication name and returns the ICD-10-CM diagnoses that medication is typically used to treat. For HCC coders, it is one of the fastest ways to surface risk-adjusted conditions that appear in the patient's medication list but were never formally documented in the note. When a coder sees Eliquis on the med list but no atrial fibrillation in the assessment, that is a documentation gap worth querying.

Why Medication Lists Matter for HCC Coding

HCC risk adjustment depends on chronic conditions being assessed and documented at least once per calendar year. The CMS M.E.A.T. standard requires that a diagnosis be Monitored, Evaluated, Assessed, or Treated during the encounter to be captured for risk adjustment purposes -- the AAPC MEAT documentation primer is the most widely cited practical explainer of how coders apply that standard at the chart level.

Medications are often the strongest signal of all four. If a patient is actively taking a chronic-disease medication, the underlying condition is by definition being treated. The challenge is that many providers copy the medication list forward but do not re-document the underlying diagnosis in each year's assessment. The condition is real, the treatment is real, and the documentation gap is a risk adjustment gap.

Drug-to-diagnosis lookups close that gap. They let a coder scan a medication list, map each active prescription to its typical indications, and flag any indication that does not appear in the current year's problem list or assessment.

A Real Example

Consider a 72-year-old Medicare Advantage patient whose annual wellness visit note contains this medication list:

The provider's assessment only lists "routine follow-up" and "hyperlipidemia." No HCC is captured.

Now run each drug through a drug-to-diagnosis lookup:

The coder now has three documentation gaps to query: diabetes, heart failure, and the reason Eliquis is on the list. Each query is grounded in a specific medication-to-indication mapping, not a guess.

How to Use Drug-to-Diagnosis Lookups in a Real Workflow

1. Pull the active medication list from the EMR for the current year's encounter.

2. Run each chronic medication through a drug-to-diagnosis lookup. Skip acute medications (antibiotics, short-course steroids) that do not imply chronic conditions.

3. Cross-reference each indication against the current assessment. If an indication appears on the med list but is not addressed in the note, flag it.

4. Draft a compliant provider query. The query should cite the medication, ask whether the underlying condition is still present, and request documentation of the current status. Never suggest a diagnosis — ask the provider to confirm or rule out.

5. If the provider confirms the condition, the new documentation supports the HCC. MEAT is satisfied because the treatment (the active prescription) is evaluated and assessed during the query-response cycle.

What Drug-to-Diagnosis Lookups Cannot Do

Drug-to-diagnosis crosswalks are a starting point, not a final answer. A single medication can have many indications. Gabapentin treats neuropathic pain, seizures, and off-label uses. Prednisone treats dozens of autoimmune and inflammatory conditions. A drug-to-diagnosis lookup tells you the common indications, not the specific reason this patient is on this medication.

That is why drug-to-diagnosis lookups must be paired with a compliant provider query workflow. The coder uses the crosswalk to identify the gap. The provider confirms the actual diagnosis. The documentation closes the loop. No diagnosis ever gets coded from a medication alone -- a principle the OIG work plan on CMS-HCC V24 vs. V28 trends reinforces as a core federal oversight expectation.

Where Drug-to-Diagnosis Fits in the Broader HCC Workflow

Drug-to-diagnosis reviews belong in prospective and concurrent coding workflows more than retrospective ones. The highest-value moment to catch a medication-based gap is before the annual wellness visit happens, so the coder can flag the condition for the provider to address during the visit. That turns a retrospective query into a prospective reminder, which is always more defensible and more efficient. MedPAC's February 2026 CY2027 Advance Notice comment letter specifically urges CMS to continue nudging MA plans toward encounter-based, prospective documentation over retrospective code capture.

Key Facts for HCC Coders

The Bottom Line

Medication lists are one of the most underused signals in risk adjustment coding. A drug-to-diagnosis lookup turns that list from a passive data field into an active source of documentation opportunities. The tool does not replace the coder's judgment or the provider's assessment — it accelerates the gap-identification step so more of the coder's time goes to the parts of the job where experience actually matters.