Sheba's Chemo Runs: 40 to 14 Minutes, Read as Company Data

What did Sheba report, in plain numbers?

The headline comes from GIX Internet, the company behind the autonomous delivery work at Sheba Medical Center in Israel. Its October 2026 releases say chemo delivery time at the hospital fell from about 40 minutes to about 14 minutes over 11 months, a reduction of roughly 65 percent. The company also reports more than 9,000 completed autonomous missions across indoor and outdoor routes as of October 2026.

Both numbers are company data. Neither has been independently measured, and the wire summaries that repeat them are relaying the company's own words. That does not make the figures false. It does mean a hospital operations lead should read them as one vendor's account, not as a benchmark that other hospitals can expect to match.

How was the clock defined, and what is missing?

The releases leave open where the clock started: at the pharmacy, at the ward request, or at robot dispatch. They also leave open where it stopped, at the door or at the moment a nurse signed for the drug. Those choices can move a delivery time more than travel speed does, and a reader cannot tell from the headline which one the company used.

The notes do not show how many runs were timed, over which dates, or whether the 40 minute baseline was recorded before the robots arrived. Those details decide whether a before and after comparison means anything. Without them, a 65 percent drop is a striking number with no visible method behind it.

Chemotherapy timing also has a clinical and scheduling side. Orders often tie to infusion chair availability and compounding windows, so a shorter transit can still miss a slot if the order sat in a queue upstream. A delivery metric that ignores the wait before pickup tells only part of the story.

What changes when only three robots are live?

Sheba's public tender permits up to 30 robots. According to the October 20, 2026 release and a Stocktitan summary of it, 3 are currently deployed. That means the reported time reduction comes from a small fraction of the contracted capacity, and the rest of the fleet is not yet doing the work the headline describes.

A small fleet can be an advantage. It is easier to schedule, easier to supervise, and less likely to crowd hallways or elevator banks. It can also mean the robots carry a narrow slice of the hospital's work. The release does not say how the three robots were split across routes, how many chemo runs they carried, or if human couriers covered the rest. Those facts set how far the 14 minute figure can travel.

What do 9,000 missions and the October expansion show?

A mission count measures activity, not speed. A mission can be a quick hop down a corridor or a longer outdoor haul, and the figure combines both route types. Nine thousand missions tell you the system has been used heavily. They do not tell you that any given run arrived sooner than it would have otherwise.

In October 2026, the company announced that bone marrow specimens were moving from hematology to the laboratory, and donated blood from the donation center to the blood bank. That widens the scope of the program. Yahoo Finance reported that the company has not disclosed measured improvements in laboratory turnaround times, staffing efficiency or patient outcomes. The company's own forward-looking language frames reduced transport delays and shorter lab turnaround as expected benefits, which is a different category from results.

How are these systems sold, and how should a buyer test them?

A TipRanks summary of the company announcement says the platform is offered through software as a service and Robotics as a Service models. The company also says its platform works with robots from multiple vendors. That is a company description, not an independent check. The sources do not name the robot hardware used at Sheba, so a buyer cannot tell from the public record which machines produced the timing figures.

Service Robot Co. approaches the same question from the integrator side. We are OEM-neutral, so we select robots across manufacturers, then deploy, integrate, train and service each unit through a nationwide US engineer network. Customers get robots on a 3-year lease, with one fixed payment quoted after a site assessment. For hospital teams, that assessment is where the timing questions above belong, before any number goes into a budget.

Before you accept a delivery-time claim on your own campus, ask any vendor for these items in writing.

• A written definition of the start and stop points for each timed run.
• The number of runs timed, the dates they cover, and how the baseline was recorded.
• How many robots were live during the measured window.
• Who covered runs when a robot was down.
• Staff minutes per delivery, not only transit time.

Where does the claim stop?

The Sheba figures are real enough to report and too thin to copy. They show one vendor reporting a large drop in chemo delivery time, across a deployment that has grown in scope. They do not show a validated improvement, a fleet-wide result, or a measured effect on staffing or patient care.

For a hospital operations lead, the useful move is to treat the 65 percent as a question. Ask what was timed, with which clock, on how many robots, and what staff did in the meantime. A vendor that answers those questions plainly is giving you something you can test on your own floors.