Infectious Disease Telehealth Scheduling Across State Lines

Infectious disease telehealth scheduling is a credentialing problem wearing a scheduling costume. The visit itself is well suited to video, the patient is often far away, and the practice usually has capacity. What stops the booking is a four-way question that nobody at the front desk can answer in the twenty seconds they have.

Credentialing resolves per provider, per payer, per state, and per treatment type. All four have to be true before a slot can be offered, and the caller is waiting on the phone while it gets decided. In a small practice with a handful of physicians, one gap in that grid blocks a large share of inbound referrals.

The data that answers it is rarely in the EHR. A multi-state, multi-specialty group may maintain the whole provider-to-plan enrollment picture in a spreadsheet outside the system, kept up by a person, because nothing in scheduling knows any of it.

So the practical outcome is the safe answer. Staff take a message, promise a callback, and the referral joins a queue. The patient waits days for a visit that could have been booked on the first call, and some of them do not wait.

The enrollment grid is a spreadsheet, and the useful version is inverted

The real constraint is that the affirmative provider-to-payer enrollment grid can be too large and too messy to hand to a vendor and keep current.

What they could produce was the inverse. A per-provider list of the plans they do not take. That negative list is a smaller, more stable artifact, and it is enough to prevent the failure that actually costs money, which is booking a patient with a provider who is not enrolled in their plan. The visit happens, and the claim dies weeks later.

For an infectious disease practice with few providers, that check has to run before a slot is offered rather than after. The automation reads the plan on file, applies the exclusion list, and only surfaces providers who can actually see that patient. When the plan on file looks stale, it refreshes coverage on the same call rather than booking on bad data. That mechanic is the same one described in insurance verification.

State is a scheduling variable, not a detail

A group with prescribers across several states may need to ask whether the follow-up and prescribing rules differ state to state. The answer often comes from the medical director rather than the scheduling system.

That is the honest state of multi-state specialty care. The rules exist, they vary, and they are held by a clinician rather than a system. What automation can do is hold the answer once it has been given, applied per provider and per state, and refuse to offer a slot that would violate it.

CMS publishes which services are payable when furnished by telehealth, and practices layer their own state and licensure constraints on top. Both belong in the booking logic. The clinic writes the rule, the automation applies it before offering a time, and anything the rule does not cover goes to staff with the patient’s state and plan already captured.

Which visits belong on video, decided by the clinic

For certain presentations telehealth does not make sense, so the workable pattern is for the clinic to supply both lists: the situations to steer toward video, and the situations never to. That is a clinical determination and it belongs to them.

Once those lists exist, applying them is mechanical. The reason the patient gives maps to an appointment type, the appointment type carries its own modality rule, and the automation offers only what the rule permits. A request that falls outside the list converts to the in-person appointment type the practice designated, or routes to a person.

There is a practical trap here too. A telehealth platform may not let staff open the platform or the patient’s chart unless insurance is active, which turns an eligibility failure into a cancelled visit rather than a billing problem discovered later. That is an argument for verifying coverage at booking rather than at check-in.

Consults arrive as faxes and sit

Infectious disease volume is consult-driven, and consults arrive as flat PDF referrals over fax rather than structured orders. They stack up in an intake queue while the referring office assumes the patient is being handled.

One detail catches almost everyone. During a fax rollout, the pipeline may only process documents whose department is the main office, while a meaningful share of new-patient referrals are filed under other departments where nothing is watching. The EHR may not permit pulling all departments at once, so the sweep has to walk them one at a time.

The fix is unglamorous: sweep every department, register the patient, resolve credentialing and modality, and offer the telehealth slot the same day the referral lands. For a practice where antimicrobial stewardship work is time-sensitive, days in an intake queue are the expensive part, not the visit.

When the answer is that nobody is available

Small practices run into panel limits constantly, and how you say no matters. A practice can write deliberate language for exactly this: the physician a caller asked for is not accepting new patients, but the caller gets steered to the providers who do have availability, without it landing as a brush-off.

That is conversation design rather than a flag in a system, and it is worth writing down properly. The automation uses the practice’s own wording, offers the real alternative, and captures the request when there is genuinely nothing to offer.

Everything clinical stays where it belongs. The automation books, verifies, and routes. Whether this patient should be seen on video, by whom, and how soon is answered by the practice’s rules and, when the rules run out, by a person. Resolving all of that against live provider and appointment data is the case for working inside athena.

Key Takeaways

Resolve provider, payer, state, and visit type together before a slot is offered. Any one of them being wrong produces a visit that happens and a claim that does not.
Ask for the inverse enrollment list. A per-provider list of plans not accepted is smaller, more current, and enough to prevent the expensive error.
Capture state-specific rules once, from the clinician who knows them, and apply them per provider in the booking logic.
Verify coverage at booking rather than check-in. Some telehealth platforms will not open a chart without active insurance, which turns a billing issue into a cancelled visit.
Sweep every athena department for inbound referral faxes. Consults filed under a non-main department are the most common silent backlog.
Write the not-accepting-new-patients script deliberately. Panel limits are a conversation problem, and the alternative offer is what keeps the referral.

For a small infectious disease practice, telehealth capacity is rarely the constraint. The constraint is answering a four-way eligibility question fast enough to book while the patient is still on the phone. That answer lives in provider, plan, state, and appointment-type data, and once it is written down, applying it is administrative work that runs inside athena on every call.

Sources