Reading Rochester's 100,000 Moxi Trips Before You Budget

What did Rochester Regional Health actually report?

In August 2026, Finger Lakes 1 reported that Moxi robots at Rochester General and Unity Hospitals had passed 100,000 trips. The same report said Rochester Regional Health estimates more than 50,000 staff hours have been returned. The first figure is a count. The second is the system's estimate, and it has not been independently audited.

The count breaks down unevenly. More than 75,000 deliveries happened at Rochester General and more than 25,000 at Unity, with operations running since 2023. The tasks named were medications, supplies and lab specimens. Walking saved for staff was estimated at about 55,000 miles, or roughly 120 million steps.

No separate primary release from the health system turned up in this review, so the account here rests on that Finger Lakes 1 report and the vendor material around it.

Why a trip count does not measure labor

A trip is a unit of activity, not a unit of time. A short run to a supply room and a longer run that rides two elevators can both register as one trip. Hours returned depend on how long the manual version of each run took, how often staff would really have made it, and whether the freed time went to other work. If it did not, it may have simply stopped or never been tracked.

None of the sources reviewed defines what counts as one trip or explains how a run with several stops is logged. Until a hospital publishes that definition, 100,000 tells you about volume and very little about labor.

How was the 50,000 staff hour estimate built?

No method for the staff hour estimate appeared in the sources. The walking figures come from the same system estimate. Turning steps or miles into staff time needs assumptions: a walking pace, the share of a shift spent walking, and a value for that time. Each assumption can move the total a long way, and none was published in what I reviewed.

That does not make the estimate wrong. It makes it impossible to verify from the outside, and a budget committee should treat it that way.

Which numbers belong to whom?

Three sets of figures often get blended in budget decks. Rochester's trip count and hours belong to the health system. Diligent Robotics, the maker of Moxi, reports fleetwide totals. The Robot Report says Moxi has surpassed 1 million deliveries across its fleet, and it reported a milestone of 300,000 pharmacy deliveries. Diligent separately announced more than 100,000 autonomous elevator rides across U.S. health systems as a Q4 2024 milestone.

These totals are reported by the vendor, span many sites, and do not measure Rochester. They can serve as background. They should not be the proof in a local case. Serve Robotics agreed in January 2026 to acquire Diligent Robotics, which belongs on any vendor risk review alongside service continuity.

What does Moxi 2.0 change for the baseline?

The Robot Report, dated August 17, 2026, describes Moxi 2.0 as delivering faster and more confidently, with longer operating hours. The model was first unveiled in October 2025.

That matters for baselines. If a site pools trips logged under older and newer software, a single count mixes two generations of performance. Ask which software version produced each log entry before you set two periods side by side.

Which questions should you ask before repeating the claim?

Put these questions to any health system or vendor before a figure reaches a budget line. An answer that comes back as a fleet total with no log behind it is a marketing figure, and should be treated that way.

• What exactly counts as one trip, and are multistop or aborted runs logged separately?
• What manual baseline was used for each task type, and who measured it?
• Were freed hours reassigned, reduced or left idle, and how was that tracked?
• Was the staff hour figure modeled or sampled, and which assumptions drive it?
• Which software version and fleet size produced the log data?
• Can the raw trip log be exported with timestamps, locations and outcomes?

How can a facility team test the claim on its own floors?

Start with a sampling window before any lease talk. Record what staff do now on the task a robot would take over, such as a specimen run or a medication transport, and time it. Pair that with trip logs from a pilot unit. The gap between the two, not the headline, should drive the decision.

This is the work Service Robot Co. does. We are OEM neutral. We pick the robots that fit the task across manufacturers, then finance, deploy, integrate, train and service every unit through a nationwide US engineer network. We lease through a three year lease, with one fixed payment quoted after a site assessment, so that cost line stays fixed in your comparison for the term. A hospital delivery robot lease only makes sense if the gap your sampling shows is large enough to justify it.

What the 100,000 figure does prove

The 100,000 figure proves volume. Moxi units completed 100,000 deliveries across two hospitals, and that is a real operating result. It does not prove a labor saving of any particular size, and it does not prove the same saving would appear in a building with different floors, staffing and traffic.

Use the claim to sharpen your questions. Do not use it to set a number in the budget.