Hospital Delivery Robots: Minutes Saved and Staff Hours

What the Sheba chemo run actually shows

Sheba Medical Center, which the vendor describes as Israel's largest hospital, is the clearest public example of a hospital delivery robot shortening a clinical run. According to GIX Internet and Pulse Equity, average chemotherapy delivery time from pharmacy to treatment units fell from about 40 minutes to about 14 minutes over 11 months. Both companies present this as company data, and GIX states that the figures have not been independently audited.

By simple arithmetic, that is about 26 minutes saved on each chemo run, or roughly 65 percent. A deliverz.ai page labels the same gain as 64 percent, which is a reminder that vendors round differently. Use the raw minutes in your own model, not a vendor's percentage.

Why the single run is the unit to measure

A single run is where the savings are earned or lost. The Sheba figure describes the chemotherapy use case, and GIX says it is not a group-wide average across all deliveries. Any model built on it should stay limited to the same kind of run, time-sensitive and bound for a known treatment unit.

Measure each run from the moment it is requested to the moment the item is signed for at the destination. That window includes the wait for a runner, the walk, the handoff, and any elevator time. A robot that cuts the walk but leaves the wait untouched will show a smaller gain than the headline suggests.

How do run minutes become staff hours?

The conversion is multiplication followed by division. Take the minutes saved per run, multiply by the number of comparable runs in a shift, then divide by 60. The result is hours that could be redeployed, if the hospital chooses to redeploy them.

For illustration only, a hypothetical unit running ten such chemo deliveries a day would free about 260 minutes, or roughly 4.3 hours, on paper. That figure is not a Sheba result. It is what your own run count would produce if the Sheba gap held at your site.

Turning hours into cost per delivery

Cost per delivery is total monthly cost of the robot program divided by completed deliveries in the same month. Total cost includes the fixed lease payment, supervision time, charging and cleaning, and any escort staff who still must ride along. Labor savings are then compared against that total, using your own loaded hourly rate for the staff whose time is actually freed.

We have not found a verified wage baseline or a per-delivery cost for the Sheba deployment, so no such figure appears here. Every input has to come from your payroll, your run logs and your vendor's quote. Leave any cell blank that you cannot source.

What the vendor multipliers do and do not prove

The deliverz.ai press release claims 4X more throughput and 7.5X greater cost efficiency compared with traditional staffing models. GIX's website repeats figures such as "Efficiency vs. manual: +64%," "Delivery throughput: x4" and "Cost vs. staffing: x7.5," labeled as company-reported. These are vendor claims, and the baseline behind them is not published in the material reviewed.

The same caution applies to qualitative statements. Sheba's Chief Transformation Officer said the system "shortens waiting times, reduces the burden on medical teams." Useful, but not a dollar figure. Pulse Equity's coverage also notes that the company has not disclosed measured improvements in lab turnaround, staffing efficiency or patient outcomes from its October 2026 expansion.

How far the Sheba deployment has scaled

According to GlobeNewswire, the hospital's commercial operation began in December 2025. A KuCoin news summary reports that Sheba selected the platform through a public tender permitting up to 30 robots, with 3 currently deployed. Pulse Equity reports more than 9,000 completed autonomous missions across indoor and outdoor routes as of October 2026, while an earlier release gave more than 7,000 as of September 2026. All of these figures are company-reported.

In October 2026, the program extended to bone marrow specimens moving from hematology to the lab, and donated blood moving from the donation center to the blood bank. Those are new lanes, so their savings are not yet part of the chemo figure. The Sheba evidence is best read as a three-robot, single-hospital program, not a proof of network-wide performance.

Where Service Robot Co. fits in a hospital run model

Service Robot Co. is an OEM-neutral integrator. We help select the right robot across manufacturers, then handle financing, deployment, integration, training and service through a nationwide US engineer network, so a hospital works with one partner for the whole lifecycle. We lease robots only, on a 3-year lease with one fixed payment quoted after a site assessment.

That site assessment is where a run-time baseline should be taken. Before any payment is quoted, the route, elevator waits, handoff points and run volume should be logged, so the savings model rests on the building's own numbers rather than a headline.

What to log before you commit to a fleet

A short baseline period will tell you more than any press release. Collect the following for at least several weeks before a pilot:

• Requested-to-delivered time for each run, split into wait, walk, elevator and handoff.
• Runs per shift by destination, including the share that are time-sensitive.
• Runner hours spent on escort or waiting, not just on the route itself.
• Overtime and agency hours tied to the same delivery work.
• Failed or rerouted runs, and how long staff spent recovering them.