Key takeaways
- A hospital route is a chain of permissions: elevator, doors, quiet zones, then a named handoff.
- Elevator integration is real but partial; one UK hospital integrated 7 of its 28 elevators.
- Doors that work for people may still need a controller or an access permission before a robot can use them.
- Quiet-zone limits belong in the route file, with their own hours and speed rules.
- A route is only as good as its handoff, so every run should end at a named person or station.
How is a routine hospital run actually built?
A routine supply or specimen run through a hospital wing is built from permissions, not from a single map. The robot has to reach the right floor by elevator, pass doors it can open or be admitted through, respect quiet-zone limits, and stop where a named person takes over. Each leg is a yes or no check before the route goes live.
The result looks dull from the nurses' station, and that is the point. The value is repetition: the same corridor, the same handoff and the same timing, run correctly on a Tuesday night as on a Monday morning.
Why do elevators decide the timing of a run?
Elevators are often the longest uncertain wait in a route. According to Elevator World, Otis enabled AGV integration with 7 of the 28 elevators at Midland Metropolitan University Hospital in the UK, as reported in January 2025. The other 21 cars sit outside that integration.
A route survey therefore lists which cars the robot may call, at which hours, and how long a wait the run can absorb before it reroutes or flags staff. ChristianaCare's nurse-led program document reports elevator integration as a first and about 8,300 miles traveled from April 2022 to August 2025. That document comes from the program itself, and we have not independently verified it.
What do door interfaces need before a robot can pass?
Doors are where many routes quietly fail. A 2022 Frontiers study describes a robot that had to pass two semi-automated doors. With no central door automation server, the team retrofitted controller units to open the doors programmatically.
For a route survey, that means recording how every door on the path opens: by hand, by push plate, by badge reader or automatically, and who can authorize the robot through it. A door that works for a person can still need a controller or an access permission before a machine can use it.
How do quiet-zone rules change a route?
A quiet zone is a corridor where speed, noise and stopping behavior matter more than the shortest path. Patient rooms, rest areas and wards with sleeping patients usually call for slower passes, wider clearance and scheduled windows when the robot stays out. Those limits belong in the route file itself, not in a memo.
Because the limits change by hour, a good route carries two timetables: the hours the robot may enter, and the speed and pause behavior it uses while inside. Staff on the unit should know both before go-live, so that a robot pausing in a hallway reads as expected rather than as a fault.
Where does the run hand off to staff?
Every route ends at a named handoff point, not at a vague drop-off spot. That point is a receiving station with a known staff role, a confirmation step and a clear rule for what happens when nobody answers. For specimens, the handoff is also part of custody, so the record has to show who received the item and when.
Hospitals set their policies for specimen custody and staff notification, and a route should follow those policies rather than invent new ones. The robot delivers to a defined person or station; the hospital decides who that is.
What does the fleet record say about scale?
An older Aethon press release, which is vendor-reported and dated, claimed more than 400 TUG robots making more than 50,000 deliveries per week in US hospitals. Treat that as the vendor's own figure, not an independent count. It does show that hospital routes can run at volume once the permissions are set up well.
For a single wing, the more useful question is not fleet size but route count: how many distinct legs the wing needs, and which of them can be scheduled reliably. Start with the legs that repeat every shift.
Where does Service Robot Co. fit in a hospital route?
We are an OEM-neutral integrator, so we start from the route rather than from a catalog. We select the robot that fits the elevator, door and quiet-zone survey, then arrange the lease, deployment, integration, staff training and service through our nationwide US engineer network.
Our offer is a 3-year lease with one fixed payment, quoted after a site assessment. The assessment is where the route rules above get written down, so a hospital team knows what it is agreeing to before a robot enters a corridor.
How do routes keep working after go-live?
A route that worked in its first week can drift. A door gets a new badge reader, an elevator goes out of service for maintenance, or a unit changes its quiet hours. The fix is a named owner who reviews the route file whenever the building changes, and a service path that reaches an engineer quickly when a leg stops.
Route logs are the early warning. Missed elevator calls, repeated waits at one door and handoffs that run late are patterns worth reviewing every week, long before they turn into complaints from the floor.
Frequently asked questions
Want a robot working for you?
Tell us the job and the site. We will recommend the robot, quote the lease, and keep it serviced.
Sources
- Elevator World: Robots integrate with Otis elevators at Midland Metropolitan University Hospital (UK)
- ChristianaCare nurse-led innovation program document (program-produced, not independently verified)
- Frontiers in Robotics and AI, 2022 study on robot passage through semi-automated hospital doors
- Aethon press release on TUG installations in US hospitals (vendor-reported, dated)