Hospitals run a continuous courier network: samples to the lab, drugs to wards, linen to docks. Porters are scarce, elevators are contended, and late samples have clinical cost, not just labour cost.
The robot has to behave in a social space. Blocking a crash cart path, getting stuck in a lift lobby, or needing a chaperone on every floor turns the project into theatre.
Requirements are stated with the reason they exist. A requirement without a reason is a preference, and preferences are how a shortlist quietly becomes a recommendation.
Without lift I/O the robot stops at every floor change and a person is back on the route.
Open trays fail pharmacy and chain-of-custody rules.
Night shifts cannot babysit charging.
Infection control will reject a robot that cannot be wiped to protocol.
Aggressive navigation that works in a warehouse is a hazard beside a patient.
These are not weaknesses to trade off against a high score. Any one of them ends the conversation, which is why they sit outside the scoring entirely.
Shipping robots in our catalogue whose class matches this job, listed under the industrial weighting so you can scan them — not a recommendation. Reliability and safe behaviour around patients matter more than developer openness.
Order follows the industrial profile score. Requirements and disqualifiers above are editorial; they do not remove robots from this list. How the score works
Compare candidatesRepeated pilots, fewer scaled fleets than the press implies. Clinical stakeholders care about infection control and lift politics more than autonomy demos. Sites that succeed start with one boring route (lab samples) and expand only after the elevator vendor and facilities team are signed on.
