It wasn't automatable until

Moving carts through a hospital wasn't automatable until a robot could navigate without tape on the floor

October 1, 2026 · 3 min read

Hospitals move linen, meals, pharmacy totes, specimens and surgical case carts all day, mostly by hand, through corridors full of people. Automated guided vehicles needed magnetic tape or reflectors and stopped for anything in the way. Mobile robots that navigate on their own map, around people, made the hospital hallway a route a machine can run.

The short answer

The first generation of automated vehicles in hospitals followed tape, wires or wall-mounted reflectors, and they were installed like infrastructure. Change a route and someone re-laid the tape. Leave a wheelchair in the corridor and the vehicle waited. Autonomous mobile robots carry their own map, localize with lidar and cameras, plan around obstacles and people, and can be given a new destination from a tablet. That is what made cart transport between departments a job a robot can take on in a building that was never designed for it.

Why this job resisted automation for so long

Hospital corridors are the worst case for a vehicle: narrow, crowded, shared with beds and visitors, broken up by fire doors and elevators, and changing hour to hour. Fixed-path vehicles handled none of that gracefully. The business case was also hard to see, because pushing a cart is a few minutes here and there spread across nurses, technicians and transport aides rather than a single job title you could point to. Nobody owned the hours, so nobody counted them.

What changed

Natural navigation, the same sensing and mapping that moved into warehouses, arrived in hospital-grade form: robots that read a building once and then find their own way, with safety-rated scanners that slow and stop for people. Integrations with elevators and automatic doors became standard features rather than custom projects. Purpose-built hospital tuggers appeared, designed around the carts hospitals already own, with runtimes that cover a shift and automatic charging. The matrix on this site lists them alongside general-purpose mobile robots, with their published payload and runtime figures and the date we checked them.

What it looks like now

A tugger or a top-module robot picks up a cart at a department, travels corridors and elevators to its destination, and returns or moves to the next job, with staff summoning it from a screen. Sterile case carts, pharmacy totes and meal carts are the usual first routes because they are scheduled and repetitive. The honest frame is clinical hours returned: a nurse or a sterile processing technician who no longer walks a cart across the building is a nurse or technician doing the job they were hired for. Deployment takes longer than in a warehouse because elevators, doors and infection control each need engineering.

What still disqualifies a building

Corridors too narrow for a cart and a bed to pass. Elevators that cannot be integrated. Routes that need a person for handoff, custody or patient interaction anyway. Floors or thresholds the robot cannot cross. And the organizational version of all of these: no department willing to own the hours, the routes and the charging station.

How to find out if yours is automatable

Pick one scheduled route, sterile carts to the operating rooms or meals to a wing, and count the trips a day, the minutes each takes, and who makes them. Walk it and note every door and elevator. That is the whole feasibility study for the first route. Describe it to Joe, the concierge on this site. It will size the robot class against your cart weight, name candidates from the matrix, and tell you plainly which parts of the building the integrator will need to engineer around.

Related on this site

• Case cart and sterile tray transport
• Cart tugging between departments
• Material movement
• Robots for hospitals and healthcare
• A mobile robot is not an arm on wheels