Clinical workflow
G2211 Attestation Language That Survives Medicare Audits
Learn the four-element G2211 note language that withstands MAC, UPIC, and RAC post-payment audits for longitudinal complexity visits.
G2211 Attestation Language That Survives Medicare Post-Payment Audits
Merry AI · Thoughtfully curated clinical briefs.
G2211 attestation language survives a Medicare post-payment audit when the visit note states four things in patient-specific terms: (1) the longitudinal relationship, (2) the single serious or complex condition being managed, (3) the treatment plan carried forward over time, and (4) the next scheduled loop of care. CMS does not require a separate attestation statement for HCPCS G2211. However, auditors at Medicare Administrative Contractors (MACs), Unified Program Integrity Contractors (UPICs), and Recovery Audit Contractors (RACs) test whether the medical record shows that the billing practitioner is the continuing focal point of care or is providing ongoing care for a serious or complex condition. Notes that only repeat the code descriptor fail that test.
Clinically reviewed by [Name, MD, FACC: board-certified cardiologist] · Coding review by [Name, CPC, CRC] · Last reviewed: January 2026 · Sources: CY 2026 Physician Fee Schedule Final Rule (90 FR 49266), MLN MM13272, MLN MM13473.
G2211 survives audit when four elements appear in patient-specific language
Auditors read the note, not the claim line. A post-payment reviewer has the encounter documentation, the problem list, and the patient's claims history with your Tax Identification Number. If those sources do not establish an ongoing relationship tied to a defined condition, the reviewer can deny G2211 even when the base E/M code is fully supported.
The four required elements are the same in every specialty:
- The relationship: who you are to this patient (continuing focal point, or ongoing manager of one serious or complex condition) and since when.
- The condition: the specific diagnosis, coded to the highest specificity, with current status (stable, progressing, exacerbated, treatment side effects).
- The plan: what you are titrating, monitoring, or coordinating, and why it requires continuity rather than a one-time opinion.
- The next loop: the dated or interval-defined follow-up, pending results you own, and who acts on them.
Audit rule: name the relationship, condition, plan, and next loop every time.
CMS pays G2211 for relationship-based complexity, not visit difficulty
The official G2211 descriptor reads: "Visit complexity inherent to evaluation and management associated with medical care services that serve as the continuing focal point for all needed health care services and/or with medical care services that are part of ongoing care related to a patient's single, serious condition or a complex condition." The complexity CMS pays for is the cognitive load of owning a longitudinal relationship. It is not the difficulty of a single encounter, which the base E/M level already captures.
Outpatient specialists qualify under the second clause. A cardiologist managing heart failure, a rheumatologist managing rheumatoid arthritis on a biologic, or a nephrologist managing chronic kidney disease stage 4 is providing "ongoing care related to a patient's single, serious condition or a complex condition." Specialists do not need to be the patient's primary care physician to bill G2211.
The first visit can qualify when the record documents intent to establish ongoing care. CMS has stated that the relationship, not the number of prior visits, determines eligibility. A new patient consult (99204 or 99205) that ends with "I will assume ongoing management of this patient's HFrEF with follow-up in 4 weeks" supports G2211. A consult that ends with "Return to referring physician, no specialty follow-up needed" does not.
CMS confirmed in MLN MM13272 that no additional documentation beyond the E/M visit is formally required, and that diagnoses, the assessment and plan, and claims history can serve as supporting documentation. In practice, that means the assessment and plan carries the entire audit burden. If the plan is thin, the claim is thin.
Modifier 25 blocks G2211 except with AWV, vaccines, or preventive services
G2211 is not payable when the base office or outpatient E/M visit carries modifier 25, with defined exceptions. Beginning in CY 2025 (detailed in MLN MM13473) and continued in the CY 2026 PFS Final Rule, CMS pays G2211 on a modifier 25 E/M when the other same-day service is an Annual Wellness Visit, a vaccine administration, or any Medicare Part B preventive service.
Minor procedures still block payment. If a dermatologist bills 99214-25 plus a destruction code, or an orthopedist bills 99213-25 plus a joint injection (20610), G2211 will deny on that claim. Billing it anyway generates an automatic edit failure and, in volume, a pattern a UPIC can flag for review.
The CY 2026 PFS Final Rule (90 FR 49266) also extends G2211 eligibility to home or residence E/M visits (99341 through 99350). Specialists who see homebound heart failure or advanced CKD patients should apply the same four-element documentation standard to those encounters.
Edit check: modifier 25 plus a minor procedure means no G2211.
Four-part attestation language: relationship, condition, plan, and next loop
Use structured, variable-filled language rather than a static macro. The template below is a scaffold. Every bracketed field must be populated with patient-specific facts at each visit, or the language becomes cloned text.
Longitudinal relationship (G2211): I have managed this patient's [condition] since [month/year] and serve as the ongoing treating [specialty] for this condition. Today's visit is part of continuing longitudinal care, not a self-limited or episodic problem.
Condition status today: [Diagnosis with ICD-10-CM code] is [stable / progressing / exacerbated / complicated by treatment side effects], as evidenced by [objective finding: lab, imaging, vital sign, functional class].
Longitudinal plan: I am [titrating / monitoring / coordinating] [specific therapy] toward [defined target], which requires serial reassessment over [interval]. Coordination today with [PCP, pharmacy, device clinic, other specialist] regarding [specific item].
Next loop: Follow-up in [interval] for [specific reassessment]. I will review [pending test] on [date or interval] and adjust [therapy] based on results.
Each sentence answers one audit question. The relationship sentence answers "Is this provider the continuing focal point?" The status sentence answers "Is the condition serious or complex?" The plan sentence answers "Does management require continuity?" The next-loop sentence answers "Is the relationship actually ongoing?"
Worked example: chronic HFrEF (I50.22) attestation that withstands UPIC review
The clinical scenario is common in outpatient cardiology. A 71-year-old Medicare beneficiary with chronic systolic heart failure, coded I50.22 (ICD-10-CM), returns 3 weeks after a sacubitril/valsartan dose increase. LVEF on the most recent echo was 30%. Potassium is 4.9 mmol/L and creatinine rose from 1.3 to 1.5 mg/dL. NYHA class improved from III to II. The cardiologist bills 99214 plus G2211.
A failing note reads like this: "Patient seen for ongoing care of complex condition. G2211 applies. Continue current meds. RTC 3 months." Every element is generic. Nothing identifies the relationship's start, the condition's status, the plan's longitudinal nature, or the specific next action.
A defensible note reads like this:
Longitudinal relationship (G2211): I have managed this patient's chronic HFrEF since March 2024 as the treating cardiologist and direct all guideline-directed medical therapy (GDMT) titration.
Condition status today: Chronic systolic heart failure (I50.22), LVEF 30% on echo dated 11/2025. Symptoms improved from NYHA III to II after sacubitril/valsartan increase to 49/51 mg BID. Creatinine 1.5 mg/dL (baseline 1.3) and K+ 4.9 mmol/L, consistent with expected hemodynamic effect; no hold criteria met.
Longitudinal plan: Continue sacubitril/valsartan 49/51 mg BID; defer uptitration to 97/103 mg until BMP confirms renal stability. Spironolactone 25 mg held at current dose given K+ 4.9. Dapagliflozin 10 mg continued. Target is maximally tolerated quadruple GDMT, followed by repeat echo to reassess ICD candidacy. Discussed BMP timing with PCP office.
Next loop: BMP in 10 days; I will review and decide on uptitration. Return in 4 weeks. Repeat echocardiogram after 3 months on optimized GDMT to determine primary prevention ICD eligibility.
This note supports both codes independently. The 99214 rests on moderate MDM: one chronic illness with side effects of treatment, review of labs, and prescription drug management. G2211 rests on the documented longitudinal ownership of GDMT titration and the defined ICD decision point months away. An auditor can trace a clear line from March 2024 to a future echocardiogram.
Key signal: a future decision point you own proves the relationship is ongoing.
Comparison table: clinical indicators, MDM thresholds, and audit defenses
G2211 has no MDM floor, but MDM context shapes how defensible the add-on looks. The table maps common specialty scenarios to eligibility and the documentation that defends them.
| Clinical indicator | Typical MDM problem element (2021+ E/M) | G2211 eligible? | Audit defense language |
|---|---|---|---|
| HFrEF on active GDMT titration (I50.22) | Moderate: chronic illness with side effects of treatment | Yes | Name titration target, lab monitoring, and dated next decision point |
| Rheumatoid arthritis on biologic, stable | Low to moderate: stable chronic illness with drug requiring intensive monitoring for toxicity | Yes | Document monitoring labs owned by specialist and infection risk surveillance |
| CKD stage 4 with anemia and bone-mineral disorder | Moderate: two or more stable chronic illnesses | Yes | State dialysis planning timeline and coordination with access surgeon |
| One-time second-opinion consult, returned to referrer | Varies | No | Do not bill; record shows no intent for ongoing care |
| Acute self-limited problem seen by specialist | Minimal: self-limited or minor problem | No | Do not bill; condition is not serious or complex |
| E/M with modifier 25 plus joint injection or lesion destruction | Varies | No | Claim edit denies; bill base E/M and procedure only |
| E/M with modifier 25 plus AWV, vaccine administration, or Part B preventive service | Varies | Yes (CY 2025 onward) | Document longitudinal elements separately from preventive service content |
| Home or residence E/M (99341 through 99350) for homebound HF patient | Moderate to high | Yes (CY 2026 PFS Final Rule) | Same four-element language plus homebound context and caregiver coordination |
| Postoperative visit within global surgical period | Not separately reported | No | Visit is bundled into the global package; no separate E/M exists |
Cloned attestation text invites denial because auditors test patient specificity
Identical sentences across many notes are the easiest pattern for a reviewer to detect. CMS program integrity guidance has long treated cloned documentation as insufficient to establish medical necessity for the individual encounter. A G2211 statement copied word for word into 400 notes demonstrates a template, not a relationship.
Post-payment exposure can extend beyond the sampled claims. Under Section 1893(f)(3) of the Social Security Act, Medicare contractors may use statistical sampling and extrapolation when a sustained or high level of payment error exists. A modest per-claim add-on multiplied across a multi-year lookback can produce a material overpayment demand.
Three practices reduce cloning risk:
- Change at least one objective value per visit (lab, vital sign, functional class, imaging finding) inside the status sentence.
- Tie the plan to a named therapy and measurable target, not "continue current management."
- Date the next loop or define its interval and the specific decision it informs.
Cloning test: if the sentence fits any patient, rewrite it.
Twenty weekly G2211 claims recover $15,600+ in annual revenue
G2211 pays approximately $16 per qualifying claim at the national average, with locality adjustments. A specialist who appropriately captures G2211 on roughly 19 to 20 longitudinal visits per week recovers $15,600+ in annual revenue that is otherwise left unbilled. For specialists with large chronic panels (heart failure, rheumatology, nephrology, endocrinology, neurology), that volume represents a fraction of eligible encounters.
Recovered revenue only holds if it survives review. A claim paid and later recouped with interest is a net loss once appeal time is counted. The four-element language is what converts billed G2211 into retained G2211. For the base-code side of this equation, see wRVU Compensation Thresholds and Undercoded E/M Visits.
Merry AI Pro costs 1.3% of a $48,000 fully loaded MA
Documentation labor is the real constraint. A fully loaded medical assistant costs a practice approximately $48,000 per year in wages, benefits, and payroll overhead. Merry AI Pro costs $54 per month on annual billing, or $648 per year, which equals 1.3% of that labor denominator.
Merry AI drafts the four elements from the encounter itself. The ambient scribe captures the relationship history, the objective status values discussed, the titration plan, and the follow-up interval, then structures them into the relationship, condition, plan, and next-loop format. Because each draft is generated from that visit's conversation, the language varies with the clinical facts rather than repeating a macro.
The physician remains the attesting author. Every AI-drafted assessment and plan requires clinician review and signature before claim submission. Compare plan tiers at Merry AI Practice Partner Plans.
Benchmark: $648 per year against a $48,000 MA equals 1.3%.
State AI scribe laws require physician review of AI-drafted documentation
State statutes increasingly govern AI in clinical documentation and utilization decisions. Requirements vary by state and can include patient disclosure of AI use, clinician review of AI-generated content, and limits on automated medical necessity determinations. Track current state requirements at the State AI Scribe Rules & Statutory Compliance Hub.
For G2211 specifically, the signing physician attests that the longitudinal relationship exists. An AI system can structure that language, but it cannot establish the relationship. Treat every draft as a proposal that the clinician confirms against the facts of care.
Pre-submission checklist for every G2211 claim
- Base code is eligible: office or outpatient E/M (99202 through 99215) or, from CY 2026, home or residence E/M (99341 through 99350).
- Modifier 25 is absent, or the same-day service is an AWV, vaccine administration, or Part B preventive service.
- Relationship sentence names start date and your role in ongoing care.
- Condition is coded to specificity (for example, I50.22 rather than I50.9) with today's status.
- Plan names a therapy, a target, and why continuity is required.
- Next loop is dated or interval-defined and tied to a specific decision.
- At least one objective value differs from the prior note.
Frequently asked questions about G2211 audit defense
Does CMS require a separate G2211 attestation statement?
No, CMS does not require a separate attestation. MLN MM13272 states that the E/M documentation, diagnoses, assessment and plan, and claims history can support the add-on. A structured statement is a best practice that makes the longitudinal relationship explicit for reviewers.
Can a specialist bill G2211 on a new patient visit?
Yes, when the note documents intent to provide ongoing care for a serious or complex condition. The note should state that the specialist is assuming longitudinal management and define the next follow-up.
Is G2211 payable with modifier 25 in 2026?
Only in defined circumstances. G2211 is payable on a modifier 25 E/M when the other same-day service is an Annual Wellness Visit, vaccine administration, or Medicare Part B preventive service. It is not payable when modifier 25 is used for a same-day minor procedure.
Does G2211 require moderate or high MDM?
No, G2211 has no MDM threshold. It may be reported with any level of eligible E/M visit when the longitudinal relationship criteria are met. Higher MDM often accompanies serious conditions, which can strengthen the overall record.
What triggers a G2211 post-payment review?
Common risk patterns include high utilization relative to specialty peers, G2211 billed on self-limited problems, G2211 billed with modifier 25 procedure claims, and identical documentation across many encounters. Contractors may extrapolate findings when payment error is sustained or high.
How long can Medicare look back on G2211 claims?
Lookback periods vary by contractor and circumstance. RACs generally review claims within 3 years of the paid date, and the 60-day overpayment rule requires providers to report and return identified overpayments within a 6-year lookback. Documentation must remain defensible for that full window.