Scoping a Hospital Patient-Transport Robot Pilot

How should a hospital scope a patient-transport robot pilot?

A hospital should scope a patient-transport robot pilot in four steps before any patient rides: define a phase that moves no patients, pick routes that test real friction, write pause rules and staff handoffs, and set go or no-go criteria in advance. That order matters more than the robot model.

The Florida pilot at Morton Plant Hospital in Clearwater is the reference point most leaders will hear about. BayCare and Rovex announced it on April 21, 2026. As of the sources reviewed, no patients are transported in its current phase and no outcomes have been reported.

The most useful lesson is what that pilot does not yet show. We found no published pause rules, handoff procedures or go or no-go criteria for it or for any other hospital transport pilot, so those have to come from your own team.

What the Florida pilot can and cannot tell you yet

The robot is named Rovi, and it is designed to attach to existing stretchers and beds so patients stay connected to their care teams, according to The Robot Report. BayCare Health System and Rovex announced the partnership on April 21, 2026.

A May 21, 2026 trade headline pairs Rovex with Sphaira and credits Sphaira's navigation. The BayCare and Rovex announcements name no Sphaira role, and The Robot Report ties Sphaira to a separate system at Charite in Germany. Treat a Sphaira role in the Florida pilot as unconfirmed.

Two facts set the boundaries for any planning drawn from this example. Rovex's Crabb told The Robot Report that the current pilot has no patient-transport phase. Outcomes have not been reported, so the pilot is a process reference, not a results benchmark.

Start with a phase that moves no patients

A patient-transport pilot should begin with empty runs. According to FMLink's trade coverage, the Florida pilot evaluates hospital workflows and transport patterns, which is the right first question. Empty runs let staff learn the route, the elevator timing and the handoff habits with no clinical exposure.

Write the scope on one page with four parts: the units involved, the routes, the equipment that attaches to beds or stretchers, and the staff accountable for each step. If a team cannot name the person responsible for a step, that step is not ready for a patient.

BayCare describes Rovi as designed to support staff rather than replace them, by reducing physical strain and operational burden, according to WUSF. Put that framing in the scope document. A pilot that quietly targets headcount will make staff reports less candid, and you will learn less from them.

How to pick routes a pilot can actually test

Choose routes by the friction they create, not by distance. A useful pilot route crosses at least one door type, one elevator or lift, and one zone where people and equipment regularly collide. A route that never leaves a single corridor tests very little.

Vendor material describes navigation and obstacle detection that let a robot move through doors and elevators and avoid equipment, spills and visitors, according to Interesting Engineering. Those are capability claims reported by the vendor, not independent results. Your mapping walk has to confirm each one on your floor.

• Time elevator waits at the hours the pilot will run, not the hours a demonstration ran.
• Walk each route at shift change and at the busiest visitor hour.
• Log every door that needs staff help, including fire doors and card readers.
• Test one route per phase so that any failure has a single cause.

Writing pause rules before the first run

The sources reviewed for this piece contain no published pause rules, handoff procedures or go or no-go criteria for the Florida pilot or any other hospital transport pilot. That gap is the most important finding for operations leaders. Your team writes these rules, and the writing happens before the robot enters the building.

A pause rule names a trigger, a responder and a restart condition. Keep each rule short enough to read at a nurse station. Triggers should cover anything that changes the patient's condition or the path ahead.

• An obstacle that stays in the path past a set wait time
• An elevator that is out of service or a door that does not respond
• A patient alarm or visible change in condition during transit
• Loss of tracking between the robot and the control view
• Any stop requested by a staff member, for any reason

Mapping staff handoffs, step by step

Every transit has at least three handoffs: sending unit to robot, robot to receiving unit, and the return of empty equipment. Each handoff needs a named role, a physical location and a sign-off. Map them on the floor plan, not on a whiteboard in an office.

Ask who holds clinical responsibility for the patient while the robot moves. The sources reviewed do not specify that rule for this pilot, so the scope document has to set it. A reasonable starting rule is a clinician or trained transport staff member accountable for any transit with a patient aboard, signed off before the first patient ride.

Setting go or no-go criteria before the data arrives

Go or no-go criteria are easiest to write before results exist. Pick a short list of measures tied to the decisions you must make: whether each route works, whether staff accept each handoff, and whether pause events stay manageable. Set the threshold for each in advance and record who signs.

No outcomes have been reported for the Florida pilot, so there is no verified benchmark to borrow. Do not adopt a figure from a vendor deck as your threshold. Base thresholds on your own staff hours and current transport delays, and review them at the end of every phase.

Reading the outcomes once they are published

When results arrive, check the denominator first. A result means little without the number of trips, the hours covered, the routes tested and the pause events recorded. A figure without those is a headline, not a finding.

Do not extrapolate beyond the route and unit that were tested. A pilot that worked on one elevator bank has told you about that elevator bank, and little more.

Where a successful pilot leads to a lease decision

If a pilot earns a go decision, the next question is how robots reach the floor and stay serviceable. Service Robot Co. is a full-service commercial robot integrator for US businesses. We are OEM-neutral, so we match the right robots across manufacturers to a site, then finance, deploy, integrate, train and service every unit through a nationwide US engineer network.

We lease robots only, on a 3-year lease with one fixed payment quoted after a site assessment. For a hospital weighing a broader program, that assessment is where the pause rules, route maps and handoff points from the pilot become the basis of the quote. We make no performance claims for any specific robot model in this article.