Telehealth Coding in 2026: A Decision Framework for Accurate Coding, Compliance & Revenue Recovery

Schedule Your Free Consultation

Last reviewed: verify current CMS and payer guidance before billing. Telehealth policy continues to change through annual rulemaking, and this resource is maintained as a living reference rather than a static annual article.

Executive Summary: What Changed and What Practices Need to Do Now

Most telehealth billing problems in 2026 aren't caused by not knowing which modifier exists. They're caused by a workflow that can't reliably answer four questions at the moment of coding: where was the patient, what modality was actually used, does this payer cover this service via telehealth, and does the documentation prove all three.

The single most consequential dated change this year: beginning October 1, 2026, Rural Health Clinics and Federally Qualified Health Centers must bill distant-site telehealth using the individual CPT/HCPCS code describing the service plus the appropriate telehealth modifier, rather than the single G2025 code. RHCs and FQHCs should be reconfiguring billing systems and retraining staff ahead of that date, not on it.

FEATURED ANSWER

What is telehealth coding in 2026?

•  Telehealth coding in 2026 is the process of selecting the correct CPT/HCPCS code, place of service (POS 02 or POS 10), and modality modifier (95 for audio-video, 93 for audio-only) based on where the patient was physically located and how the encounter was actually delivered — then validating that selection against the specific payer's current telehealth policy before submission.

The Telehealth Coding Decision Starts Before the Visit

By the time a coder sees the encounter, most of the information that determines correct coding has either been captured or lost. Patient location, modality, consent, and authorization are all front-end data points. A billing team working from an encounter note that says only "telehealth visit completed" is reconstructing facts rather than coding them.

This is why we frame telehealth coding as a ten-step decision sequence rather than a code lookup.

Step 1: Determine Whether the Service Is Billable

Not every remote interaction is a billable telehealth encounter. Brief check-ins, portal messages, and asynchronous reviews follow different coding rules than synchronous telehealth visits. Start by confirming the interaction meets the definition of a billable service under the applicable payer's policy.

Step 2: Identify the Service Actually Delivered

Code from what happened, not what was scheduled. A visit scheduled as a video encounter that proceeded by phone because of connection failure is an audio-only encounter for coding purposes.

Step 3: Match the Clinical Service to the Correct Code

Select the CPT/HCPCS code that describes the service rendered. CMS updates the Medicare Telehealth Services List through annual Physician Fee Schedule rulemaking, so a saved list from a prior year should be re-verified rather than trusted.

Step 4: Determine the Patient's Physical Location

This is the field most often missing. CMS distinguishes telehealth provided in the patient's home from telehealth provided elsewhere, and that distinction drives POS selection and frequently reimbursement.

Step 5: Select the Correct POS

POS 10 applies when the patient was in their home. POS 02 applies when telehealth was provided somewhere other than the patient's home. Select based on documented fact, not on which pays better.

Step 6: Determine Whether a Modifier Is Required

Modality drives modifier selection: 95 for real-time audio-video, 93 for real-time audio-only. Some payers still require GT. FR relates to virtual supervision, not service modality.

Step 7: Validate Payer-Specific Requirements

Medicare's telehealth framework is not automatically a commercial payer's framework. Coverage, modifier preference, authorization requirements, and provider eligibility all vary.

Step 8: Verify Documentation Before Claim Submission

Documentation should independently establish modality, patient location, medical necessity, and the service performed. If a reviewer couldn't confirm those from the note alone, the claim isn't ready.

Step 9: Scrub the Claim for Telehealth-Specific Errors

General claim scrubbing often misses telehealth-specific mismatches — POS conflicting with documentation, modifier conflicting with modality. Build telehealth-specific edits into the scrub.

Step 10: Monitor Payment and Denial Patterns

A single denial is a claim problem. A pattern is a workflow problem. Track telehealth denials separately from your general denial pool so patterns stay visible.

Telehealth Claim Validation Matrix

Validation Point	Question	Evidence Required	Common Failure	Revenue Impact
Patient location	Where was the patient physically located during the encounter?	Documented location in the encounter note	Location never captured	Wrong POS, denial or incorrect payment
Provider location	Where was the rendering provider located?	Provider location record	Assumed, not documented	Compliance exposure on audit
Modality	Was this audio-video or audio-only?	Documentation of the technology actually used	Note says 'telehealth visit' with no modality detail	Wrong modifier, denial risk
CPT/HCPCS	Does the code describe the service actually delivered?	Encounter documentation	Code selected from the scheduled visit type	Denial or incorrect reimbursement
POS	Does POS match the documented patient location?	Location documentation	POS assigned by default in the EHR	Payment variance or denial
Modifier	Does the payer require a modifier, and is it the right one?	Payer policy documentation	Same modifier applied to every telehealth claim	Denial or edit rejection
Medical necessity	Does documentation support the service billed?	Clinical note	Thin note that doesn't justify the service level	Denial on review
Documentation	Is the note complete and modality-specific?	Full encounter documentation	Template note that doesn't reflect the actual encounter	Audit exposure
Consent	Was consent obtained where required?	Consent record	Assumed from a prior visit	Compliance risk
Payer coverage	Is this service on this payer's covered telehealth list?	Current payer policy	Assuming Medicare's list applies to all payers	Full claim denial
Authorization	Was authorization required and obtained?	Authorization record	Not checked for telehealth specifically	Often unrecoverable denial
Provider eligibility	Is this provider type eligible to bill this telehealth service?	Enrollment and credentialing records	Assumed eligible	Denial, sometimes retroactive
Credentialing	Is the provider credentialed with this payer?	Credentialing file	Lapsed credentialing unnoticed	Denial and rework
Claim edits	Does the claim pass applicable NCCI and payer edits?	Scrubbing output	Skipped scrub under volume pressure	Preventable rejection

POS 02 vs POS 10: A Decision Framework

CMS defines POS 02 as telehealth provided other than in the patient's home, and POS 10 as telehealth provided in the patient's home. The definitions are straightforward; the operational failure is that practices often assign POS by default rather than by documented fact.

Patient Location	POS	Billing Consideration	Common Error	Prevention
Patient at home	10	Generally reimbursed at the non-facility rate	Defaulting to POS 10 because it pays more	Confirm actual patient location at the time of service
Patient at a clinic/facility	02	Generally reimbursed at the facility rate	Using POS 10 when the patient was at a clinic site	Document patient location in the encounter note
Patient at work or temporary location	Verify	Depends on whether the location qualifies as 'home' under the payer's definition	Assuming any non-clinic location equals 'home'	Check the specific payer's definition of home
Patient location undocumented	Cannot determine	Claim cannot be validated	Billing anyway and guessing	Require location capture as a mandatory encounter field
COMMON MISTAKE Selecting POS Based on Reimbursement •  Why it happens: POS 10 typically maps to the non-facility rate, which is often higher, and staff notice the pattern. •  Why it matters: POS must reflect where the patient actually was. Selecting POS for payment reasons rather than factual accuracy is a compliance problem, not an optimization. •  Better approach: Capture patient location as a required encounter field and derive POS from it automatically.

Modifier Decision Matrix

Modifier	General Purpose	Modality	Payer Considerations	Documentation	Common Error
95	Synchronous telemedicine service via real-time audio and video	Audio-video	Widely used by Medicare and most commercial payers	Document that video was actually used	Applying it to an audio-only encounter
93	Synchronous telemedicine service via telephone or other real-time audio-only	Audio-only	Recognized by Medicare; commercial adoption varies	Document why audio-only was appropriate	Using 95 by default when video failed
GT	Via interactive audio and video telecommunications systems	Audio-video	Largely replaced by 95 for most Medicare claims; some payers still require it	Follow the specific payer's instruction	Assuming GT is universally obsolete
FQ	Service furnished using audio-only communication technology	Audio-only	Used in specific behavioral health contexts	Verify current applicability for the service billed	Confusing FQ with 93 without checking payer preference
FR	Supervising practitioner was present through real-time audio and video	Supervision	Relates to virtual direct supervision, not the service modality	Document the supervising practitioner's virtual presence	Treating FR as a general telehealth modifier
EXPERT INSIGHT Modifier Selection Should Be Derived, Not Chosen •  Our certified coding professionals treat modifier selection as an output of documented modality rather than a coder decision. If the encounter template captures modality as a discrete field, the modifier follows logically. If modality is free text — or absent — the coder is guessing, and guessing at scale produces denial patterns.

Audio-Only Telehealth: Where Most Practices Get Exposed

Audio-only billing carries more risk than audio-video billing for a specific reason: the encounter frequently starts as video and becomes audio-only mid-visit, and the documentation rarely reflects that change.

A visit scheduled as video, coded as video, and actually delivered by phone after a connection failure is a miscoded claim. The scheduling system says video. The coder sees video. The note doesn't mention the failure. The claim goes out with modifier 95 on an audio-only encounter.

What Makes an Encounter Audio-Only

The technology actually used during the encounter — not the technology intended, scheduled, or attempted. If video was never established or dropped and wasn't restored, the encounter is audio-only for coding purposes.

Documentation Requirements

•     The modality actually used, stated explicitly

•     If video was attempted and failed, a note recording that fact

•     Why audio-only was clinically appropriate for this encounter

•     Patient consent to proceed by audio-only, where the payer requires it

Coverage and Compliance Considerations

Medicare recognizes audio-only for defined services with modifier 93. Commercial coverage varies significantly — some payers cover audio-only broadly, others narrowly, others not at all for certain service categories. Verify per payer before assuming coverage.

COMMON MISTAKE

Treating Scheduled Modality as Delivered Modality

•  Why it happens: The billing system pulls modality from the appointment type.

•  Why it matters: Systematic mismatch between scheduled and actual modality produces systematic miscoding.

•  Better approach: Require the provider to confirm actual modality at the close of the encounter.

Why Technically Correct Telehealth Coding Still Produces Denials

A claim can have the right CPT code, right POS, right modifier — and still deny. The usual causes sit outside the coding decision itself:

•     The service isn't on that specific payer's covered telehealth list, even though Medicare covers it

•     Prior authorization was required for the telehealth encounter and wasn't obtained

•     The provider isn't credentialed with that payer, or isn't an eligible provider type for that service

•     Documentation doesn't support the level of service billed, independent of coding accuracy

•     An NCCI procedure-to-procedure edit conflicts with another service billed the same day

•     Patient eligibility lapsed between scheduling and the encounter

This is why coding accuracy and claim payability are separate problems requiring separate controls.

Telehealth Denial Root-Cause Matrix

Denial Category	Root Cause	Example	Corrective Action	Preventive Control
POS mismatch	POS doesn't match documented patient location	POS 10 billed when patient was at a clinic	Correct POS and resubmit if timely	Mandatory location field before coding
Modifier mismatch	Modifier doesn't match actual modality	95 billed on an audio-only encounter	Correct modifier and resubmit	Modality-driven modifier rules
Coverage terminated	Patient coverage lapsed before the encounter	Eligibility not rechecked close to service date	Bill the patient or correct payer	Verify eligibility near the date of service
Service not covered via telehealth	The code isn't on that payer's telehealth list	Commercial payer excludes a service Medicare covers	Appeal only if coverage genuinely existed	Maintain per-payer covered-service lists
Authorization missing	Telehealth-specific authorization not obtained	Behavioral health visit requiring prior auth	Appeal with documentation if obtainable	Auth check at scheduling
Provider not eligible	Provider type can't bill this telehealth service	Non-eligible practitioner type billed a restricted service	Rebill under an eligible provider if appropriate	Provider-eligibility matrix by payer
Documentation insufficient	Note doesn't support the level or modality billed	Generic 'telehealth visit' note	Appeal with fuller records if they exist	Modality-specific documentation templates
Invalid CPT/HCPCS	Code retired or not valid for the date of service	Using a prior-year code after an annual update	Correct the code and resubmit	Annual code-set refresh in January
Duplicate claim	Same encounter billed twice	Resubmission without voiding the original	Void the duplicate	Resubmission controls in the billing system
NCCI/edit issue	Procedure-to-procedure edit conflict	Two services billed together that are bundled	Review edit rationale before appealing	Run NCCI edits during claim scrubbing
Patient location mismatch	Claim location conflicts with documentation	Note says home, claim says facility	Correct and resubmit	Single source of truth for location
Payer policy conflict	Payer-specific telehealth rule not followed	Payer requires GT, claim submitted with 95	Resubmit per that payer's requirement	Per-payer modifier requirement matrix

The Telehealth Revenue Leakage Problem

Denials are visible. Leakage often isn't. A claim that pays — but pays at the wrong rate because POS was wrong — never appears in a denial report.

Revenue Leak	How It Happens	How to Detect It	Prevention	Recovery Opportunity
Incorrect POS	Default POS applied without checking patient location	Compare POS distribution against documented locations	Require location capture before coding	Rebill within timely filing where permitted
Incorrect modifier	Same modifier applied to all telehealth claims	Audit modifier use against documented modality	Modality-driven modifier logic in the EHR	Corrected claims where still timely
Uncaptured encounters	Telehealth visits never make it into the billing queue	Reconcile scheduled encounters against billed claims	Daily encounter-to-claim reconciliation	Bill previously missed encounters if within filing window
Incorrect CPT selection	Code chosen from visit type rather than documentation	Sample review of codes against notes	Code from documentation, not scheduling	Corrected claims
Payer coverage mismatch	Medicare rules assumed to apply to commercial plans	Denial pattern analysis by payer	Maintain payer-specific telehealth policy matrix	Appeal where coverage actually existed
Missing authorization	Telehealth authorization requirements not checked	Review authorization-related denials	Authorization check at scheduling	Often unrecoverable — prevention is the fix
Credentialing gaps	Provider not credentialed with the payer for telehealth	Cross-check denials against credentialing status	Periodic credentialing verification	Retroactive credentialing where the payer permits
Documentation gaps	Notes don't support the billed service or modality	Documentation audit sample	Modality-specific templates	Limited — strengthen going forward
Unbilled portal services	Asynchronous/portal services never coded	Review portal activity against billed claims	Define which portal services are billable and train staff	Bill within filing limits where supported
RPM/RTM threshold errors	Monitoring day or time thresholds not met but billed anyway	Audit device data against billed periods	Automated threshold validation	Correct or void affected claims
Denial follow-up delays	Telehealth denials sit unworked	Aging report filtered to telehealth claims	Dedicated denial ownership	Appeal within payer deadlines
Underpayments	Claim pays below expected rate and nobody checks	Payment variance review	Automated expected-vs-actual comparison	Request reprocessing

Telehealth Revenue Opportunity: Illustrative Modeling

The table below is an illustrative example using a hypothetical $100 average allowed amount and a 3% preventable leakage assumption. These are not benchmarks, industry averages, or guaranteed results — they exist to show the calculation structure. Replace every figure with your own data.

Monthly Encounters	Potential Monthly Revenue	Potential Monthly Leakage (3%)	Potential Annual Leakage
250	$25,000	$750	$9,000
500	$50,000	$1,500	$18,000
1,000	$100,000	$3,000	$36,000
2,500	$250,000	$7,500	$90,000

Illustrative example — not a guaranteed financial result. Your actual allowed amounts vary by payer, locality, service mix, and contract. Your actual leakage rate can only be determined through an audit of your own claims.

Medicare vs. Commercial Payer Decision Framework

Issue	Medicare	Commercial Payer	What Billing Team Should Verify
Coverage	Defined by the Medicare Telehealth Services List, updated via annual PFS rulemaking	Set independently by each payer; may be broader or narrower	Whether this specific service is covered by this specific payer
POS	POS 02 (not home) vs POS 10 (home), per CMS definitions	Most follow CMS conventions, but not universally	Whether the payer follows CMS POS conventions
Modifier	95 for audio-video; 93 for audio-only; FR for virtual supervision	Some still require GT or have their own requirements	The payer's specific modifier requirement
Audio-only	Recognized for defined services with modifier 93	Coverage varies significantly by payer and plan	Whether audio-only is covered for this service
Authorization	Generally not required for covered telehealth E/M	Frequently required, especially behavioral health	Authorization requirements before the encounter
Provider eligibility	Defined by CMS practitioner categories	Varies by payer credentialing and network rules	Provider eligibility and credentialing status
Documentation	CMS documentation standards apply	May layer additional requirements	Any payer-specific documentation elements
Frequency limits	Some services carry frequency limitations	Varies widely	Any applicable frequency caps
EXPERT INSIGHT The Most Expensive Assumption in Telehealth Billing •  Assuming a Medicare rule applies to a commercial payer is, in our experience, the single most common source of avoidable telehealth denials. Medicare's telehealth framework is well-documented and freely available, which makes it the default mental model — but commercial payers set their own coverage, modifier, and authorization requirements independently. Maintain a payer-specific telehealth policy matrix and review it quarterly.

2026 Telehealth Change Timeline

Date	Change	Who It Affects	Billing Action
January 2026	Annual CPT/HCPCS code set update takes effect	All practices billing telehealth	Refresh code libraries and billing system configuration
Ongoing 2026	CMS updates the Medicare Telehealth Services List through annual PFS rulemaking	All Medicare telehealth billers	Re-verify covered services rather than relying on a saved list
October 1, 2026	RHCs and FQHCs must bill distant-site telehealth using the individual CPT/HCPCS code describing the service plus the appropriate telehealth modifier, rather than the single G2025 code	Rural Health Clinics and Federally Qualified Health Centers	Reconfigure billing systems and retrain staff before the effective date
Ongoing 2026	Commercial payers update telehealth policies on their own schedules	All practices with commercial payer mix	Quarterly payer policy review
DID YOU KNOW? •  CMS handles additions and deletions to the Medicare Telehealth Services List through its annual Physician Fee Schedule process. That means a covered-service list saved to a shared drive last year is a snapshot, not a standing reference — it should be re-verified against current CMS guidance rather than treated as durable.

Specialty-Specific Telehealth Considerations

Specialty	Common Telehealth Services	Coding Challenge	Documentation Concern	Recommended Control
Primary Care	Follow-ups, chronic disease check-ins, medication management	E/M level selection based on a remote encounter	Documentation that doesn't reflect the remote format	Modality-specific E/M templates
Behavioral Health	Therapy sessions, medication management, intake assessments	Audio-only frequency and modifier selection	Session length and modality not documented	Time and modality capture as mandatory fields
Cardiology	Post-procedure follow-up, RPM-linked visits, medication titration	Coordinating telehealth encounters with RPM billing	Overlapping RPM and E/M documentation	Separate RPM and visit documentation clearly
Neurology	Follow-ups for chronic conditions, post-diagnostic review	Exam-dependent services that don't translate remotely	Exam elements documented but not actually performable remotely	Define which services are telehealth-appropriate
Dermatology	Store-and-forward image review, lesion follow-up	Asynchronous vs synchronous coding distinction	Treating asynchronous review as a synchronous visit	Distinct workflows for each modality
Gastroenterology	Pre/post-procedure consults, chronic condition management	Pre-procedure consult coverage varies by payer	Consult coding assumptions carried across payers	Verify consult coverage per payer
Rheumatology	Chronic disease follow-up, medication monitoring	Exam limitations with remote encounters	Documenting exam elements not actually performed	Document only what was actually assessed
Endocrinology	Diabetes management, medication adjustment, CGM review	CGM/device data review coding overlap	Double-counting device review and visit time	Separate device-review and encounter documentation
Pain Management	Medication management, treatment plan review	Controlled substance and in-person requirements	Assuming remote prescribing rules are static	Track current prescribing requirements actively

How to Audit 100 Telehealth Claims

A structured sample audit is the fastest way to convert suspicion into a specific, fixable finding. Pull 100 telehealth claims across your payer mix and review each against these twelve points:

☐  CPT/HCPCS accuracy against documentation

☐  POS accuracy against documented patient location

☐  Modifier accuracy against documented modality

☐  Patient location documented at all

☐  Modality documented explicitly

☐  Documentation supports the service level billed

☐  Medical necessity supported

☐  Service covered by that payer via telehealth

☐  Authorization obtained where required

☐  Provider eligible and credentialed with that payer

☐  Payment accuracy against expected rate

☐  Denial status and root cause, where applicable

Calculating Your Error Rates

Coding error rate = miscoded claims ÷ 100. POS error rate = POS mismatches ÷ 100. Modifier error rate = modifier mismatches ÷ 100. Documentation error rate = insufficiently documented claims ÷ 100. Denial rate = denied claims ÷ 100. Underpayment rate = claims paid below expected ÷ 100. Revenue leakage rate = (underpaid + unbillable due to documentation) ÷ 100.

A finding of three POS errors in 100 claims sounds small. At 1,000 monthly telehealth encounters, that's 30 claims a month carrying incorrect location data — which is both a revenue variance and a compliance pattern.

Telehealth KPI Dashboard

Metric	What It Measures	What a Worsening Trend Indicates	Action to Take
Telehealth clean claim rate	Share accepted without correction	Front-end coding or documentation is degrading	Audit POS/modifier logic first
Telehealth denial rate	Share denied on first submission	A specific payer or rule change is being missed	Run denial root-cause analysis by payer
POS error rate	Claims with POS not matching documentation	Location capture is failing at the encounter level	Make location a required field
Modifier error rate	Claims with modifier not matching modality	Modality isn't being documented reliably	Add modality capture to the encounter template
Documentation error rate	Claims flagged for insufficient documentation	Templates aren't prompting for required elements	Revise templates and retrain
First-pass resolution rate	Claims paid correctly without rework	Upstream process issues are compounding	Focus on the highest-volume failure point
Days in AR (telehealth)	Collection speed for telehealth claims	Denials or follow-up delays are accumulating	Prioritize telehealth denial follow-up
Net collection rate	Share of expected reimbursement collected	Underpayments or write-offs are rising	Run payment variance analysis
Underpayment rate	Claims paid below expected amount	Payer configuration or contract issue	Compare paid vs contracted rates
Unbilled encounter rate	Encounters never converted to claims	Encounter-to-claim reconciliation is broken	Implement daily reconciliation
Appeal success rate	Share of appeals overturned	Appeals may be poorly documented, or denials were valid	Review appeal quality and denial validity separately

Telehealth Coding Error Scorecard

Score each area: 0 = no formal process, 1 = partial process, 2 = consistent documented process.

Process Area	Score (0/1/2)	Notes
POS validation process	0 / 1 / 2
Modifier validation process	0 / 1 / 2
Documentation audit process	0 / 1 / 2
Payer policy review process	0 / 1 / 2
Credentialing verification process	0 / 1 / 2
Denial tracking by root cause	0 / 1 / 2
Underpayment monitoring	0 / 1 / 2
Staff education on telehealth coding	0 / 1 / 2
Quarterly compliance review	0 / 1 / 2
Telehealth claim audit process	0 / 1 / 2

0–7: High Risk. 8–14: Moderate Risk. 15–20: Strong Foundation. This is an educational self-assessment framework, not a regulatory standard or compliance certification.

Building a Telehealth Billing Governance Program

Telehealth coding accuracy degrades without maintenance, because the rules underneath it keep moving. A governance cadence keeps the workflow aligned with current requirements.

Monthly

•     Telehealth denial review by root cause

•     Modifier accuracy spot-check

•     POS accuracy spot-check

•     Payment variance review

Quarterly

•     Payer telehealth policy review across your top payers

•     CMS guidance and PFS update review

•     Staff training refresh on any changed requirements

•     Billing system code and edit configuration review

•     Sample telehealth claim audit

Annually

•     Full telehealth billing audit

•     Payer contract review for telehealth terms

•     Credentialing verification across payers

•     Workflow redesign based on the year's findings

Human Review Checkpoints

Automation handles volume well and judgment poorly. These decisions should stay with qualified people:

•     Coding validation where documentation is ambiguous

•     Documentation sufficiency review

•     Medical necessity assessment

•     Payer policy interpretation, especially where policy language is unclear

•     Denial appeals and supporting narrative

•     Compliance decisions with audit exposure

•     Payer contract analysis

•     Exception handling outside standard workflow

Technology should surface the issue and prompt the review. It shouldn't close the loop on a compliance decision by itself.

Frequently Asked Questions

What is telehealth coding?

Telehealth coding is the process of assigning the correct CPT/HCPCS code, place of service, and modality modifier to a remotely delivered healthcare service, based on what was actually performed, where the patient was located, and how the encounter was delivered — then validating that against the applicable payer's telehealth policy.

What CPT codes can be used for telehealth?

Many standard CPT codes can be delivered via telehealth when the service appears on the applicable payer's covered telehealth list. For Medicare, CMS maintains the Medicare Telehealth Services List and updates it through annual Physician Fee Schedule rulemaking. Because that list changes, verify current coverage rather than relying on a saved list.

What is the difference between POS 02 and POS 10?

POS 10 indicates telehealth provided in the patient's home. POS 02 indicates telehealth provided somewhere other than the patient's home — for example, a patient at a clinic or other facility. The selection should reflect the patient's documented physical location during the encounter, not reimbursement preference.

When should modifier 95 be used?

Modifier 95 identifies a synchronous telemedicine service delivered via real-time interactive audio and video. It should be applied when video was actually used for the encounter. If video was attempted but the visit proceeded by audio only, modifier 95 is not the correct choice.

When is modifier 93 used?

Modifier 93 identifies a synchronous service delivered via telephone or other real-time audio-only communication. Medicare recognizes audio-only for defined services. Commercial payer coverage of audio-only varies considerably, so verify the specific payer's policy before billing.

Can Medicare telehealth rules be applied to commercial payers?

No. Commercial payers set their own telehealth coverage, modifier requirements, authorization rules, and provider eligibility criteria. Some align closely with Medicare; others differ substantially. Assuming Medicare rules apply universally is one of the most common causes of avoidable telehealth denials.

How should audio-only telehealth be billed?

Confirm the payer covers the service via audio-only, apply the appropriate audio-only modifier (typically 93 for Medicare), select POS based on the patient's documented location, and ensure documentation states the modality actually used and why audio-only was clinically appropriate.

What documentation is required for telehealth?

At minimum: the modality actually used, the patient's physical location, the provider's location, consent where required, the clinical content supporting medical necessity and the service level billed, and the service actually performed. A note stating only "telehealth visit" does not support a claim.

Why are telehealth claims denied?

Common causes include POS not matching documented location, modifier not matching actual modality, the service not being covered via telehealth by that payer, missing authorization, provider eligibility or credentialing gaps, insufficient documentation, and claim edit conflicts.

How can practices reduce telehealth billing errors?

Capture patient location and modality as required discrete fields at the encounter, derive POS and modifier from those fields rather than leaving them to coder judgment, maintain a payer-specific telehealth policy matrix, build telehealth-specific claim edits into scrubbing, and track telehealth denials separately.

How often should telehealth billing be audited?

A monthly spot-check of POS and modifier accuracy, a quarterly sample claim audit, and a full annual telehealth billing audit is a reasonable cadence for most practices. Higher telehealth volume or a recent policy change warrants more frequent review.

Should a medical practice outsource telehealth billing?

It depends on volume, internal coding expertise, payer mix complexity, and current denial trends. Practices with strong internal controls and stable payer mixes often manage well in-house. Practices seeing recurring POS, modifier, or payer-policy denials — or lacking capacity to track changing requirements — may benefit from specialized support.

Sources & References

This resource references current CMS telehealth guidance including CMS place-of-service definitions for POS 02 and POS 10, CMS guidance on the Medicare Telehealth Services List and its update through annual Physician Fee Schedule rulemaking, CMS guidance on the October 1, 2026 RHC/FQHC distant-site telehealth billing change, AMA CPT modifier descriptors for modifiers 93 and 95, and CMS National Correct Coding Initiative materials regarding procedure-to-procedure edits. Because telehealth policy changes frequently, verify all requirements against current CMS and payer guidance before billing.

Disclaimer

This article is provided for general educational and informational purposes only and does not constitute legal, medical, coding, billing, or reimbursement advice. Telehealth coverage, coding requirements, place-of-service conventions, modifier requirements, documentation standards, and reimbursement policy change frequently and vary by payer, plan, state, provider type, and individual patient circumstances. Financial examples in this article are illustrative only and are not guaranteed results. Practices should verify current requirements directly with CMS, applicable Medicare Administrative Contractors, and each relevant payer before submitting claims. MedCloudMD does not guarantee reimbursement, claim approval, or specific financial outcomes.