Navigating the 2026 CPT Code Changes

Every year the AMA's CPT Editorial Panel reshapes part of the code set, and every year practices lose revenue simply because nobody translated those edits into day-to-day workflow. The 2026 revision is a heavier lift than most: it touches evaluation and management documentation, remote monitoring, and several procedural families at once.

This guide walks through what actually changes, who it affects, and the operational steps to take before the effective date.

Why this cycle matters more than usual

Most annual updates are incremental - a handful of deletions, some new Category III codes, and a few descriptor clarifications. This cycle bundles three separate pressures together:

• Structural edits to code families that many specialties bill daily, not just niche procedures.
• Documentation-driven changes, where the code itself survives but the supporting note must contain new elements.
• Payer lag, because commercial plans adopt edits on their own timelines, so the same encounter can be correct under one contract and denied under another.

That third point is what turns a coding update into a revenue problem. A clean claim is not merely a correctly coded claim; it is a claim coded correctly for that payer, on that date of service.

Evaluation and management: documentation over volume

The continuing direction of travel for E/M is that medical decision making and total time govern level selection, and the narrative has to support the level on its own. Practices that still lean on templated history and exam text are the most exposed.

What to check in your notes

• Does the note state the number and complexity of problems addressed at the encounter, not merely the problem list?
• Is data reviewed attributed - which labs, which external notes, which independent interpretation?
• Where time is the basis, is total time on the date of service documented, including non-face-to-face work?
• Is risk articulated in terms of management options considered, including options ruled out?

That last item is the most commonly missed. Considering and rejecting a treatment is legitimate decision making, but only if the note says so.

Remote monitoring and digital services

Remote physiologic and therapeutic monitoring continue to expand, and with expansion comes scrutiny. The recurring denial patterns are consistent:

• Billing a monitoring management code without the required minimum monitoring days in the period.
• Missing documentation of interactive communication where the descriptor requires it.
• Device supply and management codes billed by two entities for the same patient in the same month.

If your practice launched a monitoring program recently, audit the first sixty days of claims before the code changes land. Fixing a process error on fifty claims is cheap; fixing it on five thousand is not.

Category III codes and emerging technology

Category III codes track emerging services. They are not optional when one applies - using an unlisted Category I code instead of an available Category III code is a compliance issue, and it also deprives the specialty of the utilization data needed to justify a future Category I code.

The tradeoff is that Category III codes are frequently non-covered. The correct workflow is to code accurately, verify coverage in advance, and use an advance beneficiary notice or financial responsibility form where appropriate. Coding around a coverage problem is not a coding solution.

A practical transition plan

Sixty days out

• Pull your top 50 codes by volume and your top 25 by revenue, and flag any that appear in the change set.
• Map each flagged code to the providers and locations that bill it.

Thirty days out

• Update charge master entries, superbills, and EHR favorites. Stale favorites lists are a leading cause of post-transition denials.
• Confirm which payers have published adoption guidance and which have not.
• Brief providers on documentation deltas only for the codes they actually bill. Generic training gets ignored.

First thirty days after

• Hold a daily pre-bill review on affected code families for the first two weeks.
• Track first-pass acceptance by payer and by code, not just in aggregate.
• Escalate any denial reason that appears three times to a written payer inquiry immediately.

The bottom line

Code set changes are predictable, which means the revenue loss they cause is preventable. The practices that come through cleanly are not the ones with the most coders - they are the ones that treat the annual update as a scheduled operational project with owners, dates, and a feedback loop, rather than a memo circulated in December.