Run this number for your practice: 0.33. That is the work RVU attached to HCPCS G2211, the office/outpatient E/M add-on code Medicare began paying on January 1, 2024. Multiply 0.33 by the volume of established-patient visits your primary care and specialty clinicians bill in a year, and the g2211 rvu stops looking like a rounding error and starts looking like a line item your board will ask about.

This guide is written for the person who owns the billing workflow, not the person in the exam room. It covers how the g2211 rvu enters your fee schedule math, how practices build a defensible documentation and code-selection process, and — the part most billing articles skip — which vendors end up holding the protected health information that supports those claims, and what your contracts need to say about it.

What the G2211 RVU Actually Adds to a Claim

G2211 is an add-on code. It never stands alone. It is reported alongside an office or outpatient evaluation and management service (the 99202–99205 and 99211–99215 families) when the clinician documents that the visit reflects the complexity inherent to serving as the continuing focal point for a patient's care, or to ongoing care for a single serious or complex condition.

The g2211 rvu breakdown is small and consistent: 0.33 work RVUs, plus practice expense and malpractice components. When Medicare activated payment in 2024, the national non-facility allowed amount landed at roughly $16 per unit. Your actual rate depends on your locality's geographic practice cost indices and on the conversion factor in effect.

That last variable matters more in 2026 than it used to. This is the first payment year in which Medicare applies two separate conversion factors — one for qualifying alternative payment model participants and a lower one for everyone else. The same 0.33 work RVU therefore converts to different dollars for two clinicians in the same building depending on their APM status. Do not hardcode a payment amount into your fee schedule spreadsheet. Pull the current figure from the CMS Physician Fee Schedule Look-Up Tool for your locality and re-verify it every January.

Patient cost-sharing is not waived

G2211 is not a preventive service. Standard Part B deductible and coinsurance apply. A patient who has not met their deductible will see a separate charge on their statement for a code with no procedure attached to it, and your front desk will get the call.

Write the script now. Something plain: "That line reflects the ongoing coordination of your care with this practice, not a separate test or procedure. It's billed under Medicare rules and applies to your deductible like your office visit does." Put it in the phone-team binder before the first statement cycle, not after.

The Three Operational Rules Your Coders Need in Writing

Code selection is a clinician judgment applied to documented facts. Your job is not to decide when G2211 applies to a given patient — it is to build the process that makes the decision reviewable. Three operational rules belong in your written coding policy.

Rule one: the add-on follows an office/outpatient E/M only

G2211 attaches to the office and outpatient E/M families. It does not attach to hospital, emergency department, nursing facility, or other place-of-service E/M codes. Your claim-scrubbing edits should reject the pairing before the claim leaves the building, and your denial log should tell you whether those edits are actually firing.

Rule two: know the modifier 25 boundary

When Medicare first activated payment, G2211 was not payable when the associated office visit carried modifier 25. Effective in CY2025, CMS narrowed that restriction: payment is allowed when the modifier 25 office visit is furnished on the same day as an annual wellness visit, a Medicare Part B preventive service, or a vaccine administration. Other same-day modifier 25 scenarios remain outside that carve-out.

This is the single most common source of avoidable G2211 denials in practices that run wellness visits and immunizations at scale. Have your billing lead pull a 90-day sample of modifier 25 claims and confirm the scrubber logic matches the current policy rather than the 2024 version.

Rule three: documentation must support the relationship, not just the encounter

Auditors reviewing G2211 look for evidence in the note of the continuing or complex-condition relationship the code describes. Practices that survive review generally do two things: they train clinicians on what that evidence looks like in their own charting template, and they avoid template language that auto-populates identically across every patient. Identical justification text in 400 consecutive notes is a pattern reviewers find quickly.

Your compliance calendar should include a quarterly internal review — a sample of G2211 claims pulled by a coder who did not build them, scored against your written policy, with results reported to the physician leadership. Document the sample size, the reviewer, and the findings. That record is the artifact you produce when an external reviewer arrives.

Where the G2211 RVU Documentation Lives, and Who Will Ask for It

Every G2211 unit you bill creates a documentation obligation that outlives the payment by years. When a Medicare Administrative Contractor, Recovery Audit Contractor, or Unified Program Integrity Contractor issues an Additional Documentation Request, you will be sending complete progress notes — not a coding summary — for the sampled encounters.

That transmission is a disclosure of protected health information. It is permitted under HIPAA for payment and health care operations purposes, and it does not require patient authorization. But permitted is not the same as unmanaged. Three things need to be true before your first ADR arrives:

  • A named owner. One person, with a backup, responsible for assembling and transmitting audit responses. Not "whoever is at the front desk that week."
  • A defined transmission channel. Encrypted portal upload or secure file transfer, documented in your policy. Not personal email, not an unencrypted attachment, not a fax to a number nobody verified.
  • A disclosure log entry. Payment-related disclosures are generally excluded from the accounting of disclosures a patient can request, but your internal log should still record what left the building, when, to whom, and under what authority. You will want it if the request turns into something larger.

Apply the minimum necessary standard to the response. If the ADR asks for the encounter note and supporting documentation for three dates of service, send those. Do not export the full longitudinal chart because it is easier than filtering.

The Vendor List That Touches Your G2211 Claims

Here is where a billing code becomes a privacy problem. Trace one G2211 claim from the exam room to the remittance advice and count the third parties that handle the underlying PHI.

Your EHR host. Your clearinghouse. Your outsourced coding reviewers, if you use them. The revenue cycle management firm working your denials. The analytics platform your CFO bought to benchmark RVU productivity by clinician. The AI-assisted documentation or coding-suggestion tool your physicians started piloting, which ingests full note text to recommend E/M levels and add-on codes. The audit-defense consultant you retain on standby.

Every one of those is a business associate under HIPAA. Each requires an executed business associate agreement before it receives PHI — including the ones your clinicians adopted without routing through procurement. HHS is explicit about who qualifies as a business associate and what the agreement must contain, including breach notification timelines, permitted uses, subcontractor flow-down, and return or destruction of PHI at termination.

The pattern I see repeatedly: a practice adds a new denial-analytics or coding-optimization vendor specifically to capture more G2211 revenue, the vendor connects to the EHR through an API, and eleven months later nobody can produce a signed BAA. If your vendor list has grown faster than your contract file, you can generate a signature-ready business associate agreement through a six-step wizard and export it as PDF or DOCX — one-time purchase, no subscription — rather than waiting on outside counsel to redline a template you already know you need.

Questions to ask before a coding-assist vendor touches a note

  • Does the tool retain note text after generating a recommendation, and for how long?
  • Is any PHI used to train or tune models, and is that use restricted by contract?
  • Where is the data hosted, and are subcontractors bound by equivalent terms?
  • What is the contractual breach notification window, and does it let you meet your own 60-day obligation?
  • On termination, does the vendor return or destroy PHI, and will they certify it?

A 90-Day Rollout One Administrator Can Actually Run

Days 1–15 — Baseline. Pull 12 months of office/outpatient E/M volume by clinician. Calculate current G2211 attachment rate. Confirm your locality's current payment amount from the CMS lookup tool. Present the g2211 rvu opportunity as a range, not a promise.

Days 16–30 — Policy. Draft the written coding policy covering the three rules above. Route it through your compliance officer and a physician champion. Version it and date it.

Days 31–45 — Systems. Update charge capture, scrubber edits, and fee schedule tables. Test the modifier 25 carve-out logic with live claims in a test environment. Confirm the EHR template supports documentation without auto-populating identical language.

Days 46–60 — Training. Clinician session on documentation. Separate session for billing staff on edits and denials. Front-desk and phone-team script for the cost-sharing question. Log attendance.

Days 61–75 — Contracts. Reconcile the vendor inventory against executed BAAs. Close every gap. Note that this step almost always uncovers a tool nobody logged.

Days 76–90 — First review. Sample 25 G2211 claims. Score against the policy. Report findings. Set the recurring quarterly cadence.

Five Numbers to Put on the Monthly Dashboard

  1. Attachment rate by clinician. Wide variance between clinicians in the same specialty is a training signal, an over-application signal, or both. Investigate outliers in either direction.
  2. G2211 denial rate and top denial reason. Modifier conflicts and invalid base-code pairings should trend toward zero once edits are correct.
  3. Incremental work RVUs. Attachment volume × 0.33. This is the cleanest way to express the g2211 rvu impact to leadership, independent of conversion factor churn.
  4. Patient billing inquiries referencing the add-on. A spike means your statement language or your phone script is failing.
  5. Open ADRs and days outstanding. Missed response deadlines convert into automatic recoupments.

The Risk Analysis Connection Most Practices Miss

Adding vendors to chase the g2211 rvu changes your risk profile, and the HIPAA Security Rule requires your risk analysis to reflect the systems you actually run. A risk analysis that predates your current coding-assist tool, your new RCM partner, or your analytics platform is stale by definition.

Update it when the vendor list changes, not annually by habit. If your documentation set — risk analysis, policies, workforce training records — has fallen behind your operations, automated generation of the full compliance document set closes the gap faster than rebuilding it in a word processor. HHS does not certify or endorse any compliance product, including this one; what these tools produce is your documentation, and you remain accountable for its accuracy.

Your Next Two Actions

First, pull your locality's current G2211 payment from the fee schedule tool and correct any hardcoded amount sitting in your charge master. Second, list every third party that has touched a claim or a note in the last twelve months and match each one against your contract file.

If that second list turns up gaps — and it usually does — build the missing business associate agreements before your next audit request lands. Six steps, signature-ready export, one-time purchase. The revenue from the g2211 rvu is only worth capturing if the documentation and vendor contracts behind it hold up when someone asks to see them.