Telehealth Reimbursement Workflows: CMS Codes and the Edge Cases That Bite

Telehealth platforms get the user experience right and the reimbursement workflow wrong. Patient onboarding is polished, video quality is good, the provider tooling is well-designed — and then the claims fail. Wrong place of service codes, missing modifiers, eligibility verification that doesn’t match what the payer expects, prior authorization that wasn’t checked. The result is denied claims, A/R aging, and revenue cycle teams cleaning up what the platform should have prevented.

This post walks through the reimbursement workflow that ships clean billing — the boring load-bearing layer that most telehealth platforms underinvest in.

The basics#

US telehealth billing requires getting several things right on every visit.

Place of service (POS) code. Telehealth has specific POS codes — POS 02 for telehealth provided away from patient’s home, POS 10 for telehealth provided in patient’s home. Wrong POS code is one of the most common claim rejections.

Modifier. Most telehealth claims need a modifier — typically modifier 95 (synchronous telemedicine), modifier GT (legacy, less common in 2026), modifier 93 (audio-only) for certain phone visits. Some payers require additional modifiers.

Procedure code (CPT). Telehealth uses standard E/M codes (99201-99205 for new patients, 99211-99215 for established patients) and specific telehealth-specific codes for certain services. The 2024 update to the E/M code set affects how levels are determined.

Diagnosis code (ICD-10). Must support medical necessity for the service.

Provider type and credentialing. Some payers reimburse certain telehealth services only when delivered by specific provider types. The credentialing has to match.

Originating site requirements. Historically Medicare required the patient to be in a specific originating site type; this was relaxed during COVID and continued (with modifications) post-PHE. State Medicaid programs vary.

The eligibility verification problem#

Insurance eligibility verification for telehealth is harder than for in-person visits because:

Telehealth coverage varies by payer, plan, and state. What’s covered varies. Real-time eligibility verification systems (270/271 transactions) return basic eligibility but rarely return telehealth-specific coverage details.

Prior authorization requirements vary. Some services require prior auth before the visit; some don’t.

State law affects scope. Cross-state telehealth has specific licensure and reimbursement implications.

Network status matters. In-network vs out-of-network has different reimbursement.

The eligibility verification flow has to handle these dimensions or the claims will be denied after the service is rendered.

The workflow that ships clean billing#

A telehealth platform that produces clean billing typically has:

Pre-visit eligibility verification with telehealth-specific checks. Not just “does the patient have insurance” but “does this insurance cover this type of telehealth service at this scheduled time.”

Prior authorization workflow with explicit triggers. When the visit type requires prior auth, the platform either has it on file, captures it during scheduling, or routes the visit to the prior-auth team.

Claim coding at point of service. The provider’s clinical documentation drives the billing codes. Modern platforms surface coding hints based on the documentation, with revenue cycle review of the actual codes before submission.

Modifier logic. Automated application of telehealth modifiers based on visit type and payer rules.

State and payer rules engine. Different payers have different requirements. The rules engine ensures each claim conforms to its specific payer’s expectations.

Denial management workflow. When claims do deny, structured workflow for understanding why, correcting, and resubmitting.

The PHE aftermath#

The COVID-19 Public Health Emergency expanded telehealth coverage substantially. Many of the expansions continued post-PHE through legislative action; others have expired or evolved. The state of play in 2026:

Medicare telehealth coverage continues for most services through 2026 under repeated extensions. The geographic and originating site restrictions remain relaxed.

Commercial payer coverage varies but most major payers continue substantial telehealth coverage.

Medicaid coverage varies by state with substantial state-by-state differences.

DEA controlled substance prescribing rules have evolved with specific limitations on telehealth-prescribed controlled substances.

Platforms that haven’t updated their rules engines since the post-PHE transitions are producing denied claims they shouldn’t be.

The specific edge cases#

Several specific edge cases cause more denials than their volume suggests:

Audio-only visits — different codes and modifiers than video; not all payers cover audio-only.

Asynchronous services — different from synchronous; specific codes apply.

Group visits via telehealth — specific rules.

Cross-state visits — provider must be licensed in the state where the patient is located.

Mental health parity — telehealth mental health has specific coverage requirements under federal parity law.

Chronic care management via telehealth — specific codes (99490, 99439) with specific documentation requirements.

Where pdpspectra fits#

Our data engineering and platform work for healthcare clients includes revenue cycle integration. The technical work is one component; understanding the regulatory and payer-specific dynamics is what produces clean billing.

Related reading: the AI healthcare deployment post, the telehealth platform architecture post, and the AI triage telehealth guardrails post.

---

Telehealth billing rewards engineering discipline. Talk to our team about your platform.