G2211 Add-On Billing With Modifier 25 on Preventive Days

G2211 pairs with modifier 25 on preventive visit days under 2025–2026 CMS rules.
This brief maps audit-ready logic to protect $15,600+ in annual complexity capture.
Human-attested clinical metrics prevent NCCI modifier 25 recoupment and SB 1120 clawbacks.

G2211 Add-On Billing With Modifier 25 on Preventive Visit Days: A Clinical Documentation Playbook

Merry AI · Thoughtfully curated clinical briefs.

• Jump to: Loaded Labor Model
• Jump to: Clinical Logic & Audit Defense
• Jump to: ICD-10 Documentation Standards
• Jump to: Preventive-Day Workflow Wedge
• Jump to: Chrome Extension DOM Overlay
• Jump to: Clinical Intelligence Layer

Starting January 1, 2025, CMS permits G2211 reporting alongside office E/M services billed with modifier 25 on the same day as an Annual Wellness Visit or other Part B preventive service. This brief examines what that permission actually requires at the documentation layer, and where Merry AI fits into it.

The reimbursement exists on paper. Whether a practice retains it depends on human-attested clinical specificity that survives downstream review. Merry AI treats that gap as the central problem this playbook is organized around.

The Loaded Labor & Denominator Model

A fully loaded medical assistant costs roughly $48,000 annually once benefits, payroll tax, and supervision overhead are counted. That is the honest denominator for any documentation decision.

Merry AI Pro runs $648 per year, or 1.3% of that loaded labor cost. The question is not price. The question is whether the documentation layer recovers what preventive-day billing leaves on the table.

Clinicians recover 2.1+ hours daily per provider, consistent with documentation-burden benchmarks published in NIH National Library of Medicine Research. That recovered time is the second denominator practices routinely ignore.

Clinical Logic & Audit Defense

CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.

Consider a Medicare primary care group seeing a patient for an Annual Wellness Visit while also managing uncontrolled diabetes and hypertensive heart disease during a separately identifiable E/M. Merry AI drafts the note, attaches modifier 25 logic to the problem-oriented E/M, and identifies the AWV as a CMS-allowed preventive exception for G2211.

The draft then builds an audit-ready paragraph explaining the ongoing longitudinal care relationship. That paragraph is what prevents preventable G2211 write-offs and downstream modifier 25 recoupment risk.

Audit defense rests on specificity. A generic "diabetes managed" note does not demonstrate the separately identifiable service that modifier 25 asserts. The clinician must attest to measurable clinical facts.

SB 1120 requires clinician review of AI-assisted documentation before it enters the record. Merry AI drafts; the clinician attests. That sequence is what defeats NCCI modifier 25 clawbacks, not the draft alone.

Longitudinal relationship language matters. The CMS preventive services guidance ties G2211 to sustained care partnership. The note must state that partnership explicitly.

Clinical Taxonomy: ICD-10 Documentation Standards

Diagnosis coding carries the audit. Vague codes undermine the separately identifiable claim that modifier 25 and G2211 together assert on a preventive day.

Code to the attested reality. If the clinician documents uncontrolled disease with organ involvement, E11.9 and I10 are often insufficient. Reference the E11.9 (ICD-10-CM) taxonomy before finalizing.

Supporting evidence remains reviewable. See NIH National Library of Medicine Research for the clinical basis of complexity-based coding.

Original Insight: The Preventive-Day Workflow Wedge Competitors Missed

The CMS quick-reference chart confirms eligibility but stops at the billing rule. It never addresses the documentation sequence that determines whether the claim holds under review. That is the gap.

Anchor truth: eligibility is not retention. Knowing G2211 is billable on an AWV day does nothing if the note fails to demonstrate the separately identifiable E/M. Competitors documented the permission and omitted the proof.

The 2026 home E/M expansion matters. G2211 now attaches to CPT 99341–99350. The same documentation discipline applies to the residence setting, a point the chart lists but does not operationalize.

FHIR interoperability changes the retrieval step. Pre-visit relationship context now pulls across exchange networks, which strengthens the longitudinal-partnership attestation G2211 depends on.

Explore specialty-specific variations in the Specialty Clinical Playbook Library.

Chrome Extension DOM Overlay & EHR Field Injection

Merry AI runs as a browser-native layer. The extension reads and writes directly to EHR fields through a DOM overlay, requiring zero IT setup or vendor integration contract.

Closed EHR systems remain compatible. Field injection operates at the browser rendering layer, so platforms without open APIs still receive drafted, attestation-ready notes.

PHP and IOP groups split cleanly. As documented in the Path Recovery TN case study, the overlay separates group session content into individual participant notes, preserving the separately identifiable record each chart requires.

Review supported platforms in the EHR Clinical Integration Directory.

Clinical Intelligence Layer: Closed-Pilot Orchestration

Orchestration spans the full visit. Pre-visit, Merry AI surfaces prior longitudinal context supporting the G2211 relationship claim. During the visit, it drafts the problem-oriented E/M alongside the preventive service.

Post-visit, the layer assembles the modifier 25 rationale and the audit-ready longitudinal paragraph for clinician attestation before submission.

The Practice Partner plan at $149 adds closed-pilot orchestration for multi-provider groups, with five outpatient practices selected weekly for direct solutions engineering. Review terms at Merry AI Practice Partner Plans.

The permission already exists. What remains is documentation that holds when a reviewer reads it twice. That is the work this playbook is built around.