Moxi 2.0 Reaches U.S. Health Systems: What to Ask

What should a health system ask first?

A new robot version reaching your hospital is a change to a clinical environment, not just a hardware swap. Before anyone signs off, ask four things: what changes in the software, who supports it after go-live, how you confirm your current workflows still run, and what evidence stands behind the vendor's claims.

Diligent Robotics began rolling out Moxi 2.0 to health system customers across the U.S. in August 2026, according to the company's own announcement. The rollout is recent and real, which makes this the right moment to set terms. It is also early, so most of what is public about the platform still comes from the vendor.

What does the August 2026 rollout establish, and what does it leave open?

Diligent announced on August 17, 2026 that it had begun rolling out Moxi 2.0 to health system customers. The company, which Serve Robotics acquired in 2026, names Endeavor Health Edward Hospital, Providence Saint John's Health Center and Children's Hospital Los Angeles as initial sites, and says it is actively taking orders. Those details come from the vendor, and no independent report has confirmed them yet.

Timing deserves a closer look. Earlier Robot Report coverage said Diligent planned to send upgraded robots to hospitals in the first half of 2026, and the August start came later than that plan. A later start is not a warning sign by itself. It does mean your contract should use dates you can measure, not dates copied from older press material.

Anton Robots, checked as of October 2026, reports that most long-term evidence still comes from the previous Moxi generation, because the formal Moxi 2.0 rollout began only in August 2026. The same review notes that payload, speed, dimensions and IP rating are not publicly specified, and that no public list price exists.

What should software upgrade terms cover?

Diligent describes Moxi 2.0 as a platform that delivers more value with every software update. It says its World Model was trained on Amazon SageMaker HyperPod. That is a sales line, and your contract should turn it into obligations.

Ask who authors each release and how often updates ship. Ask if updates reach your fleet remotely, or only during a scheduled visit. Ask what validation runs in your own environment before a new version touches live routes, and whether you can defer an update. Ask how the vendor rolls back a release that changes a behavior your nurses or pharmacists rely on. A written rollback path matters as much as the feature list.

Security belongs in the same clause. The Anton Robots review lists Diligent's stated credentials as HIPAA, SOC Type II and TX-RAMP Level 2, and the reviewer reports these as vendor-listed. Request current attestation documents and confirm that their scope covers the Moxi 2.0 software stack, not only the company's general operations.

How should the service and support path be defined?

Support determines how long a unit sits idle. Ask for response commitments in hours, and ask whether technicians come on site first or triage remotely. Get the spare-unit policy in writing as well. Capacity changes over time: Diligent's Children's Hospital Los Angeles quote describes a fleet that grew from two robots to three.

Connectivity is part of the support path. Diligent says tasks complete without Wi-Fi because safety and autonomy run onboard, with cellular fallback for dead zones. It also describes a collaboration with T-Mobile for Business on hospital network access and future private 5G planning. Ask IT which network the robot uses, who owns the cellular plan, and how a dropout gets logged and reported.

This is where an OEM-neutral integrator earns its keep. Service Robot Co. is a full-service commercial robot integrator. We select robots across manufacturers, then deploy, integrate, train and service every unit through a nationwide US engineer network, so one vendor covers the lifecycle. Robots reach customers through a three-year lease with one fixed payment quoted after a site assessment.

How do you confirm existing workflows still work?

A new version can keep the same name and still change the path, timing or handling your staff depend on. Diligent says the redesigned handles and storage drawers were shaped by nurse and pharmacy feedback, which means the physical interface changed. Do not assume a workflow survived because the robot looks familiar.

Build the test from your own routes. Record the current baseline first, then run the new version beside it for a defined period before cutover. Cover at least these points:

• Map every delivery type the unit handles today, including pharmacy and laboratory runs, and record the time window each one must meet.
• Test elevator and door access on every route. Diligent says no changes to existing hospital infrastructure are required, and facilities should verify that claim for your building.
• Compare the dead-zone map against cellular fallback coverage, and log every dropout.
• Confirm that the new handles and drawers still fit the trays, totes and containers your staff actually use.
• Agree on how infection control cleaning applies to the new handles and drawers before go-live.

What does a realistic deployment timeline look like?

Anton Robots reports that Diligent's general Moxi material describes implementation as little as about 12 weeks. The reviewer calls that a best case. Treat it as an optimistic floor, not a promise. Ask for a milestone schedule that names the site survey, network checks, route mapping, staff training, go-live support and the first formal review date.

A phased start protects the workflows you already run. Begin with one unit on one route, then add units only as your measured results hold. The same phased approach shows whether the upgrade helped or hurt your current operation, which is the evidence your own leadership will ask for.

How much weight should the published numbers carry?

Several figures circulate with the rollout, and each one needs a label. Children's Hospital Los Angeles, as quoted in Diligent's announcement, cites more than 40,000 deliveries and over 16,000 hours of staff transport work. The same quote describes utilization up more than 10 percent in the second quarter alone. These are vendor-published quotes, not an independent audit, and they describe one site with its own fleet and workflows.

Diligent also cites more than 25 hospitals and five years of operations, along with an older figure of over 1.25 million deliveries across three years. Its platform claims include up to nine hours per run, 30 percent faster charging and up to 18 hours of daily operation. Record each figure with its source, and ask the vendor which generation of robot each one describes. Your own site data should decide the case.