What Rochester's 100,000 Robot Trips Really Show

What Rochester Regional actually reported

In August 2026, Rochester Regional Health said its Moxi robots at Rochester General and Unity Hospitals had passed 100,000 trips. The system also estimates that more than 50,000 staff hours have been returned to staff. Finger Lakes 1 reported both figures, and they come from the system and local press, not from an independent audit.

Read narrowly, the milestone shows that two hospitals ran a large volume of autonomous moves since the robots began operating in 2023. It does not, by itself, confirm the hour savings, the fleet's availability, or the effect on staffing costs. Those claims need their own evidence before a finance team repeats them.

The useful stance for operations leaders is skeptical but specific. Treat the trip count as a usage signal, and treat the hour figure as an estimate to test.

Why a trip count is not a task count

According to the system, about 75,000 deliveries took place at Rochester General and more than 25,000 at Unity. Those two parts add up to the headline total, which is a sensible internal check. Adding them up does not make the count a measure of clinical value.

A trip is a unit of motion. A run that reaches its destination, a run that stalls in a corridor and returns to a charger, and a run a nurse finishes by hand can each look different in a log, and a headline total can hide that difference. Ask whether the 100,000 includes aborted or repeated runs, and how a handoff to a person was counted.

Where the 50,000 staff hour estimate comes from

The staff hour figure is an estimate the system makes, and the public reports do not show the method. The question to ask is how the baseline was set. A time study of staff walks before go live supports a claim. A flat assumption of minutes saved per trip multiplies the trip count and tells you little about what staff stopped doing.

Freed minutes reduce cost only when they change something on the schedule, such as an avoided hire, fewer agency shifts, or overtime that did not happen. Hours returned to staff are not the same as hours removed from a budget. Finance teams should ask which of those outcomes, if any, the system has measured.

Which uptime and downtime records to request

Uptime decides whether a trip count reflects real capacity. A robot that is charging, waiting for an elevator, or out for repair completes no trips, and a fleet total can look strong while one floor goes unserved. Request the availability record for the same period as the trip count, not a rolling average.

A complete request usually includes three records:

• Trip log fields: timestamp, origin and destination unit, elevator used, completed or aborted status, and the reason any run was handed to a person.
• Downtime records: date, unit, cause code, time to restore, and whether a spare robot covered the route.
• Baseline study: staff walks timed before go live, with dates, units included, and the sample size.

How to read the walking and step estimates

The system also estimates about 55,000 miles of walking avoided, roughly 120 million steps. Both are derived numbers. Each depends on an assumed distance per trip and an assumed step length, and neither is an observed count of staff movement.

Derived distances help explain scale to a board. They are weak evidence for claims about fatigue, injury or patient experience, which need clinical and HR data the milestone does not contain. Ask for the per trip distance used in the calculation before citing the figure.

Why Diligent's other milestones use different units

Diligent Robotics has its own milestones for Moxi, and they measure different things. In a November 2024 announcement, the company reported more than 100,000 autonomous elevator rides across U.S. health systems. A later company report put elevator rides above 110,000, and in February 2025 Diligent reported Moxi fleet deliveries passing 1 million.

All three are company figures spanning many sites. They do not confirm any single hospital's hours, and they should not be added to or compared against Rochester's 100,000 trips. Each count stays tied to its own unit and its own denominator.

What a hospital should bring to a robot lease review

Service Robot Co. is an OEM neutral integrator. We select the robot that fits the route, then finance, deploy, integrate, train, and service it through our nationwide US engineer network, so a hospital works with one partner for the whole lifecycle.

For hospital teams, our review starts with a site assessment, and the lease is quoted as one fixed payment on a three year term after that assessment. We suggest the trip log, downtime record and baseline study be part of that review, whichever robot is chosen. Those three files tell a finance team more than any headline total.