Your remittance advice comes back with eleven denials, and nine of them are virtual visits from the same provider on the same three days. The place of service says 02. The patient was sitting in her kitchen. Somebody in your workflow picked the wrong pair. That is the everyday reality behind the question of which cpt code for telehealth visit reporting your practice should use — it is rarely one code, it is a code plus a modifier plus a place of service plus a note that supports all three, and any one of those four can sink the claim.

This guide is written for the administrator, biller, or compliance lead who owns that workflow. It covers how practices determine and document code selection, who does what and when, and the privacy, records, and vendor obligations that attach to every virtual encounter. It does not tell you which code fits a given patient's presentation. That determination belongs to the rendering clinician.

What Determines the CPT Code for a Telehealth Visit

Four variables drive the selection, and your intake and documentation templates should capture all four before a claim ever reaches the clearinghouse:

  • Service type. Was this an evaluation and management encounter, a behavioral health session, a brief check-in, an asynchronous review, or something else entirely?
  • Modality. Real-time audio and video, audio-only, or store-and-forward. This drives modifier choice and, for some payers, drives the base code itself.
  • Patient location at the time of service. Home versus a clinical originating site. This drives place of service.
  • Payer rules in effect on the date of service. Medicare, Medicaid, and commercial plans do not align, and Medicare telehealth policy has moved in short legislative increments.

The short answer most billers need: for Medicare, practices have generally continued reporting the office and outpatient E/M code range with a telehealth modifier and the appropriate place of service, rather than switching to the newer telemedicine-specific code family. Commercial payers split — some accept or require the newer codes, some still want the E/M code plus modifier 95. Your payer matrix, not a blog post, is the authority.

The 2025 code family that Medicare largely declined to price

The CPT code set introduced a dedicated telemedicine E/M range covering synchronous audio-video services, synchronous audio-only services, and a brief communication technology-based service. When CMS finalized the physician fee schedule for 2025, it adopted the brief virtual check-in code as a replacement for the older HCPCS check-in code but declined to establish payment for most of the new audio-video and audio-only E/M codes, directing practices to continue using the established office and outpatient E/M codes for Medicare telehealth reporting.

That split is why your practice needs two lanes in the same fee schedule build: one for payers who want the telemedicine-specific codes and one for payers who want E/M plus modifier. Verify the current year's status on the CMS Medicare telehealth page before your first claim of any new quarter. Medicare's geographic and originating-site flexibilities have been extended in short increments by Congress and have lapsed at least once during a funding gap — treat the effective dates as volatile and re-check them, rather than hard-coding assumptions into your billing rules.

The Four Data Points Your Note Must Carry Before Billing

Coding disputes and payer audits almost always turn on documentation, not on code choice in the abstract. Build these into the template so the clinician cannot close the encounter without them:

  1. Patient's physical location during the encounter — enough specificity to support the place of service you report.
  2. Provider's physical location — home office, clinic, or other site. This matters for state licensure questions and for some payer edits.
  3. Modality actually used, including whether video was attempted and failed and the visit converted to audio-only. Conversions are a frequent source of modifier mismatches.
  4. Consent to receive care by telehealth, with date and method, plus who else was present on either end.

For E/M level selection, the same total-time or medical-decision-making framework applies as it does in person. Your job as an administrator is to confirm the note contains the substantiating detail — documented time, or the elements supporting the stated complexity — not to second-guess the level the clinician selected. When the note does not support the level, the correct move is a query back to the clinician, logged, before the claim drops.

Who Does What: Role Assignments for a Telehealth Claim

Front desk or virtual intake, at scheduling: capture patient location, confirm the platform link went to the correct contact, and record telehealth consent. Verify the phone number and email on file — a link sent to a stale address is a disclosure incident waiting to happen.

Clinician, at the encounter: document modality, locations, participants, and the clinical content that drives level selection. Note any mid-visit modality change.

Coder or biller, within 48 hours: reconcile the documented modality against the modifier, and the documented patient location against the place of service. Flag mismatches rather than correcting them silently.

Billing supervisor, weekly: run a telehealth-only denial report by payer and by denial reason code. Three of the same reason code from the same payer is a rules problem, not a claims problem.

Privacy officer, monthly: confirm every platform, interpreter service, transcription tool, and outsourced billing partner touching those encounters appears on the vendor inventory with an executed agreement.

Modifiers and Place of Service: Where the Denials Actually Come From

Modifier 95 signals a synchronous service delivered via real-time interactive audio and video. Modifier 93 signals synchronous audio-only. Some payers and institutional claim types still expect the older telehealth modifier, and Medicare has separate modifiers for certain behavioral health audio-only situations. Place of service 10 indicates the patient was in their home; place of service 02 indicates a telehealth service where the patient was somewhere other than home.

The pairing matters financially. Under Medicare's fee schedule logic, the place of service determines whether the service pays at the facility or non-facility rate. A biller who defaults every virtual visit to 02 out of habit is systematically under- or over-reporting, and either direction creates exposure. Build an edit in your practice management system that will not release a telehealth claim unless the modifier and place of service combination appears on an approved list for that payer.

Also confirm whether your payers accept the office-visit complexity add-on code alongside telehealth E/M. Policies differ, and this is a common source of quiet revenue leakage.

The Claim Itself Is PHI — Including the Modifier

Every element you have just assembled is protected health information moving through a chain of business associates. Place of service 10 tells the recipient that a person received care at home. A behavioral health audio-only modifier discloses service category and modality together. That is not a reason to code inaccurately; it is a reason to apply minimum necessary to everything downstream of the claim.

Practical controls that hold up under review:

  • Role-based access in the practice management system, so a scheduler cannot pull the full claim history for a behavioral health panel.
  • Written standards for remote billing staff — encrypted device, no local storage of remittance files, no printing at home, session timeouts.
  • Clearinghouse and remote-hosting agreements that name the specific data flows, not a boilerplate template signed in 2016 and never revisited.
  • Audit log review on any account that exported more than a threshold number of records in a month.

Your Telehealth Platform Is a Business Associate — No Exceptions Since 2023

During the public health emergency, OCR exercised enforcement discretion for good-faith use of non-public-facing communication technologies in telehealth. That discretion ended, with a transition period that closed in August 2023. Since then, the ordinary rule governs: a vendor that creates, receives, maintains, or transmits PHI on your behalf is a business associate and needs a signed agreement. HHS maintains its telehealth and HIPAA guidance for exactly this question.

Walk your actual telehealth stack, not the one on the org chart. It typically includes the video platform, the scheduling and reminder tool, the e-consent or e-signature service, the remote interpreter vendor, any ambient documentation or transcription tool, the clearinghouse, the patient payment tool, and any outsourced coding or RCM partner. Each one needs a current agreement, an owner, and a renewal date.

If your inventory has gaps — and most do after two years of adding tools one at a time — you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX. One-time purchase, no subscription, which matters when you need four agreements this week and none next quarter. Send them out with a tracked due date and log the countersignature in the same place you keep the vendor list.

One more vendor category people miss: analytics and tracking code on the pages patients use to reach a virtual visit. OCR issued guidance on online tracking technologies, portions of which a federal court set aside in 2024 as applied to unauthenticated pages. The litigation history does not change the underlying analysis for authenticated portals and scheduling flows tied to an identified patient. Have your web vendor produce a current inventory of every third-party script on those pages.

Recordings, Chat Logs, and the 30-Day Access Clock

A patient emails your practice asking for "everything from my video visit." You have 30 days to act, with one possible 30-day extension and written notice of the reason, under the HHS right of access guidance. The complication is scope.

Deciding what is in the designated record set

The encounter note is plainly in. In-session chat transcripts and any recording your practice retains are records you maintain and use to make decisions about the individual, so treat them as in scope unless counsel has documented a specific basis for excluding them. Waiting-room telemetry and platform connection diagnostics generally are not.

Decide this before a request arrives and write it into your access policy. Then align retention: if your platform holds recordings for 90 days by default and your policy says you do not retain recordings at all, you have a contradiction that a records request or a subpoena will expose. Confirm the platform's actual retention setting in writing, and confirm the deletion behavior when you terminate the contract.

A Worked Example: Auditing One Month of Telehealth Claims

Pull every claim from last month with a telehealth modifier or a telehealth place of service. For a mid-size primary care practice that is often 150 to 400 lines. Sample 25.

For each, confirm five things: the note states the patient's location and it matches the place of service; the note states the modality and it matches the modifier; the payer's policy on the date of service permitted that code and modality combination; the documented time or decision-making supports the level billed; and telehealth consent is on file. Record pass or fail per element.

Two or more failures on the same element across 25 charts is a systems fix — template change, edit rule, or a targeted training. Isolated failures are coaching. Keep the audit worksheet; it is the evidence that your practice monitors its billing, which is exactly what a payer audit or an OIG-style review will ask you to produce.

Verify Before You Bill: The Sources That Actually Govern

Three sources, checked on a schedule, will keep your telehealth billing defensible. The CMS telehealth pages and the current-year physician fee schedule final rule govern Medicare code status, modifiers, and place of service. Your state Medicaid provider manual governs Medicaid, which frequently diverges. Each commercial payer's telehealth reimbursement policy, downloaded and dated, governs the rest.

Assign one person to re-download all three each quarter and note the changes in a one-page log. When a denial pattern shows up eight months later, that log is how you determine whether the rule changed or your process drifted.

Selecting the right cpt code for telehealth visit reporting is the visible half of the job. The other half is proving that the vendor carrying the encounter is under agreement, that the recording retention matches your policy, and that a records request will not expose a gap between what you say you keep and what your platform actually stores.

If your telehealth vendor list has grown faster than your paperwork, start by closing the agreement gaps — build and export the BAAs you are missing this week, then work the rest of your documentation set, including the risk analysis and policies, through automated HIPAA compliance documentation. Neither is a certification, and no vendor can grant one. Both are the evidence you will be asked to produce.