Your billing lead pulls a report on 412 virtual visits from the last quarter and finds 37 claims that went out with a place-of-service code that contradicts the modifier on the same line. Nobody caught it because the encounter template auto-populated one field and the clearinghouse edit didn't fire on the other. That is a $4,000 rework problem and, depending on the payer, a refund letter.

This guide is about the operational plumbing behind telemedicine CPT codes — who touches them in your practice, where the handoffs break, and which privacy and vendor obligations attach the moment a visit moves onto a screen. It is administrative guidance for administrators, billers, and privacy officers. It does not tell you which code fits a given clinical encounter; that determination belongs to the rendering provider working from documentation and current payer policy.

What Telemedicine CPT Codes Actually Control in Your Workflow

A code is a routing instruction. It tells the payer what modality was used, where the patient was, whether the interaction was real-time or asynchronous, and how long it lasted. Get one element wrong and the claim either denies, underpays, or pays and becomes an overpayment you owe back later.

The operational problem is that four different people usually touch a single virtual encounter: the scheduler who picks a visit type, the intake staffer who verifies the patient's physical location, the provider who documents, and the biller who submits. Each one can quietly break the chain.

Your job as administrator is to make the chain visible. That means a written coding policy, an assigned owner per step, and a monthly audit sample — not a hope that the EHR template is right.

The Code Families Your Staff Will Encounter

Real-Time Audio-Video Encounters

Two-way audio-video visits have historically been reported using standard office/outpatient evaluation and management codes with a telehealth modifier appended. CPT 2025 also introduced a dedicated telemedicine E/M series in the 98000–98015 range, split between new and established patients and between audio-video and audio-only.

Payer adoption of that series has not been uniform. Medicare and commercial plans have taken different positions on which set to accept, and some plans still expect the office/outpatient codes with a modifier. Your coding policy needs a payer-by-payer grid, refreshed at least quarterly, or your billers will guess.

Audio-Only Encounters

The old telephone E/M codes in the 99441–99443 range were deleted from CPT effective January 1, 2025 and replaced within the 98000-series structure. If your charge master, superbill, or claim-scrubber rules still reference the deleted codes, you have a cleanup task that should have closed a year ago.

Audio-only also carries a distinct documentation burden. Most payers that reimburse it expect the record to show why video was not used — patient device limitation, connectivity, patient preference — and to show that the patient consented to the modality.

Asynchronous and Patient-Initiated Digital Services

Online digital E/M services (the 99421–99423 range for physicians and qualified health professionals, with a separate range for non-physician practitioners) cover patient-initiated portal messaging that meets time and content thresholds. Brief virtual check-ins and remote image or video evaluations sit in the HCPCS G-code space.

These are the codes most often left on the table and most often billed sloppily. The common failure: nobody logs cumulative provider time across a seven-day window, so the claim can't be substantiated on audit.

Remote Monitoring

Remote physiologic monitoring (99453, 99454, 99457, 99458) and remote therapeutic monitoring (98975–98978, 98980–98981) are technically distinct from telemedicine visit codes but land in the same operational bucket because they depend on device vendors and data transmission. Every one of those vendors is a business associate. More on that below.

Which Modifiers and Place-of-Service Codes Apply to Telehealth Claims?

Short answer for the person searching this at 4 p.m. on a Friday:

  • Modifier 95 — synchronous telemedicine service delivered via real-time interactive audio and video.
  • Modifier 93 — synchronous telemedicine service delivered via real-time audio-only.
  • Modifier FQ — behavioral or mental health service furnished audio-only (Medicare).
  • Modifier FR — supervising practitioner was present via real-time audio-video.
  • POS 02 — telehealth furnished somewhere other than the patient's home.
  • POS 10 — telehealth furnished in the patient's home.

The place-of-service code reflects where the patient was, not where the provider was. That single sentence resolves most of the POS errors we see in claim audits. Which combination a payer requires — and whether it wants POS 02/10 or the practice's usual office POS with a modifier — varies by plan and changes with policy updates. Verify against the payer's current telehealth policy, not last year's cheat sheet.

Medicare Policy Runs on a Short Clock — Build For That

Medicare's expanded telehealth authority has moved through a series of short legislative extensions rather than a permanent settlement, and there have been gaps where practices held claims while waiting for retroactive fixes. Certain categories, notably behavioral and mental telehealth, sit on different statutory footing than general telehealth.

Treat this as an operational assumption, not an annoyance: your revenue cycle needs a documented hold-and-release procedure for the weeks around any expiration date. Assign one person to check the CMS telehealth coverage page and the Physician Fee Schedule on a fixed calendar cadence, and to post the current status where billers can see it. Do not let that check live in someone's inbox.

Also maintain a written record of what your practice believed the rules were on each date. When a payer audits telemedicine CPT codes two years later, contemporaneous policy documentation is what separates a coding correction from a pattern allegation.

The Documentation Checklist That Survives a Payer Audit

Build this into the encounter template so it captures at the point of care, not on appeal:

  1. Patient's physical location at the time of service, including state. This drives POS, licensure, and sometimes payer eligibility.
  2. Provider's location — office, home, other site.
  3. Modality — audio-video or audio-only, stated explicitly, with the reason if video was not used.
  4. Consent to telehealth, including any cost-sharing disclosure, with date and method captured.
  5. Identity verification method for both patient and any third party on the call.
  6. Start and stop times or total time, where the code family is time-based.
  7. Platform used, named. This matters for both billing and privacy investigations.
  8. Who else was present on either end — interpreter, caregiver, resident, scribe.

Item 7 is the one practices skip and later regret. If a patient complains that a visit was recorded or that a family member overheard, your incident response depends on knowing which platform carried that encounter.

Every Telemedicine CPT Code Has a Vendor Behind It

OCR's enforcement discretion for telehealth platforms during the public health emergency ended in 2023. There is no consumer-app grace period anymore. The video platform, the scheduling layer, the transcription or AI scribe tool, the remote monitoring device manufacturer, the clearinghouse, and any contract coder working off-site all handle protected health information on your behalf.

Each one needs a signed business associate agreement before it touches a record. HHS maintains telehealth-specific HIPAA guidance that walks through the platform obligations directly.

Run this exercise: list every system that touched last month's virtual visits, from scheduling through remittance. Then match each name against your executed BAA file. Most practices find two or three gaps — typically an AI scribe added by a single provider, a texting reminder tool, or a monitoring device vendor onboarded by clinical staff without procurement review.

When you find a gap, close it in writing rather than adding it to a list. A signature-ready business associate agreement generator walks through a six-step wizard and exports PDF and DOCX, one-time purchase, which is generally faster than waiting on a vendor's template and cheaper than routing a one-off through counsel.

Audio-Only and the Privacy Assumptions Nobody Wrote Down

Audio-only telehealth is not exempt from HIPAA. OCR has published specific guidance on audio-only telehealth addressing verification, safeguards, and when a telecommunications provider is or isn't a business associate. A standard telephone carrier acting as a mere conduit generally is not; a platform that stores, transcribes, or routes call content generally is.

The practical distinction your staff needs: if the vendor can access, retain, or process the content of the encounter, get a BAA. If it only carries the signal, document your conduit analysis and move on.

Behavioral Health Records Carry an Extra Layer

If your practice bills telemedicine CPT codes for substance use disorder treatment covered by 42 CFR Part 2, the alignment rule between Part 2 and HIPAA reached its compliance date in February 2026. Your consent forms, notice, breach procedures, and disclosure accounting for those records should already reflect it. If they don't, that is this week's priority, not this quarter's.

A 30-Day Cleanup Plan You Can Actually Assign

Week 1 — Inventory. Privacy officer lists every vendor touching virtual encounters. Billing lead pulls 90 days of telehealth claims and flags modifier/POS mismatches and any deleted codes still active in the charge master.

Week 2 — Reconcile. Match the vendor list against executed BAAs. Match the claim sample against each payer's current published telehealth policy. Document every discrepancy with a named owner and a due date.

Week 3 — Fix the template. Add the eight documentation elements above as required fields. Have the EHR administrator disable auto-population of POS on virtual visit types so a human has to confirm patient location.

Week 4 — Train and record it. Fifteen minutes with front desk and billing on patient-location verification and consent capture. Log attendance. Training records are the first thing requested when a payer or OCR asks how a pattern happened.

Set the next sample audit for 90 days out and put it on the calendar before you close the project. Telehealth policy drifts faster than almost anything else in the revenue cycle, and a workflow that was clean in March is often stale by September.

Where to Start This Week

Pull the vendor list first. It takes an hour and it tells you more about your exposure than a claims audit will, because a coding error costs money while an unpapered vendor relationship costs money and becomes a reportable event.

If that exercise turns up vendors without agreements, generate the missing business associate agreements and get them countersigned before the next round of virtual visits. If it turns up bigger gaps — no current risk analysis, policies that predate your telehealth program — automated risk analysis and policy generation will close the documentation set faster than rebuilding it by hand. Either way, do it before someone else asks to see it.