HCC Buddy

The "40%" number comes up whenever we talk to HCC coders and coding managers about where chart time actually goes. It's not clinical judgment that eats the hour — it's the lookups. Code verification. V28 cross-referencing. MEAT documentation criteria. The process of confirming what you already suspect is correct.

This post breaks down where the time actually goes, why it compounds at the team level, and how eliminating lookup friction changes the math.

Where the Time Actually Goes

An average HCC chart review session takes 15–25 minutes. Break down what's happening during that time:

• Reading and interpreting clinical documentation: 6–10 minutes — this is the clinical judgment work, irreducible
• Code lookup and verification: 3–5 minutes per encounter — ICD-10-CM detail, confirming billable status, checking inclusion/exclusion notes
• V28 HCC mapping verification: 2–4 minutes — confirming which HCC category a code maps to, whether it changed from V24, what the RAF weight is
• MEAT documentation review: 2–3 minutes — confirming documentation supports the HCC code selected, identifying gaps
• Cross-referencing between tabs/tools: 1–3 minutes — switching between the EHR, a coding reference, a V28 mapping table, a MEAT criteria document

The non-clinical steps — lookup, verification, cross-referencing — consistently account for 8–15 minutes per chart. On a 20-chart day, that's 2.5–5 hours per coder spent on tasks that require no clinical judgment and generate no billable value beyond confirming what the coder already knows.

Why V28 Made This Worse

The V24 model had 86 HCC categories. Coders who worked with it long enough built intuitive knowledge: they knew which codes mapped, roughly what category, and whether documentation needed to be more specific. That pattern recognition was a legitimate productivity asset.

V28's full 2026 rollout invalidated much of that institutional knowledge. 2,000+ codes were removed from HCC mapping. Hundreds were reassigned to different categories. 29 new HCC categories were added. The model expanded to 115 categories.

The result: coders can no longer rely on memory for V28 verification. Every HCC-relevant code needs a live lookup. Teams that haven't adapted their tooling are spending significantly more time per chart in 2026 than they did in 2024.

The Current Workflow vs. the HCC Buddy Workflow

The workflow change isn't about replacing clinical judgment — it's about eliminating the mechanical reference retrieval that surrounds it. The coder's chart time is the same; the lookup time is cut by 3–5 minutes per chart.

The Team-Level Math

Individual time savings compound at the team level in ways that matter for operations and budgeting:

Assumptions: 20 working days/month, $28–$36/hr fully burdened coder cost. Time savings estimates based on 3–5 minutes per chart from eliminating tab-switching and lookup steps.

The "fully burdened coder cost" figure — salary + benefits + overhead — typically runs $28–$36/hr for experienced HCC coders in the current market. Even at the conservative end of time savings (3 minutes per chart), the ROI for a team of 10 coders is approximately 27:1 annually. The cost of not having the tool is roughly 27 times the cost of having it.

What Doesn't Change

It's worth being direct about what HCC Buddy doesn't accelerate:

• Clinical judgment time — Reading the note, interpreting findings, deciding what's supported: HCC Buddy doesn't speed this up and doesn't try to. This is where the coder's expertise lives.
• Documentation gap queries — When a chart needs physician clarification, that process doesn't change.
• Complex multi-condition coding — HCC Buddy helps with individual code lookups; sequencing and combination coding logic still requires the coder's judgment.
• Quality accuracy — HCC Buddy surfaces information; the coder makes the coding decision. If accuracy was a problem before, faster lookups don't fix accuracy gaps.

How to Implement It (No IT Required)