What CMS Expects in Your Medical Records for G-Code Billing
G-code denials are increasing, and documentation requirements are often unclear. This guide provides clarity on what CMS expects - and what your EMR might be missing.
What documentation does CMS require for G-code billing?
CMS G-code documentation requirements vary by code but generally require a dated clinical note, documentation of the specific service performed, patient eligibility confirmation, and clinician signature. Many codes also require evidence of findings, counseling, referrals, and follow-up plans. Inadequate documentation is the leading cause of G-code claim denials and post-payment audits.
The Provider's Challenge
While CPT codes have established documentation guidelines developed over decades, G-codes often do not. CMS creates G-codes to track policy initiatives, but documentation requirements may not be explicitly defined - leaving providers to interpret what's needed and auditors to determine if it's sufficient.
This creates a documentation paradox: providers don't know exactly what to document, but claims are still being denied. The solution is understanding the policy intent behind each G-code and documenting accordingly.
The Documentation Standard for G-Codes
The Core Principle
Documentation must prove the policy intent of the G-code.
G-codes exist because CMS needs to track, control, or incentivize specific types of care. Your documentation must demonstrate that the care provided aligns with why CMS created the code in the first place.
Documentation Should Show:
- ✔The specific service or assessment was performed
- ✔The service meets the G-code's policy requirements
- ✔Medical necessity for the service
- ✔Required elements are complete (if specified)
Documentation Failures:
- ✘Template-only entries without specifics
- ✘Missing required assessment elements
- ✘No evidence of longitudinal relationships
- ✘Incomplete care plans or interventions
The G2211 Example
CMS has explicitly stated: "We have not specified any additional medical record documentation requirements for reporting the HCPCS code G2211 add-on code."
Yet claims are being denied. Why? Because reviewers look for evidence that the practitioner serves as the "continuing focal point" for the patient's care - even though CMS hasn't told providers exactly how to document this. The documentation must implicitly prove the longitudinal relationship.
G-Code-Specific Documentation Guidance
G2211: E/M Complexity Add-on
HIGH RISKPolicy Intent:
Compensate for cognitive load of maintaining ongoing care relationships - either as the continuing focal point for all care needs OR for ongoing management of a serious/complex condition.
Documentation Should Demonstrate:
- ☐Longitudinal relationship: Reference prior encounters, ongoing management
- ☐Ongoing responsibility: Statement of continued care commitment
- ☐Care coordination: Evidence of coordinating across providers
- ☐Chronic/serious conditions: Documentation of conditions being managed
Sample Documentation Language:
"I am [patient name]'s primary care physician and serve as the continuing focal point for their healthcare needs. I have been managing their care continuously since [date]. Today's visit, while addressing [chief complaint], occurs in the context of my ongoing responsibility for their ongoing care including management of [conditions]."
G0438/G0439: Annual Wellness Visit
HIGH VOLUMEPolicy Intent:
Develop or update a personalized prevention plan based on thorough health risk assessment. CMS has defined specific required elements.
Required Documentation Elements (G0438 - Initial AWV):
Health Risk Assessment (HRA):
- ☐ Demographic data
- ☐ Health status self-assessment
- ☐ Psychosocial risks (depression, stress, loneliness)
- ☐ Behavioral risks (tobacco, physical activity, nutrition, alcohol)
- ☐ Activities of daily living (ADLs)
- ☐ Instrumental ADLs (IADLs)
Additional Required Elements:
- ☐ Medical and family history
- ☐ Current provider list
- ☐ Screening schedule (5-10 years)
- ☐ Risk factors and conditions identified
- ☐ Personalized prevention plan
Common AWV Documentation Failures:
- • HRA missing required domains (especially psychosocial/behavioral)
- • No personalized prevention plan documented
- • Confusing AWV with annual physical (different service)
- • Missing screening schedule
G0136: SDOH Assessment
EMERGINGPolicy Intent:
Screen for social determinants of health that affect patient outcomes and connect patients to appropriate resources or interventions.
Documentation Should Include:
- ☐SDOH screening tool used: Identify the specific instrument
- ☐Domains assessed: Food insecurity, housing, transportation, etc.
- ☐Findings documented: Specific needs identified
- ☐Interventions/referrals: Actions taken based on findings
- ☐Follow-up plan: How needs will be addressed
Common SDOH Screening Tools:
- • PRAPARE (Protocol for Responding to and Assessing Patients' Assets, Risks, and Experiences)
- • AHC HRSN Screening Tool (Accountable Health Communities)
- • SDOH-focused portions of validated instruments
G0320/G0321: Telehealth Home Health
TELEHEALTHPolicy Intent:
Enable remote care delivery for home health patients, integrated with overall care plan and documented appropriately.
Documentation Should Include:
- ☐Telehealth platform: Technology used for encounter
- ☐Duration: Time spent in telehealth encounter
- ☐Clinical content: What was addressed during the encounter
- ☐Care plan integration: How it relates to home health plan
- ☐Patient location: Confirmation patient was at home
The EMR Gap: Why Your Software May Be Failing You
Most Electronic Medical Record (EMR) systems were designed for CPT codes, not G-codes. This creates documentation gaps that lead to denials - even when providers believe they've documented appropriately.
Documentation Prompts Missing
EMR templates often don't include prompts for G-code-specific documentation. Providers complete visits correctly but fail to capture the evidence CMS requires because their software doesn't ask for it.
Example: G2211 requires evidence of longitudinal care. Most EMRs don't prompt for statements about ongoing responsibility or reference to prior encounters demonstrating continuity.
Export Quality Issues
When records are exported for appeals or audits, G-code-related documentation may not be included in standard exports. Critical information can be scattered across different system modules or lost entirely.
Auto-Coding Risks
Automated coding suggestions may apply G-codes inappropriately based on incomplete logic. This leads to claims being submitted without proper documentation to support them.
Longitudinal View Challenges
G-codes like G2211 require evidence spanning multiple encounters. Many EMRs are designed for discrete visit documentation, making it difficult to demonstrate care continuity over time.
EMR Evaluation Checklist
Assess whether your EMR supports proper G-code documentation:
- ☐Does it have templates or prompts for each G-code you bill?
- ☐Can it capture all required AWV elements (HRA, prevention plan, etc.)?
- ☐Does it support SDOH screening documentation?
- ☐Can exports include all G-code documentation for audits?
- ☐Does it show longitudinal care history easily?
- ☐Are auto-coding suggestions reviewed for appropriateness?
Preparing for a CMS Audit
G-codes face higher audit scrutiny than CPT codes. Proactive preparation is essential to avoid costly post-payment denials and recoupments.
Audit Preparation Checklist
Review G-Code Claims History
Pull a report of all G-code claims from the past 12-24 months. Identify volume, denial rates, and patterns.
Sample Medical Records
Pull a random sample (10-20 charts per G-code) and verify documentation meets requirements. Use the checklists in this guide.
Identify Documentation Patterns
Are there consistent gaps across charts? Are certain providers or templates associated with weaker documentation?
Implement Corrective Actions
Update EMR templates, train staff, create documentation checklists. Address gaps before auditors find them.
Ongoing Monitoring
Establish regular chart reviews for G-code compliance. Don't wait for audits to identify problems.
High-Risk Audit Triggers
These patterns may increase audit likelihood:
- ⚠G2211 billed on high percentage of E/M visits
- ⚠Billing patterns significantly above peers in same specialty
- ⚠Rapid increase in G-code utilization
- ⚠High AWV volume relative to patient panel
- ⚠New G-codes with unclear documentation (like G2211)
Key Takeaways
- 1.Documentation must prove policy intent, not just that a service occurred.
- 2.G-code requirements vary significantly. Know the specific requirements for each code you bill.
- 3.Your EMR may have gaps. Evaluate whether it supports G-code-specific documentation.
- 4.Audit before you're audited. Proactive chart review identifies problems early.
- 5.Consult your MAC. Documentation requirements may vary by jurisdiction.
This content is for informational purposes only and does not constitute legal, medical, or billing advice. Documentation requirements may vary by MAC jurisdiction. Consult with qualified billing professionals for coding decisions. Last updated: December 2025.