Interventional Radiology Scheduling for the Procedure Suite

Interventional radiology scheduling breaks the assumption every scheduling system is built on, which is that a request maps to an appointment. Here a request maps to a sequence. There is usually a consult, then the procedure itself in a room with its own constraints, then a follow-up, and the patient on the phone is asking for one thing while the calendar needs three.

The failure mode is not that the sequence is hard to understand. It is that nothing enforces it.

At one vascular group roughly ninety percent of visits were an imaging study paired with a provider visit, booked together with specific spacing between them. That pairing lived entirely as convention among the schedulers. It was not in any template, and the patient simply called asking to see the doctor.

So the predictable thing happens. One leg gets booked and the other does not. The second half of the workflow silently does not exist until somebody notices it in a review, which is usually the day before or the day after.

The reminder layer makes it worse rather than better. Reminders in most systems fire on the chronologically first appointment, so a patient with a morning study and a mid-morning provider visit gets reminded about one of them and misses the other. The system was working. The patient was still half absent.

Book the set, not the appointment

The unit of work has to become the sequence, and that is a design decision before it is an automation one.

A procedure request expands into its constituent bookings according to your own rules: what has to precede the procedure, what spacing is required between the steps, what has to follow it, and which of those can be provisional. The automation offers the set, confirms the set, and treats a partially booked set as an open item rather than as a completed call.

athenaOne gives this a place to live. Appointment types encode what each leg actually is and how long it takes, scheduling templates decide where those types can sit, and the open-slot search runs against both. Once the linkage is expressed as types and rules rather than as scheduler habit, an incomplete set is detectable instead of invisible.

The reminder problem needs solving at the set level for the same reason. Confirmations and reminders go out per leg, and the readiness call covers the whole sequence, because a patient who confirms one appointment has told you nothing about the other.

The room is the constraint, and it is not the same as the calendar

Procedure suite capacity behaves differently from clinic capacity, and treating them the same is how a schedule ends up unbookable.

A suite slot needs the room, the interventionalist, the staff for that procedure, and whatever coverage your sedation protocol requires, all at once. Any one of those missing makes the slot fiction. And the day has a hard back edge that is not closing time. Procedure blocks commonly end early because of preparation and turnover between cases, so the last bookable procedure sits well before the practice closes.

Template mechanics add friction on top. Generic interchangeable slots will return availability for a case that needs far longer than the block can hold, and changing a slot’s duration to fit usually means freezing or removing the neighbouring slots to make room. That is a real operational cost, which is why it is worth encoding the durations correctly once rather than adjusting them case by case.

The practical rule is that eligibility gets checked before availability. A slot that cannot hold the case should never be offered, which means the constraint has to be in the type definition rather than in the head of whoever is answering.

Readiness is a sequence of confirmations, not a single call

The pre-procedure call is the highest-value automated call in this segment, because a case that cancels on the day costs the room as well as the appointment.

What it covers is entirely administrative and entirely checkable. Confirm the date and arrival time for each leg. Restate the preparation instructions your protocol specifies for this procedure, in the patient’s language. Confirm the escort, since a patient who cannot drive home and has nobody coming is a cancellation that happens in the waiting room. Confirm any required paperwork came back. Confirm required values are on file where your protocol calls for them.

When something is missing, the useful move is to fix it while the calendar can still absorb the change. Resolve it on the call, or move the case deliberately, or release the slot early enough that the waiting list can take it.

No-shows and late cancellations remain a live problem for practices, and in a procedure suite the cost per event is much higher than in clinic. That asymmetry is the whole argument for making the call every time rather than on the cases somebody remembered.

Backfill closes it. A suite slot released three days out is a slot another patient can use, and offering it automatically is a call nobody currently has time to make.

Where the automation stops

This segment sits close to the line, which is exactly why the line has to be stated rather than implied.

The automation does not decide what procedure a patient needs, does not determine whether a case is appropriate for the suite, does not evaluate what a patient reports, and does not order anything by urgency based on what it heard. All of that is clinical work performed by your interventionalists and clinical staff.

What it does is take a decision that has already been made and turn it into a correctly built calendar. Match the ordered procedure to eligible appointment types, respect the sequencing and spacing rules, respect the room constraints, confirm readiness, and reschedule when readiness fails.

Exceptions route immediately with context attached. A patient describing something that your protocol says a clinician must review, an ambiguous order, a request that does not fit the type it was sent under, or anything about the procedure itself goes to a person with the order, the booked set, and the constraints already assembled. The contribution is that the exception reaches a qualified person sooner rather than sitting in a callback queue.

What referring practices notice

The visible outcome is access, which is what the offices sending you cases actually judge.

A referring practice does not see your template design. It sees whether its patient got booked on the first call, whether the whole sequence got booked, and whether the case happened on the day it was scheduled. Practices consistently rank wait times and phone responsiveness at the top of their own patient access priorities, and a referral source that has to call twice draws its conclusions quickly.

Internally the change lands on your most experienced schedulers. The sequence logic stops depending on who picked up, and their day shifts toward the cases that genuinely needed judgment rather than the ones that needed somebody to remember a rule.

Key Takeaways

Make the booking unit the sequence, since a procedure request expands into a consult, a suite slot and a follow-up with required spacing between them.
Treat a half-booked set as an open item, because nothing in a standard scheduling template enforces the pairing that your schedulers hold as convention.
Send confirmations and reminders per leg, as reminders that fire on the first appointment leave the second one unconfirmed.
Check suite eligibility before availability, and respect the turnover cutoff that ends procedure blocks well before closing time.
Run a readiness call covering preparation, escort and paperwork on every case, and release the slot early enough for backfill when it fails.

A procedure suite is the most expensive calendar in the practice and the one most likely to be booked by convention. Express the sequence as linked appointment types, let the room constraints filter the search before availability does, confirm readiness on every leg, and route anything clinical to a person immediately. The procedures are unchanged. What changes is how many booked cases turn into performed ones.

Sources