Rochester's 100,000 Hospital Robot Trips: Reading the Claim

What the Rochester milestone actually says

Rochester Regional Health reports that its Moxi robots passed 100,000 trips at Rochester General Hospital and Unity Hospital, with the milestone reached in August 2026. The system also estimates more than 50,000 staff hours returned. Both figures are the health system's own estimates, and the sources I could check show no independent audit of either.

That makes the claim a useful starting point and a weak benchmark. A trip count tells you that a robot moved something from one place to another. It does not tell you what counted as a trip, how long the same job took by hand, or how much time the robot spent waiting or charging. The staff hour figure rests on a second estimate built on top of the first, so the two numbers need to be read together and questioned together.

What counts as a trip?

The report summaries I checked do not define a trip. A trip could mean one completed delivery, one leg of a longer route, a return to a charging base, or a delivery finished after a staff member took over a load. Each reading produces a different count from the same robot log, and the headline number carries none of that detail.

Ask for the definition in writing before comparing sites. Find out if failed or abandoned runs are counted, if a robot that paused at a door until someone opened it is logged as a completed trip, and if both campuses use one rule. Rochester's count is split across two hospitals, so that last question matters more than it first appears.

How were the 50,000 staff hours estimated?

The sources I checked give the total but not the method. They do not say how each trip was timed, what baseline was used for the manual version of the same job, or how the hours were measured. Without those answers, the figure is a model output with a hospital's name on it.

A quick check is possible with the published numbers. Dividing 50,000 hours by 100,000 trips comes to about half an hour credited per trip. That is simple arithmetic on the reported figures, not a number the system gave. Half an hour is a generous credit for one hallway run, so a team should ask how the baseline was built before accepting it.

A vendor hosted case study for Mary Washington Healthcare reports over 14,300 hours across more than 27,500 deliveries, which works out to just over half an hour per delivery. Similar ratios from different sites and years do not prove the Rochester figure is accurate. They do show that the implied credit matches what this vendor's public case material reports, and that match is itself worth testing.

Why single hospital numbers are not a like for like comparison

Hospital reported figures use different scopes, time spans and robot counts. Read them as separate case studies, not as a ranking.

• Children's Hospital Los Angeles reported more than 2,500 deliveries and about 1,620 staff hours saved in just over four months in 2023.
• Elmhurst Memorial Hospital reported about 1,800 deliveries a month with two robots, and more than 3,100 hours returned over six months, in January 2023 reporting.
• According to the Finger Lakes 1 report, Rochester recorded more than 75,000 deliveries at Rochester General and more than 25,000 at Unity since the robots began operating in 2023, with four Moxi robots at each hospital.

Two 100,000 milestones are not the same count

Diligent Robotics, the maker of Moxi, announced in 2024 a milestone of more than 100,000 autonomous elevator rides across US health systems. That is a different unit from a delivery, and an elevator ride is not a trip to a bedside or a supply room.

A headline that says 100,000 robot milestone can refer to rides, deliveries or hours. Before sharing any such figure internally, write the unit next to the number.

What did the robots not take on?

The sources I checked describe the deliveries and do not list the tasks that stayed with staff. That silence matters. A trip count can look like workload removed when part of the job still needed a person to finish it.

Put these questions to any vendor or hospital that reports a total. Which deliveries were excluded? Did urgent runs go to staff? Which items required a witnessed handoff? What happened on nights when a unit was out of service or charging? The answers change how much of that trip count can honestly be credited as hours returned.

What the vendor's own totals show

As of October 2026, Diligent Robotics' AWS case study page reports Moxi in 25 US hospitals, more than 1.3 million deliveries and over 600,000 staff hours returned, with roughly 150 employees. Those are company totals, not an independent audit. An earlier company figure, as of September 2023, cited more than 400,000 deliveries and more than 200,000 hours saved.

Vendor totals help set expectations about scale and direction. They are weak evidence for judging one hospital's program. Use those totals to read the market, then require each site to produce its own trip definition and hour method.

Where a site assessment fits

Service Robot Co. is a full service commercial robot integrator, and we work OEM neutral. We pick the right robots across manufacturers for the floor in front of us, then lease, deploy, integrate, train and service each unit through our nationwide US engineer network. Robots are leased through financing on a three year lease, with one fixed payment quoted after a site assessment that maps routes, elevator access and the hours a robot would actually cover.

For a hospital team, that assessment is where a claim gets tested. Before the first robot runs, write the trip definition, the exclusions and the hour method into the pilot scope, and time the same routes by hand for a baseline. Those three documents will tell a team more than any headline count.