Skip to main content

Practice Operations

Hematology Telehealth Appointments and the Cycle Around Them

A hematology telehealth visit sits inside a treatment cycle with lab and chair time booked around it. Here is how AI books the right athenaOne slot type.

9 min read

Hematology telehealth appointments are almost never a standalone visit. They sit inside a treatment cycle that already has a lab draw, chair time, and a provider slot spaced around each other, and the video visit has to land in the one place where that spacing still holds. Book it as a generic virtual slot and the rest of the week comes apart.

Most scheduling tools read a telehealth request as a preference. The patient wants video, the system finds a video slot, done. In a hematology and oncology practice that assumption breaks on contact, because the visit the patient is calling about is one leg of a repeating series and the other legs have hard spacing between them.

The failure is familiar to anyone who has run that front desk. A patient calls to move a visit to video, one appointment changes, and the lab draw that was supposed to come first stays exactly where it was. Nobody catches it until the morning of, when the provider has a video visit on the schedule and the work that was meant to precede it never happened.

Then there is the second half of the same call, the one about money. Cost of care questions ride along with almost every cycle change, and they are not scheduling questions at all.

A telehealth request lands in the middle of a sequence

In a hematology practice the booking unit is rarely one appointment. It is a lab draw, then chair time, then a provider visit, with spacing between them that exists because the sequence has to work in that order. Nothing in the scheduling template enforces the pairing. It lives as convention in the heads of two schedulers, and the patient just calls asking to move their appointment.

The specific trap is that native reminders fire on the chronologically first appointment. A patient with a 9:30 lab draw and a 10:30 provider visit gets reminded about one of them and treats the other as optional. When the provider visit becomes virtual and moves, the lab draw does not move with it.

Automation helps here by treating the set as the set. The linked visits are read together, changed together, and confirmed together, and the patient hears both times read back on the same call. Where it stops is spacing it cannot satisfy inside the window the practice defined, and that goes to a scheduler with the conflict named rather than being forced into the nearest opening.

This matters more than a scheduling nicety. When practice leaders were asked what their top patient access focus would be in 2026, no-shows led the field at 27%, ahead of online scheduling and phone access. A patient who shows up for one leg of a linked pair and misses the other is counted as a no-show and is really a booking defect.

Modality is a property of the appointment type, not a patient preference

Inside athenaOne, virtual and in-person are usually separate appointment types per provider rather than a checkbox on one. So “can we make it video” is really a question about whether an equivalent virtual appointment type exists for that provider, in that department, for that visit reason.

Often it does not, and often it should not. Chair time cannot be virtual. Neither can anything that requires the patient to be physically present, and practices routinely bar the modality at the appointment type level rather than trusting it to be caught at check-in. That is a rule the practice writes once and the system then applies on every call at the same strength, which is the part front desk staff under pressure cannot do.

The honest version of this on a call is short. The automation says the visit type has to be in person, offers the in-person slot, and does not quietly book something adjacent that looks close enough. Converting the request rather than granting it is the correct behavior, and it is the behavior that keeps the schedule truthful.

Payer rules sit underneath all of this. Medicare covers certain telehealth services under Part B, and after the deductible the patient pays 20% of the Medicare-approved amount, the same cost share structure as the in-person visit. Coverage is not the practice’s opinion, so encoding which visit reasons may be virtual is the only place the practice actually gets a decision.

One reschedule cascades through the series

Cycle appointments repeat on a fixed cadence, which means moving one is rarely moving one. Push a visit out four days and every downstream appointment in the series either moves with it or stops making sense.

Authorization makes this sharper. Rescheduling silently breaks the link between an appointment and the approval attached to it, and an appointment whose authorization has not come back can be pushed later but never pulled earlier. A scheduler who does not know that will offer an earlier slot in good faith and create a visit that cannot be billed.

What automation contributes is the re-check. When one visit in a series moves, the rest of the chain is read again, the authorization window is compared against the new date, and any leg that no longer fits gets surfaced instead of silently drifting. The rebooking that is mechanical happens on the call. The rebooking that requires a judgment about what the patient can tolerate goes to the person whose job that is.

The internal handoff matters as much as the booking. A case routed to the named scheduling bucket, with the broken leg and the reason attached, is a thirty second fix for a human. The same problem discovered on the morning of the visit is a wasted chair.

Sending a telehealth link is the easy part. Getting a patient onto the call is a sequence of small administrative steps that practices usually staff with whoever is free, which means it happens inconsistently.

The steps themselves are unglamorous. Confirm the patient has the link and can open it. Resend it to the number they actually answer. Confirm the day before rather than the hour before, because a patient who discovers a problem at 9:55 for a 10:00 visit has no path except cancelling. Check that portal messaging is switched on for that patient at all, since a link delivered to a portal nobody logs into is a missed visit with extra steps.

Hematology panels skew older, and the practical result is that tech readiness calls convert more visits than any reminder cadence does. When the readiness call fails, the fallback is the practice’s rule and not the caller’s improvisation: convert to phone where the appointment type allows it, convert to in-person where it does not.

None of that requires anyone with a license. It is confirmation work, it is repetitive, and it is exactly the shape of work that gets skipped on a busy Tuesday and then shows up as an empty slot on Thursday.

Cost of care questions are a fast human handoff

Almost every cycle change call carries a second question underneath it, and it is about money. What will this one cost, did the authorization go through, why was the last statement different from the one before it.

Those questions need a person, and the useful thing automation can do is get them to that person warm rather than cold. Eligibility gets checked in real time during the call. Any outstanding balance is surfaced. A case is created and routed to the financial counseling bucket with the patient, the appointment, and the actual question attached, so the callback starts with context instead of starting over.

What the automation does not do is answer a benefits question it cannot verify. A confident wrong answer about coverage is worse than a callback, because the patient acts on it. The rule is simple and it holds across every one of these workflows: verify and route, or hand it to staff.

That boundary is not a limitation the practice has to work around. It is the reason the front office can hand the AI the volume in the first place.

Key Takeaways

  • Treat the linked set as the booking unit. A lab draw, chair time, and a provider visit that only work in sequence should be read, changed, and confirmed together, not one leg at a time.
  • Write the modality rule at the appointment type level in athenaOne. Virtual and in-person are separate types per provider, so a visit reason that cannot be virtual should be unbookable rather than caught later.
  • Re-check the authorization window on every reschedule. An appointment whose approval has not returned can be pushed later but not pulled earlier, and a moved visit does not carry its old link.
  • Confirm telehealth readiness the day before, not the hour before. A patient who cannot open the link at 9:55 has no option left except cancelling.
  • Route cost of care questions to a named bucket with eligibility, balance, and the actual question attached. Warm handoffs get answered once; cold ones get called back three times.
  • Define which reasons may be virtual before you automate anything. The automation applies your rule on every call at the same strength, which is only useful if the rule is the one you meant to write.

The hard part of a hematology telehealth visit was never the video. It is everything the visit is attached to, and that is booking work your team is already doing by hand on every call.

Sources

Ready to See It in Action?

See how PGA books a telehealth visit without breaking the rest of the cycle

Schedule a Demo →

Written by Kevin Henrikson