Telehealth coding documentation in 2026 requires a different compliance approach than the pandemic-era flexibilities most providers grew accustomed to. With the Public Health Emergency (PHE) ended, CMS has finalized new permanent telehealth rules that vary by payer, location, and service type. Proper telehealth coding documentation now demands specific originating site details, audio-visual confirmation, state licensure verification, and modifier discipline that many coding teams weren't trained to capture. This checklist walks you through the compliance requirements, state-by-state variations, and documentation templates you need to code telehealth encounters correctly and avoid denials.
Core documentation requirements for telehealth claims in 2026
Every compliant telehealth claim starts with four foundational documentation elements. Miss any one of these and you're looking at a denial or compliance flag.
Provider location and credentials. Your documentation must specify where the provider was physically located during the encounter, confirm they hold an active license in the state where the patient is located, and note any interstate compact participation if applicable. CMS and commercial payers now audit this aggressively after PHE waivers expired.
Patient location and originating site details. Document the patient's physical address at the time of service, not just "patient's home." Include city and state at minimum. If the patient is at a clinical originating site, document the site name, address, and NPI. This matters because reimbursement rules differ based on whether the patient is in a rural Health Professional Shortage Area, at home, or at a facility.
Technology platform and audio-visual confirmation. Note the platform used (Zoom, Doxy.me, Epic MyChart video, etc.) and explicitly document that two-way audio and video were functional throughout the encounter. Audio-only visits have different code sets and coverage limitations. If video failed mid-visit, document when and how the visit continued.
Consent and medical necessity. Document that the patient consented to telehealth delivery and that the presenting condition was appropriate for virtual evaluation. Not every service is covered via telehealth, even if technically feasible. Your clinical documentation should reflect why telehealth was medically appropriate for this specific encounter.
State-specific telehealth compliance variations
Federal rules set the floor, but 38 states have enacted their own telehealth parity laws, coverage mandates, and documentation requirements that often exceed CMS standards.
Licensure and practice location rules
Most states require providers to hold an active license in the state where the patient is physically located during the telehealth visit. The Interstate Medical Licensure Compact covers 40 states as of 2026, but your documentation must confirm compact participation or individual state licensure for each encounter.
California, New York, and Texas maintain strict in-state licensure requirements with limited exceptions. If your coding team doesn't verify provider credentials match patient location before code assignment, you're coding visits that aren't legally billable.
Originating site and geographic restrictions
Medicare still restricts some telehealth services based on patient location. While the Consolidated Appropriations Act made many telehealth services permanent, behavioral health and certain E/M codes remain tied to rural originating sites or require specific facility types.
Commercial payers vary widely. UnitedHealthcare covers home-based telehealth for most services in 47 states. Anthem maintains geographic restrictions in 6 states. Your coding team needs payer-specific grids to apply modifiers correctly.
Documentation template requirements by state
Twelve states now mandate specific template elements beyond federal requirements. Oregon requires explicit documentation of why in-person care wasn't used. Arkansas mandates notation of backup communication plans if technology fails. Massachusetts requires documentation of interpreter services when used via telehealth.
Check your state health department's telehealth portal quarterly. These rules change faster than most coding manuals update.
Modifier discipline and common coding errors
Modifier misuse is the leading cause of telehealth claim denials in 2026. Most errors stem from confusion about when to use place of service 02 versus modifiers 95, GT, or GQ.
Place of service 02 with modifier 95. This is the standard combination for synchronous audio-visual telehealth visits billed to Medicare. Use POS 02 (Telehealth) on the claim form and append modifier 95 to the procedure code. Don't use both 95 and GT on the same line item.
Modifier GT for telehealth via interactive audio and video. Some commercial payers still require GT instead of 95. Check your payer contracts. Using the wrong modifier triggers auto-denials even when documentation is perfect. Your clearinghouse edits won't always catch this.
Modifier GQ for asynchronous store-and-forward. Used primarily in Alaska and Hawaii for dermatology, radiology reads, and specialist consultations where images are transmitted and reviewed later. Requires explicit documentation of what was transmitted, when, and how clinical decision-making occurred asynchronously.
Audio-only visits: codes 99441-99443 or G2012. These are distinct from E/M telehealth codes. Don't append modifier 95 to audio-only codes. Medicare covers G2012 for established patients only. Many commercial payers don't cover audio-only at all, so check before your coders assign these.
Common error: using POS 11 (office) with modifier 95 because "the system defaults to 11." That's wrong. POS 02 is required for most payer telehealth policies. Your billing system default isn't a compliance defense.
Documentation templates for high-volume telehealth scenarios
Standardized templates reduce documentation gaps and speed up coding turnaround. Here are four scenarios your team codes most often, with the minimum documentation elements each requires.
Established patient follow-up (99213-99215)
- Patient full name, DOB, location (city, state, full address if at home)
- Provider name, credentials, physical location during visit, state license number
- Platform used and audio-visual confirmation statement
- Chief complaint and history of present illness
- Review of systems (document pertinent positives and negatives)
- Medication reconciliation or explicit statement medications reviewed
- Assessment and plan with medical decision-making elements
- Total time spent if billing time-based (99202-99205, 99212-99215)
Behavioral health visit (90832-90834, 90836-90838)
- All elements from E/M template above
- Mental status exam findings
- Risk assessment (suicide/homicide ideation, plan, means)
- Treatment plan modifications if applicable
- Crisis plan review or establishment
- Time spent in psychotherapy (required for code selection)
- Documentation that patient was in a private, secure location
New patient telehealth visit (99202-99205)
- All elements from established patient template
- Explanation of why telehealth was appropriate for new patient evaluation
- Documentation that patient identity was verified
- Past medical history, family history, social history
- Comprehensive review of systems (10+ systems for 99205)
- Explicit statement of medical necessity for virtual visit vs in-person
Chronic care management via telehealth (99439)
- Patient name, DOB, diagnosis codes for chronic conditions being managed
- Date of service and interactive communication method
- Care plan review and updates made during the encounter
- Total time spent in care management activities this calendar month
- Next scheduled contact date
Your documentation doesn't need to use these exact formats, but every encounter must contain these minimum data points. If your telemedicine documentation workflows don't capture this consistently, your coders will spend hours querying providers or writing off charges.
Compliance auditing and common denial patterns
Run monthly audits on 10 telehealth charts per provider. Focus on these four denial triggers that account for 73% of telehealth claim rejections in 2026.
Missing originating site documentation. Medicare requires originating site information even when the patient is at home. If your template doesn't prompt for patient location, your denial rate will climb. This is the #1 avoidable error in telehealth coding.
Modifier and POS mismatch. Claims with POS 11 and modifier 95 get denied. Claims with POS 02 and no modifier get denied. Set up your EHR to hard-stop claims where POS and modifier combinations don't align with payer rules.
Non-covered service via telehealth. Coders can't bill every CPT code via telehealth just because the provider did it virtually. CMS maintains a specific list of covered telehealth services. Commercial payers have their own lists. If your coding team doesn't reference current coverage policies, you're billing non-covered codes and eating denials.
Insufficient medical decision-making documentation. Time-based billing requires total time documentation. MDM-based billing requires documented complexity elements. Many telehealth denials happen because the documentation doesn't support the E/M level billed, not because telehealth wasn't covered. This is a clinical documentation integrity issue, not a coding error.
Your compliance officer should track denial reasons by payer and service type monthly. If one provider or location shows denial rates above 8%, audit their documentation templates and modifier logic immediately.
Payer-specific telehealth policies and credentialing requirements
Every major payer has distinct telehealth billing policies that override CMS rules for commercial claims. Your coding accuracy depends on keeping current with these variations.
Medicare Advantage plans don't uniformly follow traditional Medicare telehealth rules. Humana covers home-based telehealth for most E/M services. Aetna Medicare Advantage requires prior authorization for certain telehealth subspecialty consults. Your coders need payer-specific guidance documents, not assumptions.
Medicaid managed care plans vary by state and by plan within states. In Ohio, CareSource Medicaid covers telehealth differently than Molina Medicaid, even though both operate under the same state Medicaid program. Code the same visit differently depending on which plan the patient has.
Commercial payers increasingly require telehealth-specific provider credentialing. Cigna rolled out telehealth roster requirements in Q4 2025. If your rendering provider isn't on Cigna's approved telehealth roster, claims deny even with perfect documentation. Your credentialing team and coding leadership need to communicate regularly about which providers can bill which payers for telehealth.
Frequently asked questions about telehealth coding documentation
What's the difference between POS 02 and modifier 95 for telehealth billing?
Place of service 02 indicates the claim is for a telehealth encounter and goes in Box 24B of the CMS-1500 form. Modifier 95 appends to the procedure code itself and tells the payer the service was delivered via synchronous audio-visual technology. Medicare requires both POS 02 and modifier 95 for most telehealth E/M services. Some commercial payers accept POS 02 alone or require modifier GT instead of 95.
Do I need separate consent documentation for every telehealth visit?
CMS doesn't require encounter-by-encounter consent as of 2026, but 18 states do mandate either per-visit or annual written telehealth consent. California requires documented verbal consent at minimum for each visit. Your documentation should note consent was obtained and renewed annually at minimum, with state-specific requirements checked quarterly since these rules change frequently.
Can I bill telehealth and in-person services on the same day for the same patient?
Generally no. If a patient has an in-person visit and a telehealth visit on the same date with the same provider, only one E/M service is billable unless the services are for unrelated conditions and documentation clearly separates them. Use modifier 25 only when the telehealth encounter addresses a distinct, separately identifiable problem from the in-person service, and expect payer scrutiny on these claims.
What documentation proves a telehealth visit was medically necessary?
Medical necessity for telehealth means documenting why virtual delivery was appropriate for the patient's presenting condition and circumstances. Note factors like patient mobility limitations, infection control considerations, distance from specialty care, or continuity needs that made telehealth clinically suitable. Simply stating "patient requested telehealth" isn't sufficient for most payers. The clinical documentation should reflect that the provider could adequately assess and treat the condition virtually.
How long must I retain telehealth documentation and video recordings?
Retain telehealth documentation for the same period as in-person visit records, which is typically 6 years under Medicare rules and varies by state law for other payers. You're not required to retain video recordings of telehealth visits unless your state specifically mandates it or the recording contains diagnostic information not otherwise documented in the medical record. Most compliance experts recommend against routine recording retention due to storage costs and additional breach risk.
What to do next with your telehealth coding compliance
Audit 20 telehealth charts this week using the checklist in this post. Focus on originating site documentation, modifier accuracy, and payer policy alignment. If your denial rate on telehealth claims is above 5%, your documentation templates or coding workflows need adjustment.
Train your coding team quarterly on payer-specific telehealth rules. Annual training isn't enough when policies change mid-year. If your coders are still using 2023 telehealth guidance, you're losing revenue.
If your team is struggling to keep pace with telehealth documentation requirements across multiple specialties and payers, MedCodex Health can help. Our certified coders stay current on state-by-state telehealth regulations and payer policy changes so your team doesn't have to track 40+ payer portals manually. Contact us for a free telehealth coding assessment and see where your documentation gaps are costing you revenue.