Telehealth became a permanent fixture in most practices after 2020, but billing systems never fully caught up. Many practices still run virtual visits through workflows designed for in-person care, then paper over the gaps with manual edits at claim time. The result is a quiet, recurring leak: clean clinical encounters that get denied, downcoded, or underpaid because of a wrong modifier or place-of-service code that nobody caught.
This isn't a clinical problem. It's a data problem. And it's one of the most fixable sources of lost revenue in a telehealth practice.
The denials almost never come from the visit itself. They come from three small fields that have to agree with each other and with the way the patient was actually seen.
Place of service (POS) codes. When CMS retired the blanket public health emergency flexibilities, POS coding got stricter. POS 10 signals telehealth provided to a patient in their home; POS 02 signals telehealth provided somewhere other than the home. Many commercial payers now reimburse these two codes at different rates, and several pay POS 10 at the higher, in-office-equivalent rate. If your system defaults every virtual visit to a single POS, you are either triggering edits or quietly leaving the differential on the table on every applicable claim.
Telehealth modifiers. Modifier 95 indicates a synchronous audio-video service. Modifier 93 indicates an audio-only service. Payers increasingly want the modifier to match the actual modality of the encounter, and some still expect legacy modifiers like GT or GQ on specific lines. A video visit billed as audio-only, or an audio-only visit billed with modifier 95, is a mismatch a payer's automated edits will flag.
Modality drift. This is the underestimated one. A visit is scheduled as video, the patient's connection fails, and the clinician finishes by phone. The encounter is now audio-only, but the schedule, the chart, and the charge ticket still say video. Unless someone manually reconciles all three, the claim goes out describing a visit that didn't happen the way it was coded.
Most billing teams know these rules. The problem is that the rules live in people's heads and get applied by hand, visit by visit, often days after the encounter when the detail is already cold.
That approach breaks down for predictable reasons:
The honest conclusion is that this cannot be a human-vigilance problem. The coding has to be driven by the modality of the visit, captured automatically, at the moment the visit happens.
The fix is to make the way a visit was conducted the single source of truth for how it's coded. Instead of a biller inferring modality after the fact, the system records it as the encounter occurs and propagates the correct billing data forward without anyone retyping it.
A sound modality-driven workflow does four things:
Done well, this turns a recurring manual chore into a background process. The biller's job shifts from re-coding every telehealth claim to reviewing the rare exceptions the system can't resolve on its own.
This is precisely the gap GenMed Clinical is built to close, because the telehealth and billing functions live on the same platform rather than in two systems that have to be reconciled by hand.
When a visit runs through GenMed's integrated telehealth, the platform knows how the encounter actually happened — whether it started as video, whether it dropped to audio-only, and where the patient was located. That modality data doesn't sit trapped in the video tool. It flows directly into GenMed's charting and billing engine, so the correct telehealth modifier (95 versus 93) and the correct place-of-service code (10 versus 02) are applied from the real encounter, not from whatever was on the schedule.
Because scheduling, charting, telehealth, and claims are one connected workflow, the modality drift problem largely disappears: a visit that changes modality mid-stream carries that change through to the claim automatically. GenMed's claims and billing tools then scrub each telehealth claim against payer-specific rules before it goes out, surfacing any mismatch between modality, modifier, POS, and procedure code so your team fixes it pre-submission instead of working a denial weeks later. And because the whole stack is HIPAA-ready, the visit data driving those codes stays inside a compliant system end to end.
The practical payoff: fewer telehealth denials, no quiet underpayments from defaulted POS codes, and a billing team that reviews exceptions instead of re-coding every virtual visit by hand. If telehealth is a real share of your volume, modality-driven coding inside GenMed Clinical is one of the cleanest revenue recoveries available to you.
Home · Blog · Pricing · Support · Privacy