Pre-Surgical Coordination Calls Across Three Departments

Pre-surgical coordination calls are the least visible work in a thoracic practice and the easiest to get half done. One case can mean an imaging appointment in one department, a pulmonary function test in another, and a pre-operative visit in a third, each with its own template, its own lead time, and its own front desk. Your coordinator books the first one, gets pulled onto the phone, and the other two exist only as a note she meant to come back to.

The scheduling template does not know that these three appointments belong to each other. It holds slots. The relationship between them lives in a coordinator’s head, in a paper checklist, or in a chart note nobody queries.

So the failure is never dramatic. It is one leg of a three-leg sequence quietly not existing, discovered when the surgeon opens the chart the day before and the study is not there. Then the case moves, the block hour goes unused, and someone calls the patient to explain.

Medical group leaders already know where the pressure is. An MGMA Stat poll on patient access priorities found no-shows (27%) topped the list, with online scheduling (24%), phone access (22%), and wait times (21%) close behind. A missed leg of a surgical sequence reads as a no-show in your numbers and as a lost week in the patient’s.

One surgery, three bookings, three front desks

Pre-operative work in thoracic surgery is a dependency graph rather than an appointment. Something has to happen before something else, and the order is not negotiable. A study read has to exist before the pre-operative visit is useful, and the pre-operative visit has to exist before the case can hold a date.

athenaOne carries the pieces you need to run that as a sequence instead of a memory exercise. Outstanding orders on the encounter say what still has to be scheduled. Order documents in the chart say what was requested and by whom. Open appointment slots across departments say what is actually available, per appointment type and per provider group.

The automation reads all three, works out which legs are still missing, and books them in an order that respects the dependencies. Your coordinator opens a sequence that already exists with one item flagged, rather than a blank checklist.

The second leg is the one that disappears

The common failure in linked scheduling is booking one leg and never booking the other. The first appointment is the one the patient called about, so it gets made while somebody is on the phone. The second exists only as an intention.

Nothing in a standard scheduling template enforces the pairing. It is convention, held by whoever has been there longest, and it leaves with them. When a practice runs multi-stage visits at volume, that convention is doing load-bearing work with no backup.

Automating it means the pairing becomes a rule the system applies rather than a habit a person has. When the second leg cannot be booked because no slot fits the lead time, the case goes into an exception queue with the reason attached instead of silently ending up half scheduled.

Reminders cover the first appointment, not the day

There is a smaller version of the same bug in patient reminders. Native reminders fire against the chronologically first appointment. A patient with imaging at 9:30 and a pre-operative visit at 10:00 gets reminded about one of them and shows up for one of them.

From the practice’s side that looks like a no-show on the second appointment and gets counted as one, which is why no-show numbers in surgical specialties can be misleading. The patient was in the building. Nobody told them there was a second stop.

The fix is unglamorous. Confirm the whole day rather than the next appointment, by text and by call, and re-confirm when any leg of the sequence moves. That is the same discipline behind pre-op calls in an orthopedic practice, applied to a schedule with more moving parts.

Confirming the sequence is most of the work

Coordination in a surgical practice is mostly confirmation. Did the study get done. Did the read come back. Is the pre-operative visit still on the calendar. Does the patient know where to go first and what time.

All of that is administrative, repeatable, and phone-shaped. It is a good candidate for automation and a poor use of a coordinator’s afternoon. The AI works the outstanding order list every day, calls the patients whose legs are incomplete, books what it can against open slots, and closes the follow-up task when the sequence is whole.

AHRQ describes care coordination as deliberately organizing patient care activities and sharing information among everyone involved. The front-office share of that is scheduling and confirming, and it is the share that consumes the hours.

Where it hands back to your team

The AI does not decide what a patient needs before surgery, in what order, or whether they are ready. Those calls belong to your surgeon and your nursing staff, and the automation never has an opinion about them.

What it hands over is a shorter and better-labeled list. A patient who has not completed a study after three outreach attempts. A leg that cannot be booked inside the window because that department has nothing available. A sequence where the surgeon’s date moved and two of three appointments no longer line up. Each one arrives with the history attached and the specific gap named.

That division holds up in practice. Your coordinator stops being the system of record for which appointments exist and starts being the person who resolves the ones that will not resolve themselves.

Key Takeaways

Treat a pre-surgical workup as a sequence with dependencies, not as three unrelated appointments that happen to share a patient.
Read outstanding orders and order documents in athenaOne to find the legs that were never booked, rather than relying on a coordinator’s checklist.
Confirm the whole day for multi-appointment patients, because native reminders fire on the first appointment only.
Send half-booked sequences to an exception queue with the blocking reason attached instead of letting them sit as an intention.
Keep every question about what a patient needs before surgery with your surgeon and nursing staff, and automate only the booking and confirming.

Pre-surgical coordination fails in the gap between one booking and the next, not in anybody’s judgment. Read the outstanding orders, book the legs in dependency order, confirm the whole day rather than the next appointment, and route the sequences that will not close to a person with the reason already attached. Your coordinator gets her afternoon back and the surgeon stops finding out the day before.

Sources