Skip to content
Hybot
Request a demo

Healthcare

Service robots for healthcare

A hospital delivery robot moves supplies, meals and non-urgent items between named points on a ward instead of a nurse walking them. Hybot dispatches a robot to any configured point of interest on any mapped floor, and a confirmation waypoint holds the robot at the destination until a member of staff acknowledges the handover.

What this page is and is not claiming

Hybot is a service-robot platform, not a clinical system. It moves a load between two named points in a building, tracks that the movement happened, and reports the robot's state while it does. It holds no patient data, makes no clinical judgement, and is not a medical device.

That boundary is the honest one, and it is also where the value is. The errands that dominate a ward's non-clinical time — supplies from a store to a bay, meals from a kitchen to a day room, items between departments — are exactly the repetitive point-to-point movements the platform was built for.

How a task works on a ward

Every destination is a configured point of interest on a mapped floor. A task names the point, a robot is assigned by the auto-assignment loop weighing priority, distance and battery, and the robot travels. Where a human has to be involved at the far end, the task carries a confirmation waypoint: the robot waits at the destination until a member of staff confirms the step, and only then continues or returns.

A robot can also be dispatched straight to a point without a queued task, which is the simplest form of "bring the trolley here".

Why the mapping matters more here

Hospitals are the hardest buildings Hybot maps, for two reasons: they have many similar corridors, and they get re-measured often. Both are handled by keeping the floor plan and the robot's own point list in a deliberate relationship rather than letting them drift.

Points are imported from the robot and re-placed against a stored affine transform per floor, so alignment is done once. Before any push back to the robot, the translation is re-estimated from linked markers with outliers dropped, so a stale offset is never written. If a bulk of points would move at once, the move is blocked pending review. Forty snapshots of the robot's point list per floor are retained and restorable, and a single Realign action shifts every point by one vector after a relocalisation.

The detail is on robot fleet management across every site and in how service robots navigate.

Monitoring a site you cannot walk around

Each deployment reports to the Central Platform by heartbeat. The platform shows per-project internet, frontend, backend and WebSocket status with one-hour charts, primary and secondary server node state, vendor API reachability and per-project risk analytics. Updates are rolled out per project rather than pushed across every site at once, which in a healthcare setting is the difference between a controlled change and an incident.

Deployments

There is no published healthcare deployment. Nothing on this page is drawn from a hospital, and no figure is offered because none has been measured in a healthcare setting. If that is the proof you need before a conversation, say so in the enquiry and we will be direct about where we are.

Frequently asked questions

Is Hybot a clinical system?

No. Hybot moves things between points in a building. It does not touch patient records, it is not a medical device, and it makes no clinical decision. Anything that would require clinical certification is outside what the platform does today.

Can a robot carry samples or medication?

Whether a robot may carry a given item is a matter of the receptacle, the chain of custody and local regulation, not of the software. The platform moves a load between two named points and records that the task completed; the compliance question has to be answered by the site.

What stops a robot being sent somewhere it should not go?

Robots only travel to configured points of interest, and the point list on the robot is driven from the floor plan with a preview of every addition and deletion before anything is applied. A place that is not a point is not a destination.

What happens if a corridor is blocked?

The robot navigates against a stored map for the fixed structure and its own sensors for anything that moves, so it slows and yields rather than forcing a path. A robot that cannot complete a task reports its state over the live connection instead of failing silently.

Do you have a healthcare deployment we can look at?

Not one that is published. This page describes what the platform does, not a hospital that is running it. A healthcare reference will be linked here when a deployment is live and the site has approved being written about.

Where this fits

This page is part of Smart robotic solutions by industry. If you are working through the topic in order, these are the neighbouring pages.

  • Service robots for hotels

    Hotel service robots carry items between the front desk, floors and rooms, using stored multi-floor maps and named points of interest rather than a person walking.

  • Service robots for warehouses

    Warehouse service robots move loads between named points on a mapped floor, taking the repeated walking out of picking, replenishment and returns handling.

  • Service robots for offices and workplaces

    Office service robots handle internal deliveries, refreshment runs and visitor guidance between named points, and show information on screen between tasks.

Tell us about the venue

Pricing depends on unit count, layout and integration work, so we quote against a real site rather than publishing a package.

Request a quote