# Pathways for Public Hospitals

> Pathways gives public hospitals a pre-admission service that triages elective patients by risk rather than clinic availability. Every booked patient receives a voice assessment by SMS, the risk engine profiles each case against perioperative guidelines, and the anaesthetist receives a generated review list of red-flagged patients only.

*Source: https://getpathways.ai/public-hospital*

## Run the pre-admission service your waiting list needs.

Elective backlogs, utilisation targets, a clinic booked out for weeks. Pathways puts clinic slots where the risk is, generates anaesthetist review lists automatically, and keeps every decision auditable.

## From list import to theatre door.

### Assessments go out in bulk (Monday · Bookings)

The booking clerk imports the elective list. Every patient receives a secure SMS assessment link the day they are scheduled — no phone tag, no paper packs.

### The tracker board, worked (Midweek · CNC)

The CNC sees who has completed, who is mid-interview, who needs a reminder. One click resends a link. Nothing slips.

### Review only the red tier (Thursday · Anaesthetist)

The anaesthetist opens a generated review list: only red-flagged profiles. The clinic sees the moderate tier. Everyone else proceeds.

## Clinic capacity goes to the patients who need it.

Triage by risk, not by availability. The tracker and routing engine turn a paper-driven service into one queue, correctly ordered.

- Clinic slots to moderate-risk patients; anaesthetist time to red flags
- Automated review lists — no manual chart trawling
- Every routing decision auditable for governance and accreditation

## Built to pass your procurement review.

- **Data sovereignty** — AWS Sydney. Patient data never leaves Australia.
- **Audit exports** — Org-wide and per-patient logs, exportable for committees.
- **Role-based access** — Clerks, nurses, anaesthetists each see what their role requires.
- **Model isolation** — No personally identifying information sent to model providers.

## What changes for each role in the service

A public pre-admission service has four people in the loop, and the constraint
sits in a different place for each of them. Pathways is deployed against those
four constraints rather than against the service as an abstraction.

### The booking clerk

The clerk's constraint is volume: an elective list arrives as a spreadsheet and
every patient on it needs contacting. Today that means phone calls that go
unanswered and paper packs that come back incomplete, weeks later, if at all.
Pathways turns the import into a batch send — every patient gets a signed,
time-limited SMS link on the day they are scheduled. The clerk's job becomes
exception handling rather than outbound calling. (How this compares with [posting out paper packs](/alternatives/paper-pre-admission-questionnaires).)

### The clinical nurse consultant

The CNC's constraint is visibility. Without a tracker, "who has been assessed?"
is answered by opening records one at a time. The pre-admission tracker shows
sent, opened, in progress, completed and expired for every booked patient, so
the follow-up work is a filtered list rather than an audit. Reminders are
automatic; resending a link is one click.

### The anaesthetist

The anaesthetist's constraint is time — specifically, the time spent reading
charts that turn out to be unremarkable. Because every completed assessment
carries a severity-tiered risk profile, the review list is generated rather
than assembled: red-tier profiles only, each with the triggering evidence, the
guideline reference and the rule version attached.

### The perioperative lead

The lead's constraint is defensibility. Elective throughput targets and
accreditation both require showing why a patient was routed the way they were.
Every analysis, flag, recommendation and human review is timestamped and
exportable, and because the safety-critical rules are deterministic and
versioned, a decision made in March reproduces identically when it is examined
in September.

## Deployment without an integration project

Pathways runs standalone. The SMS-driven workflow needs no PMS or EMR
integration to start, so a service can begin screening the next elective list
without waiting on an IT project, an interface engine, or a change window.
Integration is available later; it is not a precondition for value.