Your Tuesday schedule has fourteen virtual visits. Nine of the patients carry an Anthem-branded card, three of those cards belong to out-of-area Blue plans, and one is a self-funded employer group that quietly follows its own telehealth rules. This guide is for the person who has to make that morning work: the administrator, biller, or privacy officer running anthem telehealth encounters end to end. It covers eligibility verification, documentation habits that survive a payer audit, the platform vendor questions nobody asks until after a breach, and what happens when a patient requests the record of a video visit.

Nothing here is clinical guidance and nothing here tells you which code fits a given encounter. It tells you how to build the process that produces defensible answers.

Verify Before the Visit, Not After the Denial

Anthem-branded plans operate as Blue Cross Blue Shield licensees across a defined set of states under Elevance Health. That means the telehealth policy that applies to your Ohio patient may not be the policy that applies to your Virginia patient, and an out-of-area Blue member routed through the BlueCard arrangement is adjudicated under a different home plan's benefit design entirely.

Self-funded employer groups add another layer. The card looks identical. The benefit booklet is not.

So the rule for your front desk is simple: the eligibility check for a virtual visit is a separate task from the eligibility check for an in-office visit, and it happens before the link goes out. Confirm the member's plan, confirm that virtual visits are a covered benefit under that specific plan, and confirm the cost-share the patient will owe. Write the reference number from the call or the portal transaction into the encounter note field your practice management system provides.

Assign the Task to a Name, Not a Department

The failure pattern is predictable. Verification is "the front desk's job," so on a short-staffed Thursday it belongs to no one. Assign virtual-visit verification to a named person with a named backup, and give them a same-day deadline: all next-day telehealth appointments verified by 3 p.m.

Track two numbers monthly. First, the percentage of virtual visits verified before the appointment. Second, the denial rate on virtual visits compared with in-office visits. When the second number climbs, the first one usually explains it.

What a Practice Needs to Bill an Anthem Telehealth Visit

Practices typically need five things in place before a virtual encounter is billable and auditable:

  1. Verified eligibility and benefits for that member's specific plan, documented with a reference number and date.
  2. A confirmed provider participation status for the rendering clinician under that plan, including licensure in the state where the patient is physically located at the time of the visit.
  3. Documented patient consent to receive care by virtual means, captured in a way you can retrieve later.
  4. An encounter note that records the modality — audio-video or audio-only — the patient's location, the provider's location, start and stop times, and who participated.
  5. Code selection supported by that documentation, with place-of-service and modifier conventions confirmed against the payer's current provider manual and any published telehealth policy update.

Miss any one of the five and the claim may still pay. It will not survive a post-payment review.

Code Selection Is a Documentation Question, Not a Guessing Game

Your billing staff should never be selecting telehealth modifiers or place-of-service values from memory, from last year's cheat sheet, or from what worked for a different payer. Payer telehealth policies changed repeatedly through the post-public-health-emergency years, and place-of-service conventions for virtual care are exactly the sort of thing that gets revised in a quarterly provider bulletin.

Build the process this way:

  • Designate one person to review the payer's provider communications each month and log any telehealth-relevant change with the date it takes effect.
  • Maintain a single internal reference document — one page, versioned, dated — that states your practice's current convention for virtual encounters and cites the payer source it came from.
  • Require the clinician's note to establish modality and locations independently of the claim. If the note says audio-video and the claim says something else, you have a discrepancy an auditor will find faster than you will.
  • Run a quarterly sample. Pull ten virtual encounters, compare note to claim, and document what you found and what you fixed.

Coders determine code selection from the documented encounter. Administrators build the system that makes the documentation complete. Keep the two roles distinct in writing, because that distinction is your defense if a selection is later questioned.

Your Telehealth Platform Is a Business Associate — Confirm It in Writing

During the COVID-19 public health emergency, OCR exercised enforcement discretion for good-faith use of everyday video applications. That discretion ended on May 11, 2023, with a short transition period that closed on August 9, 2023. Since then, the ordinary rules apply in full: the vendor transmitting or storing protected health information for your anthem telehealth visits is a business associate, and you need an executed agreement with it.

OCR's telehealth guidance for covered entities lays out the expectations, including the 2022 guidance addressing audio-only telehealth and the conditions under which it may be conducted.

Pull your vendor list and answer these for every product touching a virtual visit — the video platform, the scheduling tool that emails links, the interpreter service, the transcription or ambient documentation tool, the patient messaging system:

  • Is there a signed BAA on file, and who holds the countersigned copy?
  • Does the vendor record sessions by default, and can you turn that off?
  • Where is data stored, for how long, and what happens on termination?
  • Does the platform's free or consumer tier differ from the tier you are actually paying for? Practices get caught here constantly.
  • Are subcontractors disclosed, and does the vendor flow the obligations down?

If a vendor cannot produce a countersigned agreement this week, treat that as an open finding, not a scheduling inconvenience. You can produce a signature-ready business associate agreement through a guided wizard in less time than it takes to chase the vendor's legal team for a third round of edits.

The Risk Analysis Has to Name the Telehealth Stack

A security risk analysis that describes "the EHR" and stops there does not cover the way care actually moves through your practice now. Virtual visits introduce home networks, personal devices, waiting-room queues visible to staff, recorded sessions, and links delivered by email or text.

Each of those is an item to inventory, assess, and either mitigate or accept with a documented rationale. If your last risk analysis predates your telehealth program, it is stale, and staleness is one of the most common findings in OCR resolution agreements. Practices that would rather not rebuild the document set by hand can generate a current risk analysis and the supporting policy set and spend the recovered hours on remediation instead of formatting.

Virtual Visit Records Are Part of the Designated Record Set

A patient who had a video visit in November calls in January and asks for "everything from the telehealth appointment." Your obligation runs on the same clock as any other request: act within 30 days, with one 30-day extension available if you notify the patient in writing of the reason and the new date. HHS explains the scope and the fee limits in its right of access guidance.

The complication is that telehealth records often live in more places than office records do. The clinical note is in the EHR. The consent may be in the platform. A chat transcript may sit in the video vendor's system. A recording, if one exists, may sit somewhere neither you nor the clinician has looked in months.

Decide now, in writing, what your practice considers part of the designated record set for a virtual encounter, and make sure the answer matches what the platform actually retains. Then make sure your records custodian can retrieve all of it without a support ticket that takes eleven days.

Recording: Default to Off

If your platform records sessions, you have created a category of PHI with its own storage, access-log, retention, and disclosure obligations — and in some states, consent requirements that go beyond HIPAA. Most practices do not need recordings. Turn the feature off at the account level, document that you did, and require a written exception process if a clinician wants it on for a specific purpose.

When the Claim Denies, the Audit Trail Is the Argument

Denials on anthem telehealth claims tend to cluster around a few causes: the member's plan did not cover the service virtually, the modality documented did not match what was billed, the provider was not licensed where the patient sat, or the place-of-service convention shifted and nobody caught the bulletin.

Log every telehealth denial in a single tracker with the reason code, the plan type, and the resolution. Review it monthly. Three denials for the same reason is not bad luck; it is a broken step in your workflow, and the tracker tells you which one.

Appeals move faster when the encounter note already establishes modality, both locations, times, and consent. That is the entire argument, written before anyone knew it would be needed.

A 45-Minute Quarterly Review You Can Actually Run

Put this on the calendar four times a year and give it to a named owner:

  • Pull the current payer telehealth policy and compare it against your internal one-page reference. Update and date the reference.
  • Sample ten virtual encounters. Confirm note-to-claim agreement on modality, locations, and times.
  • Reconcile the vendor list against signed BAAs. Flag anything unsigned or expired.
  • Confirm recording remains disabled and check who holds admin rights on the platform.
  • Review terminated staff against platform access lists. Virtual care tools are a frequent offboarding miss.
  • Review the denial tracker for repeating patterns.

Write down what you reviewed and what you changed. The record of the review is worth nearly as much as the review, because it demonstrates an ongoing process rather than a one-time cleanup. Practices that want federal-source background on program operations can start at HHS's telehealth resources for providers.

Where to Start Monday

Take one hour. List every system that touches a virtual visit, mark which ones have a countersigned BAA, and check whether your risk analysis mentions any of them by name. Whatever is missing after that hour is your Q1 work plan.

If the gap is documentation — a risk analysis that predates your telehealth program, policies that never got updated, agreements that were never countersigned — building the compliance document set from a structured assessment gets you to a defensible baseline in days rather than quarters, and leaves you free to fix the workflows the assessment exposes.