Perioperative operations · 20 August 2026 · Pathways

Why clinics fill with the wrong patients

Pre-admission clinics fill with low-risk patients because slots are allocated in the order bookings arrive rather than by screened risk. The result is a clinic of largely well patients while the frail patient with poor functional capacity gets a short phone call. The constraint is allocation, not capability, so adding clinic capacity does not fix it.

Ask a perioperative lead what their pre-admission clinic needs and the answer is usually more of it — more slots, more nursing hours, another consultant session. It is a reasonable answer to the wrong question, and it is why services that successfully expand their clinic often find the day-of-surgery cancellation rate barely moves.

The clinic is not the bottleneck

Consider what a pre-admission clinic actually is: a fixed quantity of skilled clinical attention, allocated among a much larger booked population. The clinical work done inside it is generally excellent. The problem is upstream of the appointment.

Without a mechanism for deciding who should attend, slots are allocated by the only signal available — the order in which bookings arrive. That signal is uncorrelated with risk. The result is predictable and near-universal: a clinic substantially populated by ASA 1 and 2 patients for whom the visit changes nothing, while a frail 82-year-old with poor functional capacity is handled by a fifteen-minute phone call because the diary was full by the time their booking landed.

Adding capacity to a system allocating by arrival order produces more appointments distributed the same way. It is genuinely useful — more patients are seen — but it does not preferentially reach the patients whose assessment changes an outcome.

Why the obvious filters do not work

Services that recognise the allocation problem usually reach first for a triage rule based on something already in the booking data. Two candidates present themselves, and both disappoint.

ASA class is the most common. It is appealing because it is already recorded and it is a clinical judgement rather than an administrative one. But ASA class describes systemic health independent of the procedure, and it is coarse. A large share of the booked population is ASA 2, which includes both a well-controlled hypertensive undergoing a cataract and a patient with a BMI of 38, untreated snoring and a hip replacement ahead of them. Triaging on it fills the clinic with ASA 2 patients, which is roughly where it started.

Procedure type is the other. It correctly identifies that a hip replacement carries more physiological demand than a cataract, and it is completely blind to the patient. It routes healthy patients having major surgery into clinic and sends unwell patients having minor surgery home.

Neither fails because it is a bad measure. They fail because they are single measures, and perioperative risk is a profile.

What the routing decision actually needs

The information that would let a service allocate correctly is not exotic. It is a structured history: current medications verified rather than recalled, functional capacity asked as a concrete question rather than a general one, a sleep apnoea screen, frailty indicators, glycaemic control, and the specific red flags that change an anaesthetic plan.

That information exists. The difficulty is that collecting it has historically required the very clinic appointment being allocated — which makes the assessment its own prerequisite. You cannot triage into the clinic on information only obtainable inside it.

This is the circularity that keeps the allocation problem in place, and it is the thing worth attacking. Not the size of the clinic; the order of operations.

Breaking the circularity

If a structured history can be taken before the clinic — remotely, at scale, without consuming clinical time — then the routing decision has something to work with. Every booked patient carries a screened profile, and the clinic’s finite capacity can be pointed at the patients whose profile warrants it.

The clinic does not shrink and its work does not change. What changes is the population inside it. Anaesthetist review goes to red-tier profiles, clinic slots to the moderate tier, telephone review to patients who need a conversation rather than an examination, and everyone else proceeds.

The second-order effect

There is a consequence that tends to surprise services, and it is arguably larger than the throughput gain.

Once every booked patient is screened at the point of booking, a set of interventions that were previously impossible become schedulable: anaemia correction, glycaemic optimisation, prehabilitation for patients with low functional capacity. These all require weeks of lead time, and none can be initiated from a clinic appointment three days before surgery.

A clinic allocating by arrival order cannot deliver them, not because it lacks the skill but because it meets the relevant patients too late. Screening early turns the wait for surgery from dead time into a window — which is the premise enhanced recovery programmes are built on, and the reason they are hard to run without it.

The question worth asking

“Do we have enough pre-admission capacity?” is not the diagnostic question. A better one is: of the patients who attended clinic last month, for how many did the visit change the plan?

Where that proportion is low, the constraint is allocation. More capacity will be absorbed and the cancellation rate will hold roughly steady, because the patients driving it were never in the room.

FAQ

Related questions

What is Socrates Pre-Op?

Socrates Pre-Op is the Pathways voice agent that takes a structured anaesthetic history from a patient by phone. It is delivered as a secure, time-limited SMS link — no app, no login, no paper questionnaire — and covers 12 clinical domains conversationally, producing structured, severity-tagged findings that feed the risk engine directly.

It is a purpose-built anaesthetic variant rather than a generic intake bot. The distinction matters in practice: a general-purpose intake tool collects answers to the questions it was given, whereas an anaesthetic interview needs to follow up on a positive family history of anaesthetic problems, probe functional capacity when a patient says they are “fine”, and recognise when a described medication is worth photographing.

Completion is tracked, and a finished interview automatically triggers a fresh risk analysis.

How this compares with the two methods it usually replaces — paper questionnaires and telephone pre-assessment — including where each of those still wins.

Which clinical domains does the Pathways interview cover?

The Socrates Pre-Op interview covers 12 domains — surgical context, presenting symptoms, prior anaesthetics, systems review, functional capacity and frailty, airway assessment, medications and allergies, social and risk factors, implanted devices, pre-op investigations, a red-flag screen, and safety and shared decisions.

Every domain produces structured, severity-tagged findings rather than free text, which is what allows the risk engine to screen on them directly instead of re-parsing a narrative.

How does Pathways generate its risk flags?

Pathways screens each case with deterministic, versioned rules referenced to perioperative guidelines. Every flag carries a severity tier, the clinical rationale, the triggering evidence, the guideline reference and a recommended action, plus the rule version that produced it. The same inputs always produce the same flags, months later.

Screening covers the domains that drive perioperative outcomes: unstable cardiac symptoms, marked hypertension, diabetes control and SGLT2 management, obstructive sleep apnoea, frailty, malnutrition, functional capacity, smoking and discharge support.

Pathways also states what it does not know. Missing investigations and unconfirmed timings are listed explicitly on every profile, and extraction confidence is shown rather than hidden — a profile that is 86% confident about a patient-reported HbA1c says so.

Can we audit why a patient was cleared or flagged?

Yes. Pathways keeps org-wide and per-patient audit logs with full workflow tracing on every risk analysis — the inputs used, the rule version that fired, the output produced, and the human who reviewed it, all timestamped. Logs are exportable for governance committees, M&M review and accreditation.

Because the safety-critical rules are deterministic and versioned, an audit is reproducible rather than merely archived: re-running a case against the rule version recorded at the time produces the same flags. That is the property that lets a decision made in March be examined in September without argument about whether the system “would have said something different”.

What happens to patients who are not high risk?

They proceed. Every completed profile carries a triage recommendation — anaesthetist review, pre-admission clinic, telephone review, or no further assessment — so clinic slots go to moderate-risk patients and anaesthetist time goes to red flags. Low-risk patients are not routed into a clinic appointment they do not need.

This is the throughput argument, and it runs in both directions. A pre-admission clinic booked out three weeks ahead with mostly healthy ASA 1 patients is not short of capacity so much as misallocating it. Screening every patient at booking makes the queue orderable by risk rather than by whoever called first.

What happens if a patient doesn't complete their assessment?

The tracker shows exactly where they stopped — sent, opened, part-way through, or expired — and automated reminders go out without anyone chasing. A link can be resent in one click. Because the status is visible per patient rather than inferred from silence, an incomplete assessment becomes a task on a list instead of a discovery on the day of surgery.

Non-completion is normal and expected — it is why the tracker exists. The failure mode worth designing against is not the patient who does not finish, but the service that does not know they did not finish until the pre-admission clinic.

Patients who genuinely cannot complete a remote assessment are then a known, named group who can be routed to a phone call or a clinic slot deliberately, rather than turning up unassessed.

What if a patient has no smartphone, or can't use one?

They are identified as a group rather than missed. The assessment needs only a phone that receives SMS and opens a link — no app, no login, no account. Patients who cannot complete it that way show as incomplete on the tracker, so the service can route them to a telephone assessment or a clinic slot deliberately instead of discovering the gap later.

The design point is that remote assessment does not have to work for every patient to be worth doing. It has to work for enough of them that the clinic’s finite capacity can be pointed at the ones it does not work for — which includes patients without a suitable phone, patients who need an interpreter, and patients who would simply rather come in.

What Pathways changes is that this group is visible in advance and small enough to plan around, instead of being indistinguishable from everyone else on the list.

How long does the assessment take a patient?

Most of a Socrates Pre-Op interview is conversational rather than form-filling, and patients complete it from home in their own time rather than in a clinic slot. It can be paused and resumed, and photographing medications happens during the conversation rather than as separate homework. Duration varies with how complex the patient's history is.

The comparison that matters is not against a stopwatch but against what it replaces: a paper questionnaire that arrives in the post and comes back incomplete, or a phone call at a time that suits the service rather than the patient.

Complexity drives length, which is the correct behaviour — a patient with a long medication list and several prior anaesthetics has more to cover than a healthy patient presenting for a day case, and a structured interview should spend the time where the information is.

See all questions

See your list the way Pathways sees it.

Book a 30-minute demo with a real pre-admission workflow.