Skip to content
Back to Blog
April 10, 2026·10 min read

How to Increase HCC Coding Speed: Tips From Coders Who Did It

HCC CodingProductivitySpeedTips

By Daniel Plasencia — Certified Risk Coder (CRC), Certified Professional Coder (CPC)

How to Increase HCC Coding Speed: Tips From Coders Who Did It

Quick Answer

The fastest HCC coders hit 50+ charts per day at 95%+ accuracy by combining three things: eliminating unnecessary clicks (tool optimization and keyboard shortcuts), batching similar work together, and doing pre-visit prep so they know what to look for before opening the chart. Speed in HCC coding is not about reading faster — it is about removing everything that is not reading and coding from your workflow. Coders who made the jump from 30 charts/day to 50+ charts/day consistently report that tool changes and workflow restructuring mattered more than raw coding knowledge.

The Speed Pressure Is Real

If you are reading this, you probably know the pressure. AAPC forums are full of posts from risk adjustment coders asking how to get faster. The numbers look something like this:

  • Entry-level expectation: 25-35 charts per day
  • Standard production target: 40-50 charts per day
  • High-performance target: 55-70 charts per day
  • Accuracy floor: 93-95% (below this, speed does not matter)
  • Coders who cannot hit production targets face real consequences — performance improvement plans, reduced hours, or termination. This is not abstract productivity advice. It is job security.

    The good news: speed is learnable. It is not a talent issue. It is a systems issue. Here are the specific changes that move the needle.

    Tip 1: Eliminate Tab-Switching

    The single biggest speed killer in HCC coding is switching between your EHR and your coding tools. Every tab switch costs 5 to 15 seconds of cognitive reorientation, and a typical chart requires 8 to 15 lookups. That is 40 to 225 seconds of lost time per chart — just from switching tabs.

    The fix: Use a coding tool that works inside your browser alongside your EHR. The HCC Buddy Chrome Extension opens as a side panel, so you look up codes without leaving the chart. Coders who switch from tab-based tools to the extension consistently report saving 60 to 90 minutes per day.

    If you cannot use a Chrome extension (some organizations restrict browser extensions), arrange your screen with the EHR on one side and your coding tool on the other. Two monitors is significantly faster than one monitor with tab-switching.

    Tip 2: Learn 50 Codes by Heart

    You do not need to memorize all 72,000+ ICD-10-CM codes. You need to know approximately 50 by heart — the ones that appear in 80% of your charts.

    For risk adjustment coding, these typically include:

  • Diabetes family: E11.9, E11.65, E11.22, E11.42, E11.311, E11.319
  • Heart failure: I50.22, I50.32, I50.42, I50.9
  • CKD: N18.1 through N18.5, N18.6
  • COPD: J44.0, J44.1, J44.9
  • Hypertension combos: I12.9, I13.0, I13.10
  • Depression: F32.0, F32.1, F32.2, F33.0, F33.1, F33.2
  • Obesity: E66.01, E66.09
  • AFib: I48.0, I48.1, I48.2, I48.91
  • Dementia: F01.50, F01.51, F02.80, F02.81, F03.90, F03.91, G30.9
  • Vascular disease: I70.0, I73.9, I63.x
  • Knowing these codes by heart means you do not look them up. You confirm them with your tool (always verify), but you are not searching from scratch. This saves 3 to 5 seconds per code, which compounds to 15 to 30 minutes per day.

    How to learn them: Use flashcards for two weeks. Anki is free. Make a card for each code with the description on one side and the code + HCC mapping on the other. Twenty minutes of flashcards per day for two weeks will lock in the top 50 codes.

    Tip 3: Batch Similar Charts Together

    Context-switching between chart types is expensive. A Medicare Advantage chart from a PCP visit has a different documentation pattern than one from a specialist visit or an inpatient discharge. When you jump between chart types, your brain has to re-calibrate what to look for.

    The fix: If your workflow allows it, sort your queue by provider, specialty, or visit type before you start. Code all the PCP charts, then all the cardiology charts, then all the inpatient charts. Batching reduces the cognitive switching cost and lets you build momentum within each category.

    Some coders batch by diagnosis pattern instead of provider: all the diabetes-heavy charts first, then the cardiovascular charts, then the respiratory charts. The specific batching strategy matters less than the principle — similar charts in sequence.

    Tip 4: Use Pre-Visit Prep for Prospective Reviews

    If you are doing prospective risk adjustment (reviewing charts before the encounter), pre-visit prep is the highest-leverage time investment you can make.

    Before the patient visit, pull:

  • Last year's HCC profile — Which HCCs were captured last year? These need to be recaptured this year.
  • Current medication list — Cross-reference against the diagnosis list using the Drug Reference tool. A patient on insulin, lisinopril, and metoprolol who only has "diabetes" and "hypertension" documented is likely missing diabetic complications and possibly heart failure.
  • Recent lab results — A1C, eGFR, BNP, and lipid panels all indicate severity that may support more specific codes.
  • Pre-visit prep means you walk into the chart knowing exactly what HCCs you are looking for. Instead of reading the entire chart hoping to find relevant diagnoses, you are confirming expected diagnoses and looking for new ones. This cuts chart review time by 30 to 50%.

    Tip 5: Master Keyboard Shortcuts

    Mouse-driven workflows are inherently slower than keyboard-driven workflows. Every time your hand moves from keyboard to mouse and back, you lose 1 to 2 seconds. Over hundreds of charts, this adds up.

    EHR shortcuts to learn:

  • Navigation shortcuts within your specific EHR (these vary by system — ask your EHR trainer or look them up in the system documentation)
  • Copy/paste shortcuts for codes and descriptions
  • Quick-search or command palette shortcuts if your EHR supports them
  • Browser shortcuts:

  • Ctrl/Cmd + L: Jump to the address bar (useful for quick searches)
  • Ctrl/Cmd + T: New tab
  • Ctrl/Cmd + W: Close tab
  • Ctrl/Cmd + Tab: Switch tabs (if you must tab-switch)
  • F6: Focus address bar in Chrome
  • HCC Buddy shortcuts: The Chrome extension side panel supports keyboard-first navigation. You can search, browse results, and view details without touching the mouse.

    Tip 6: Set a Timer and Track Your Pace

    You cannot improve what you do not measure. Use a simple timer to track how long each chart takes:

  • Under 8 minutes per chart: You are on pace for 50+ charts in an 8-hour day (accounting for breaks)
  • 8-12 minutes per chart: You are in the 35-50 charts/day range — good but improvable
  • Over 12 minutes per chart: You are below 35 charts/day — focus on the tips above
  • Track your time for one full day, then identify where the slowdowns are. Is it lookup time? (Fix with better tools.) Is it documentation reading? (Fix with pre-visit prep.) Is it decision-making on codes? (Fix with studying the top 50 codes.)

    Some coders use the Pomodoro technique — 25 minutes of focused coding followed by a 5-minute break. This prevents fatigue-driven slowdowns that accumulate through the day.

    Tip 7: Stop Over-Researching

    There is a difference between thorough coding and over-researching. Thorough coding means verifying that each code is supported by documentation and maps correctly. Over-researching means spending 3 minutes looking up whether F32.9 maps to an HCC (it does not under V28) when you could have verified it in 5 seconds with the right tool and moved on.

    The rule of 30 seconds: If you cannot resolve a coding question in 30 seconds using your tool, flag it for follow-up and move to the next diagnosis. Come back to flagged items at the end of the chart or the end of the day. Do not let one ambiguous diagnosis stall your entire chart.

    Tip 8: Build a Personal Quick-Reference

    Create a one-page document (physical or digital) with:

  • Your top 50 codes and their HCC mappings
  • Common V28 gotchas (codes that lost HCC mapping in the transition)
  • Your organization's specific query templates
  • Quick-reference for MEAT criteria documentation requirements
  • Keep this visible at all times. Even coders who know the codes by heart benefit from a visual confirmation reference that eliminates the "did I remember that right?" hesitation.

    Tip 9: Use the Drug-to-Diagnosis Cross-Reference

    One of the fastest ways to catch missed HCCs is to scan the medication list before you finish the chart. Use the HCC Buddy Drug Reference to look up any medication you do not immediately associate with a coded diagnosis.

    Common catches:

  • Gabapentin/pregabalin on the med list without diabetic neuropathy coded
  • Furosemide/bumetanide without heart failure coded
  • Donepezil/memantine without dementia coded
  • Warfarin/apixaban without AFib or VTE coded
  • This takes 60 to 90 seconds per chart and catches 2 to 5 missed HCCs per day for most coders.

    The Speed-Accuracy Balance

    Speed without accuracy is useless — and dangerous. A coder who closes 70 charts per day with 85% accuracy is producing more errors than a coder who closes 45 charts per day at 97% accuracy. Errors trigger audits, recoupments, and compliance investigations — and federal oversight is tightening, with the OIG work plan project on V24 vs. V28 CMS-HCC trends tracking exactly the kind of RAF drift that high-volume, low-accuracy coding produces.

    The tips above are designed to increase speed without sacrificing accuracy. Eliminating tab-switching does not reduce accuracy — it increases it (fewer cognitive interruptions). Knowing codes by heart does not reduce accuracy — it increases it (less reliance on potentially misread search results). Pre-visit prep does not reduce accuracy — it increases it (you know what to look for).

    Speed and accuracy are not in tension. They are both products of a well-designed workflow.

    Try HCC Buddy free — see how much faster you work with HCC mapping built into every lookup.

    Daniel Plasencia

    Daniel Plasencia

    Founder & Developer

    Daniel Plasencia — Risk adjustment coding professional and software engineer who built the tool he wished existed, at a price coders can actually afford.

    Get HCC Coding Tips in Your Inbox

    Join our newsletter for coding tips, guideline updates, and tool announcements.

    Related Articles