← Blog

The Add-On Code Nobody Bills

Revenue rarely disappears in the service that wasn't delivered. It disappears in the service that was delivered and never recorded.

In January 2024, Medicare introduced G2211, an add-on code for the complexity of ongoing, longitudinal care. The payment was set. The Centers for Medicare & Medicaid Services (CMS) asked only that the reason for billing appear in the visit note. CMS had projected the code would be appended to 38 to 54 percent of eligible evaluation and management (E/M) office visits.

In its first year, it was appended to 5.2 percent. Physicians were doing the work, and the payer was ready to pay. What was missing was the one thing every claim depends on: a record that shows why. That gap doesn't start in billing. It starts in the exam room.

What Is An Add-On Code?

An add-on code describes additional work performed in the same encounter as a primary service, such as an E/M visit. It is never billed on its own. It exists only alongside the primary code it extends.

That dependency is what makes add-on codes easy to lose. The primary service is obvious, so it gets coded. The additional work, such as an extra clinical evaluation layered onto the visit, lives in the physician's reasoning. Often it never reaches the note in a form anyone downstream can code. This isn't about individual diligence. If nothing in the workflow captures the justification at the point of care, then as far as the claim is concerned, the service never happened.

##Why Did G2211 Go Unbilled?

The data doesn't point to a missing rule or a missing payment. It points to a justification that was rarely written down when the visit happened.

ECG Management Consultants analyzed 2024 billing data from more than 20,000 physicians. They found G2211 on 5.2 percent of eligible E/M visits, against CMS's projected range of 38 to 54 percent. Only 36 percent of physicians billed the code even once. The other 64 percent never did. The documentation bar was not high. CMS guidance asks practitioners to document the reason for billing and adds no requirement beyond standard visit documentation. Medical reviewers may still examine the diagnoses, the assessment and plan, and other services billed to confirm the visit was reasonable and necessary. That is the lesson. When both the rule and the payment exist, the missing piece is the justification, captured at the point of care in a form the claim can stand on. An add-on code that depends on someone remembering to add it later will usually not be added.

What Does A Missing Or Unsupported Add-On Code Cost?

A missing or unsupported add-on code costs in two directions. An add-on service that never reaches the record is never billed. An add-on code billed without supporting documentation invites denials, recoupments and audit exposure. In both cases, the care was delivered. The loss comes from the record. Payers review the documentation behind a code, not just the code itself. If the justification wasn't written during the visit, the billing team can rarely recover it later. Reasoning rebuilt after the fact is slow and incomplete, and harder to defend. Denied claims, write-offs and audit findings come back to the organization as cost, after the work has already been done.

Is The Answer More Add-On Codes?

No. Closing the gap does not mean adding more codes. It means tying every code to a clinical justification documented during the visit. An add-on code billed without that justification brings more audit risk than revenue.

A defensible code is one the record can answer for:

Why was this service delivered? Which clinical finding supports it? Is it consistent with the diagnosis?

Those answers hold only if they are captured when the clinical information first appears, during the encounter. A justification reconstructed after the fact is incomplete and hard to defend.

Most documentation tools focus on making the note faster. But if a faster note still feeds coding and billing through a disconnected process, the problem isn't solved. Unsupported codes simply move to the next step, and the problem remains. Every other tool stops at the note. AIM doesn't.

How Does AIM Capture Add-On Services?

AIM captures add-on services from the encounter itself, together with their clinical justification. The process doesn't end at the note. The clinical information in the note carries through to coding and billing without a break. The pipeline begins during the visit. AIM turns the conversation between physician and patient into a structured clinical history in real time, with AIM Scribe as the entry point. The record forms once, at the source, and is never reconstructed after the fact. When the physician signs off on the history, AIM presents likely diagnosis codes for the physician's review. AIM then works from the history and the diagnoses to surface add-on services the encounter supports. Suggestions are limited to the code set defined for the relevant specialty. Each one comes with a justification that points to the clinical finding behind it, along with a confidence level. The physician reviews each suggestion and accepts or rejects it. Accepted codes enter the clinical assessment and the patient record with their justification attached. The pipeline doesn't stop there. Before anything reaches a claim, accepted codes are checked again against compliance rules, including whether the diagnosis and the procedure are consistent and whether the codes can be billed together. The service, the justification, the code and the claim all rest on the same clinical record.

Who Makes The Final Call On Add-On Codes?

The physician always makes the final call. AIM suggests codes and shows the reasoning behind each one, and no code enters the record until the physician accepts it. AIM is built on three principles:

• Assistive: supports the workflow rather than dictating decisions. • Auditable: every output can be reviewed, validated and governed. • Clinician-first: the physician stays in full control of the final clinical judgment and the record.

**AIM provides clinical decision support; it does not replace clinical decision-making.

What Does This Mean For Practice And Revenue Cycle Leaders?

Add-on revenue is lost in the exam room, not at the billing desk, so recovering it has to start in the exam room too. Much of the correction, appeal and resubmission work after a claim goes out is an attempt to rebuild a justification nobody wrote down during the visit. When the justification is captured during the visit, the organization gains twice. The care that was delivered appears on the claim, and the claim holds up under payer review because the record supports every code. Coding teams spend less time on retrospective fixes, and physicians spend less time on documentation and more with patients.

Accurate coding isn't administrative work layered on top of care. It is the natural continuation of the clinical record. The goal isn't to bill more codes. It is to make sure every service delivered is reflected in the record, so physicians can spend their time on proper diagnosis and patient care, not paperwork.

To see how AIM carries add-on services from the encounter to the claim in your own workflow, request a demo at aimdx.co.

Sources

  1. ECG Management Consultants. G2211 One Year Later: Adoption, Impact, and What Comes Next. Based on ECG's 2025 Physician and APP Compensation Survey (2024 CPT data, 20,000+ physicians, US).
  2. Centers for Medicare & Medicaid Services. MLN MM13473: How to Use the Office & Outpatient Evaluation and Management Visit Complexity Add-on Code G2211.