Telehealth Billing Gets Complicated Fast. PIMSY Keeps Your Claims Clean.

UPDATED ON: Mar 30,2026

You already know the rules. Modifier 95 for audio-video sessions, modifier 93 for phone-only, FQ for Medicare audio-only behavioral health. POS 10 when the patient is home, POS 02 when they’re not. The October 2025 in-person mandate. DEA extensions for controlled substance prescribing. Q3014 for originating sites.

Knowing the rules isn’t the problem. Applying them correctly across hundreds of telehealth in behavioral health claims every month, without errors compounding, that’s where practices get hurt.

PIMSY handles this at the workflow level. Here’s how.

The Right Modifier on Every Claim: Not a Dropdown Someone Has to Remember

You’ve got 40 clinicians. Two hundred telehealth claims a week. A payer mix that includes Medicare, Medicaid, and six commercial plans, each with slightly different modifier requirements.

No billing manager reviews every claim before submission. That’s just not how it works at scale.

Manual modifier selection introduces errors you won’t catch until they come back as denials. By then you’re looking at a pattern, not a one-off. One miscoded session type across a high-volume week creates a denial cluster that takes staff time to identify, remediate, and resubmit.

PIMSY’s behavioral health billing software applies modifiers based on session type and payer configuration. Audio-video sessions get modifier 95. Phone-only sessions get modifier 93. Medicare audio-only behavioral health claims (for FQHCs and RHCs) get modifier FQ, stacked with 93 where required.¹ The logic follows the claim automatically.

A billing manager at a 40-clinician outpatient agency in Charlotte doesn’t need to audit modifier selection. The system does it. That’s what mental health billing software built for behavioral health volume should look like.

POS 02 vs. POS 10: The Code That’s Quietly Costing You Money

POS 10 means the patient is at home. It pays at the non-facility rate. POS 02 means the patient is at a non-home telehealth site. It pays at the facility rate, which is lower.²

Most outpatient behavioral health telehealth is POS 10. Patients connect from home. But practices using a generic EHR, or manually entering place of service on every claim, often default to POS 02 out of habit or confusion.

The revenue leakage is quiet. Each individual claim is only a few dollars off. Multiply that across your telehealth volume for a quarter and it becomes a number worth paying attention to. And consistently wrong POS coding doesn’t just cost you money: it flags payer audits.

In PIMSY, place of service flows from how the appointment is created. Schedule a home telehealth session and the claim carries POS 10. Schedule an in-office visit and it carries the appropriate office code. No one looks it up. No one corrects it after the fact.

A clinical director at a 50-clinician agency in Nashville running a routine billing audit shouldn’t discover that POS 02 has been applied to home-based sessions for six months. With PIMSY, that discovery doesn’t happen. The code is set correctly from the start.

Tracking the Medicare In-Person Requirement Across Your Panel

As of October 1, 2025, Medicare required new behavioral health telehealth patients to complete an in-person visit within six months of their first telehealth encounter, then at least annually thereafter.³ Congress extended the waiver through December 31, 2027, but the requirement is active policy, not a rumor, and practices treating Medicare patients need to track compliance by individual patient.

“Track it by patient” sounds manageable until you’re running a panel of 800 Medicare beneficiaries across 60 clinicians.

Without a system, you’re relying on individual clinicians to remember which patients need in-person visits and when. That works until it doesn’t. A Medicare audit with missing in-person visit documentation can result in retroactive clawbacks: not just for one patient, but across everyone in that cohort.

PIMSY records visit type on every encounter: telehealth or in-person, logged against the patient record. Compliance review becomes a report pull, not a chart-by-chart audit. A COO at a community mental health center in Nashville managing a 60-clinician panel can surface compliance gaps without reviewing individual notes.

Even under the current waiver extension, building the tracking habit now means you’re not scrambling when requirements lock in.

DEA-Compliant Prescribing for SUD and MAT Programs

The DEA extended telemedicine flexibilities for Schedule II-V controlled substances through December 31, 2026.⁴ Buprenorphine, methadone, and naltrexone are all eligible for telehealth prescribing under the extension, without a prior in-person exam. For SUD agencies and MAT programs, that’s a significant clinical flexibility.

The compliance pressure isn’t the prescribing decision: it’s the documentation. DEA requires a verifiable encounter record, proper DEA registration on file, and the right visit type documented. Regulators audit the paper trail, not just the prescription.

SUD practices running a separate prescribing tool alongside their EHR face a reconciliation problem. Notes live in one system, prescriptions in another, audit trail split between platforms. Staff end up printing from one system and manually logging in another. That’s exactly the kind of gap that shows up in a DEA audit.

In PIMSY, eprescribing through DrFirst or H2H runs inside the same record as the clinical note. A prescriber at an outpatient SUD agency in Raleigh writes the note, issues the buprenorphine prescription, and both are documented in the same patient chart. One audit trail. No reconciliation.

MAT programs are among the highest-scrutiny settings for DEA compliance. The documentation needs to hold up. A unified record is the only way to make that reliable at scale.

Q3014: The Originating Site Fee Most Practices Never Collect

HCPCS code Q3014 is the telehealth originating site facility fee. It pays approximately $31 per eligible encounter, and it’s available to community mental health centers, FQHCs, hospitals, and other qualifying originating sites.⁵

Most eligible practices don’t claim it. The code doesn’t appear in a standard claim template. Staff don’t add it unless they’ve been trained specifically to look for it. So it goes uncollected, claim after claim.

At volume, that adds up fast. A community mental health center running 300 eligible telehealth encounters per month and skipping Q3014 is leaving roughly $9,000 per month on the table. An FQHC in rural Tennessee went 18 months before a billing review surfaced the miss. By that point it was a significant uncollected amount, not a minor oversight.

PIMSY’s billing module supports Q3014 claims. If your site qualifies as an originating site, configure it at implementation. Don’t discover it during an audit.

A quick check: if your agency hosts telehealth encounters where a distant-site provider delivers the clinical service, you may be eligible. Confirm with your billing team and get it into your claim workflow.

One System Handling All of It

Here’s what makes fragmented tools genuinely risky: the billing rules above don’t operate in isolation.

A single telehealth encounter can touch every compliance layer at once: a Medicare patient at home, seen by a prescriber at an FQHC, receiving a buprenorphine prescription. Right modifier. Right POS code. In-person visit tracking. DEA-compliant prescribing documentation. Q3014 originating site claim. All on the same encounter.

When telehealth, prescribing, scheduling, and billing live in separate tools, errors happen at every handoff. Each system handles its piece, but no system owns the whole claim.

PIMSY integrates scheduling, HIPAA-compliant video (Jitsi/8×8 or SecureVideo), clinical notes, ePrescribe, and billing in one record. A practice owner in Atlanta who switched from three separate tools described it plainly: one login, one record, one place to look when something goes wrong.

Clearinghouse partners (Claim MD, Waystar, Trizetto, Office Ally) catch errors before they reach the payer. The clearinghouse step is a final validation layer, not a backup plan.

PIMSY is ONC-Certified, HIPAA-compliant, and 42 CFR Part 2 compliant. Built for behavioral health from the start, not adapted from a primary care platform.

When telehealth billing runs through PIMSY, the workflow handles the rules. Your staff handles the patients.

Ready to See It in Your Workflow?

Compliant telehealth billing for behavioral health breaks down at the workflow level, not the knowledge level. Staff can know every rule perfectly and still make errors under volume pressure, across payer variation, using tools that weren’t built for this.

PIMSY applies modifiers, sets POS codes, tracks Medicare in-person requirements, supports DEA-compliant prescribing, and surfaces Q3014 claims, all inside one system.

If you want to see how PIMSY handles telehealth billing for a practice your size, request a demo. We’ll walk through the exact workflow with you.