Billing G2211 With 2026 Home Visit Codes 99341 Through 99350: The Operations Playbook

This playbook is for Practice Administrators and CMOs running home-based primary care, house-call, assisted-living, and longitudinal outpatient programs. It explains how the CY2026 expansion of HCPCS G2211 to home and residence E/M services changes documentation, edits, and revenue integrity. Scribing.io built its Clinical-Grade Scribing workflows around this rule change, and this guide reflects that implementation work.

The core rule is simple: starting January 1, 2026, G2211 attaches to home or residence E/M codes 99341 to 99350 when documentation shows a longitudinal relationship and a medically necessary base visit. Making that rule hold up on post-payment review is harder. Below, Scribing.io and its Merry AI engine show how to produce defensible evidence for every claim, not just a billing flag.

• What Changed on January 1, 2026

• Home and Residence Code Eligibility Matrix

• The Longitudinal Evidence Standard

• Scenario One: Home Visit 99350 With G2211

• Scenario Two: Behavioral Health IOP Group Notes

• Scenario Three: Cardiology Same-Day Procedure and Modifier 25

• Denial Patterns and Pre-Bill Edits

• EHR Integration and FHIR Write-Back

• 30-60-90 Day Implementation Roadmap

• Revenue Modeling for Administrators

• Frequently Asked Questions

What Changed on January 1, 2026

CMS extended the complexity add-on beyond office and outpatient E/M (99202–99215) to the home and residence family. The CY2026 Physician Fee Schedule recognizes that home-based clinicians often carry the heaviest longitudinal burden in Medicare. Until this year, those clinicians could not report G2211 at all.

The add-on describes a relationship, not a visit's difficulty. CMS defines it as the work tied to being the continuing focal point for all needed services, or ongoing care for a single serious or complex condition. Medical decision making and time still select the base code; G2211 captures the longitudinal dimension.

Key Facts at a Glance

Medical Director's note on payers: Medicare Advantage and Medicaid plans adopt G2211 on their own timelines. Load payer-specific rules into your scrubber before assuming Traditional Medicare logic applies. Current state rules are tracked in our AI scribe compliance and law library.

Home and Residence Code Eligibility Matrix

New and established patients both can qualify for G2211. CMS has stated that new-patient status does not disqualify the add-on when the documented intent is an ongoing relationship. Auditors will still look harder at a first visit, so the plan of care must state that intent explicitly.

Specialty-specific pairing guidance lives in the Specialty Clinical Playbook Library. Home-based programs should also review the home-based primary care specialty page for template configurations.

The Longitudinal Evidence Standard

Auditors ask one question: does the record show this clinician is responsible for the patient over time? A diagnosis list does not answer it. Evidence of ongoing management over months does.

Five Evidence Elements Merry AI Extracts

1. Twelve-month encounter history summary: dates, rendering clinician, and visit type showing a continuous relationship.

2. Medication titration trail entries: dose changes with reasons, such as diuretic adjustments tied to weight trends.

3. Care-plan revision timestamps logged: goals modified across visits, not copied forward unchanged.

4. Coordination with other clinicians: specialist referrals, home health orders, and results reconciled by this practitioner.

5. Forward-looking management plan stated: next visit interval and the conditions that will be managed at it.

What Does Not Qualify

• Single-problem episodic visits documented: a one-time wound check with care handed back to another practice.

• Copied-forward plan text blocks: identical plan language across visits invites cloned-note findings.

• Relationship asserted without evidence: "patient followed longitudinally" with no supporting history fails review.

Scenario One: Home Visit 99350 With G2211

A home-based primary care team sees an 82-year-old homebound patient with chronic systolic heart failure, I50.22 (ICD-10-CM), and type 2 diabetes, E11.9 (ICD-10-CM). The visit involves a 3-pound weight gain, a furosemide change, and a decision to avoid hospitalization. High MDM supports 99350.

The billing gap was documentation: before 2026, the team could not report G2211 in the home. Now they can, but their notes described the visit, not the relationship. A payer reviewing 99350 + G2211 would see a strong base visit and an unsupported add-on.

How Merry AI Builds the Rationale

1. Ambient capture during visit: Ambient Clinical Intelligence records the weight, symptoms, and diuretic decision in structured fields.

2. Chart history query runs: Merry AI retrieves 12 months of encounters, showing 11 home visits by the same NP-physician team.

3. Titration trail is assembled: four furosemide adjustments and one metformin dose change, each with date and indication.

4. Care-plan revisions are cited: two goal updates, including a revised A1c target appropriate to frailty.

5. Attested rationale is drafted: a G2211 statement citing the above is presented for clinician attestation.

6. One-click EMR injection completes: the attested note and code pair write back to the chart and charge.

Sample attested G2211 rationale: "I serve as the continuing focal point for this patient's care, including 11 home visits over 12 months, ongoing diuretic titration for I50.22, and glycemic management for E11.9. Today's plan revises volume targets and schedules reassessment in 7 days."

The outcome is measurable: clean-claim rates rise because the scrubber sees an eligible pairing and supporting language. Post-pay denials fall because the record already answers the auditor's question. The clinician spends seconds reviewing, not minutes writing.

Scenario Two: Behavioral Health IOP Group Notes

G2211 does not attach to psychotherapy codes such as 90853 group therapy. It applies only to E/M services. Behavioral health programs still face the same underlying audit risk, though: proving individualized care in high-volume settings.

A therapist runs a 3-hour IOP group with 10 attendees. Writing 10 distinct notes after a session is where cloned text enters the record. Joint Commission surveyors flag identical narrative blocks as evidence that individualized care was not documented.

Merry AI Group Note-Splitting Workflow

1. Speaker attribution during session: the system tags each participant's contributions and the therapist's interventions per person.

2. Individual notes are generated: 10 notes, each with that patient's statements, response to intervention, and treatment-plan goals.

3. Shared content is scoped: the group topic appears once as context, never as the clinical substance of the note.

4. Similarity check runs before signing: notes exceeding a text-overlap threshold are flagged for therapist revision.

5. One-click Kipu injection follows: all 10 signed notes post to each patient's record in Kipu.

Program-level configuration details are on the behavioral health specialty page. Where a psychiatric prescriber provides a same-day E/M to an IOP patient, that E/M can carry G2211 if the longitudinal evidence standard is met.

Scenario Three: Cardiology Same-Day Procedure and Modifier 25

A cardiologist performs a same-day E/M and a separately billable procedure. The E/M carries Modifier 25. This is where G2211 logic must actively suppress the add-on, because CMS still does not pay G2211 when Modifier 25 accompanies a procedure.

The larger risk is Modifier 25 itself. An audit sampling 30 claims with thin separate-service documentation can extrapolate to a $15,600 clawback. The E/M must show decision making beyond the procedure's inherent pre-service work.

The Clinical Logic Bridge

Merry AI constructs a bridge linking the E/M to clinical facts independent of the procedure. In this case it cites an LVEF of 35% on recent echo and a failed trial of guideline-directed medication due to symptomatic hypotension. The note documents a separate decision to restructure the heart failure regimen.

Cardiology template settings are documented on the cardiology specialty page. The same suppression rule protects home-based teams who perform same-day procedures such as joint injections.

Denial Patterns and Pre-Bill Edits

Most G2211 denials are predictable. They come from invalid code pairs, missing relationship language, or payer policies that lag CMS. Build these edits into your scrubber before the first 2026 claim drops.

• Track G2211 attachment rate monthly: a sudden spike to near 100% across all clinicians draws payer analytics attention.

• Audit ten charts per clinician: quarterly internal review catches drift before an external auditor does.

• Map diagnoses to chronicity correctly: use the ICD-10 clinical reference to confirm codes reflect managed chronic conditions.

EHR Integration and FHIR Write-Back

The rationale only protects revenue if it lands in the legal medical record and the charge in the same transaction. Copy-paste between systems breaks the audit trail. Scribing.io writes back through native APIs and FHIR R4 resources.

• DocumentReference carries the note: the attested G2211 rationale is stored as part of the signed encounter document.

• ChargeItem or vendor API posts codes: base E/M and G2211 post together, preventing orphaned add-ons.

• Provenance resource logs attestation: who reviewed the AI draft, when, and what changed.

• Encounter history queried via FHIR: prior visits and MedicationRequest changes feed the longitudinal evidence.

Supported systems and connection methods are listed in the EHR Clinical Integration Directory. Home-based programs on Epic, athenaOne, eClinicalWorks, and behavioral health programs on Kipu can review setup steps at our integration hub.

30-60-90 Day Implementation Roadmap

Days 1–30: Rules and Baseline

1. Load 2026 code pairs: add 99341–99350 G2211 pairings and remove 99346 everywhere.

2. Configure payer allow lists: confirm each MA and Medicaid plan's G2211 status in writing.

3. Pull a documentation baseline: sample 50 home visits and score them against the five evidence elements.

Days 31–60: Workflow Deployment

1. Activate Merry AI rationale drafting: start with two clinicians who carry the largest home panels.

2. Train on attestation discipline: clinicians must edit, not rubber-stamp, the drafted rationale.

3. Script front-desk coinsurance conversations: explain the add-on before the first statement arrives.

Days 61–90: Measurement and Scale

1. Measure clean-claim rate change: compare G2211 first-pass acceptance against the 30-day baseline.

2. Run internal audit sample: ten charts per clinician, scored by compliance, not by billing.

3. Expand to full team: roll out once attestation quality and denial rates meet targets.

Revenue Modeling for Administrators

The per-claim value is modest. The panel-level value is not, particularly in home-based programs where nearly every established patient meets the longitudinal standard. Model conservatively using locality-adjusted rates.

Denial avoidance belongs in the model. A single extrapolated clawback can erase a year of add-on revenue for a small practice. Plan comparisons for practices of each size are on the Merry AI Practice Partner Plans page and the Scribing.io pricing page.

Administrator's decision point: target defensible attachment, not maximum attachment. An 80% rate backed by attested evidence outperforms 100% with thin notes.

Frequently Asked Questions

Can G2211 be billed on a new home visit?

Yes, with explicit intent. The note must state that the practitioner is assuming ongoing responsibility and outline the longitudinal plan. Expect more scrutiny than on established visits.

Does G2211 apply in assisted living?

Yes, under residence codes. Assisted living (POS 13) and group home (POS 14) visits billed with 99341–99350 are eligible when the evidence standard is met.

What if the visit includes a procedure?

G2211 is not payable then. When the E/M carries Modifier 25 for a same-day procedure, remove the add-on. The exceptions are AWV, vaccine administration, and Part B preventive services.

Does AI-drafted rationale satisfy auditors?

Only after clinician attestation. The clinician remains responsible for the record. Medical AI Scribing drafts the evidence; the signing clinician confirms it is accurate and edits where needed.

Where can teams see the workflow?

Open the clinical interface directly. The Merry AI Clinical Interface shows the G2211 rationale drafting, group note-splitting, and Clinical Logic Bridge workflows. Additional rule commentary is published on the Scribing.io clinical operations blog.

The 2026 expansion rewards documentation that reflects how home-based clinicians already practice. Programs that capture longitudinal evidence at the point of care will collect the add-on and keep it. Those that append codes without evidence will return it on review.