Ninety-one claims come back on Tuesday's remittance with the same remark: modality not supported. Your billing lead traces all of them to the same two weeks, the same three clinicians, and the same root cause — a telehealth modifier that did not match the place of service code, or a progress note that never recorded whether the visit had video at all. This guide is written for the administrator who has to fix that: what the modifiers signal, who decides which one lands on the claim, what documentation has to exist before anyone decides, and why the modality you bill is also a privacy fact that leaves your building.

Coding and billing decisions belong to your coders and clinicians working from payer policy and the documented encounter. Nothing here tells you which code fits a specific patient. What follows is workflow: the sequence, the roles, the source documents, and the compliance exposure attached to each step.

The Four Fields That Have to Agree on Every Virtual Claim

A telehealth claim fails or survives on four data points lining up: the modality documented in the note, the modifier appended to the CPT/HCPCS code, the place of service code, and the payer's published policy for that date of service. Break any one link and the claim either denies, underpays, or — worse — pays at a rate you cannot defend on audit.

Most practices treat this as a billing problem. It is a documentation problem that surfaces in billing. Your coder cannot invent modality. If the note says "telehealth visit" and nothing else, the coder is guessing, and a guess that pays is still a guess.

  • Scheduler: records the intended modality and the patient's expected location at booking.
  • Clinician: documents actual modality, actual patient location, participants, and any mid-visit change (video dropped to phone).
  • Coder/biller: maps documented modality to modifier and POS under the payer's current policy.
  • Practice administrator: maintains the payer policy grid and the effective dates.
  • Privacy officer: owns the platform inventory, the BAAs, and the recording/retention rules.

Write those five rows into your telehealth policy with names attached. Ambiguity about ownership is the reason the same denial recurs quarter after quarter.

What Each Telehealth Modifier Signals: The Short Answer

A telehealth modifier is an administrative flag telling the payer how a service was delivered, not what was delivered. The commonly encountered ones:

  • 95 — synchronous service delivered via a real-time interactive audio and video telecommunications system.
  • 93 — synchronous service delivered via telephone or other real-time interactive audio-only system.
  • FQ — service furnished using audio-only communication technology, used in certain Medicare behavioral health contexts.
  • FR — the supervising practitioner was present through real-time two-way audio/video.
  • GT — interactive audio and video telecommunications; retained on certain institutional claim types after Medicare moved professional claims away from it.
  • GQ — asynchronous store-and-forward telecommunications, tied to specific federal demonstration contexts.
  • G0 (G-zero) — telehealth services for diagnosis, evaluation, or treatment of acute stroke symptoms.

Selection follows the documented encounter and the payer's policy in effect on the date of service. It does not follow what was scheduled, and it does not follow what the practice usually bills.

Place of Service 02 and 10 Ride Alongside the Telehealth Modifier

POS 02 designates telehealth provided somewhere other than the patient's home. POS 10 designates telehealth provided in the patient's home. Those two codes changed the arithmetic for a lot of practices, because the payment rate can differ depending on which one you submit.

Medicare has, at various points, instructed practitioners to submit the place of service they would have used for an equivalent in-person visit and append modifier 95, rather than using POS 02 or 10, in order to preserve a particular payment rate. That instruction has changed more than once as statutory flexibilities were extended in short increments. Do not rely on institutional memory here.

Assign one person to check the CMS telehealth coverage pages at the start of each quarter and after any appropriations action, and to date-stamp the grid. Medicare telehealth authority has repeatedly been extended in short windows tied to funding bills, and each extension has arrived with its own billing instructions and its own effective date. A grid without a "verified on" date is a liability.

The Payer Grid

Build a simple matrix: payer down the left, columns for accepted modifiers, accepted POS codes, audio-only coverage, consent requirements, and the URL and date of the policy you read. Commercial plans, Medicaid managed care, and traditional Medicare will not agree with one another. Medicaid rules vary by state and change on state timelines, not federal ones.

Review it monthly. Attach the review to an existing recurring meeting so it does not become someone's optional side project.

The Documentation Your Coder Needs Before Anyone Picks a Modifier

Standardize the telehealth note so modality is never inferred. At minimum, the encounter record should capture:

  1. Modality actually used — two-way audio and video, or audio only.
  2. Patient's physical location during the encounter, at least to the level the payer requires.
  3. Practitioner's location.
  4. Everyone present on the call, including family members, caregivers, interpreters, and any staff observing.
  5. Start and stop times, or total time when the code set is time-based.
  6. Patient consent to receive the service by that modality, and the date consent was obtained.
  7. Any technology failure and what the encounter converted to.

That seventh item is where most audits find daylight. A visit that starts on video and finishes on the phone is not documented by a template that only has one checkbox. Give clinicians a field for the switch and a place to note the time it happened.

Retention rules do not change because the visit was virtual. The telehealth note is part of the designated record set, and a patient's right of access reaches it on the same 30-day clock as everything else in the chart.

Where the Telehealth Modifier Becomes a Privacy Question

Here is the part most billing training skips. The modifier you submit is disclosed PHI. It tells every downstream recipient of that claim — the clearinghouse, the payer, the payer's subcontractors, anyone who later receives an explanation of benefits — that this specific person had a specific kind of encounter.

Certain modifiers carry more signal than others. A code combination that flags an audio-only behavioral health encounter reveals the category of care, not just the delivery method. For patients in shared households, in domestic violence situations, or on a family plan where the subscriber is not the patient, that disclosure has consequences your front desk will hear about first.

Two operational responses. First, know your confidential communications workflow cold: patients have the right to request that you communicate by alternative means or at alternative locations, and your staff need a documented path for honoring reasonable requests. Second, train the person who handles "why did my spouse's insurance company send me this letter" calls, because they will get them.

Minimum necessary does not let you drop a required modifier — claims transactions are what they are. It does govern everything around the claim: who inside your practice sees the telehealth schedule, who can pull modality reports, and what your platform logs.

Your Vendor List Grew When Telehealth Did

The OCR notification of enforcement discretion that let practices use non-public-facing consumer video tools during the public health emergency ended, along with its transition period, in 2023. Since then, the ordinary rules apply in full: your telehealth platform creates, receives, maintains, or transmits ePHI on your behalf, and it is a business associate. HHS keeps its current position on the telehealth and HIPAA special topics page, and practical implementation guidance sits at telehealth.hhs.gov.

Inventory everything that touches a virtual encounter, not just the video window:

  • The video/audio platform itself, including any waiting-room or check-in module.
  • Scheduling and intake tools that collect symptoms or reason for visit.
  • SMS and email reminder services.
  • Ambient documentation or AI scribe tools, plus any subcontractor they route audio to.
  • Remote interpreter services.
  • Remote monitoring device vendors and their data platforms.
  • Cloud storage holding recordings, transcripts, or screenshots.
  • Your clearinghouse, which sees every modifier you submit.

Each line needs an executed business associate agreement on file, with a named owner and a renewal date. A conventional landline carrier that merely transmits a call is treated differently than a technology vendor that stores or processes ePHI — but the moment a vendor holds recordings, transcripts, or metadata, you are past that distinction. If any row on that list is missing paperwork, you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX in an afternoon. One-time purchase, no subscription — which matters when you are closing eleven gaps at once and cannot justify eleven seats of something.

Recording, Transcripts, and the Question Nobody Asked

Decide, in writing, whether telehealth encounters are recorded. If they are, decide where recordings live, who can access them, how long they are kept, and whether they are part of the designated record set. If they are not recorded, verify that the platform's default settings match that decision — vendors change defaults on their release schedule, not yours.

Ambient AI documentation deserves its own paragraph in your policy. Capture consent language, retention of the raw audio, whether the vendor uses your data for model training, and whether any subcontractor receives the audio. Get those answers in the contract, not in a sales email.

A 30-Day Cleanup Plan

Week 1. Pull 90 days of telehealth claims. Sort by modifier and POS combination. Flag every combination that appears fewer than five times — outliers are usually errors or one clinician's habit.

Week 2. Audit 20 charts against their claims. Does the note state modality explicitly? Does it record patient location? Is consent documented? Record the pass rate; you will need the baseline.

Week 3. Rebuild the payer grid with URLs and verification dates. Confirm the current Medicare billing instruction rather than assuming last year's still holds.

Week 4. Reconcile the vendor inventory against executed BAAs. Update your risk analysis to reflect the telehealth data flows you just mapped — if that document has not been touched since the platform changed, it is stale, and stale risk analysis is the single most common finding in OCR enforcement. Tools that automate risk analysis and the supporting policy set shorten that lift considerably.

The Audit Trap: When the Modifier and the Note Disagree

Payer audits of telehealth claims tend to start with modality, because it is the easiest thing to disprove. A reviewer asks for ten charts, finds that six notes say nothing about video, and extrapolates. The recoupment letter arrives months later, addressed to you.

Protect against this with a quarterly internal sample — twenty charts, four fields, pass or fail. Track the rate by clinician and feed it back individually. Practices that do this for two quarters usually see the failure rate collapse, because the problem was never intent; it was a template that did not ask the question.

Keep the audit results. A documented internal monitoring program with dated findings and corrective actions is worth considerably more in a payer dispute or an OCR inquiry than a policy binder nobody has opened.

Start With the Paperwork You Can Close This Week

Modifier accuracy is a training and template problem you will work on all year. Vendor agreements are not — they are a discrete list with a discrete finish line. Pull your telehealth vendor inventory, mark the rows with no executed agreement, and close those gaps with a signature-ready BAA before the next audit request lands. Then go fix the note template.