No fully autonomous or remotely teleoperated surgical robot is cleared for use in the United States. As of July 2026, FDA says, none has been granted marketing authorization. On November 6 the agency published a discussion paper asking how it should weigh benefit and risk when one arrives, and the public docket stays open until January 5, 2027.
For a hospital, the useful work starts before any application lands. Most of it has nothing to do with the robot.
The paper is titled "Evaluating Benefit-Risk in Robotic Medical Devices with Autonomous or Remote Teleoperation Capabilities." FDA states plainly that this is not draft or final guidance. What it contains is fifteen numbered questions, and the agency wants answers.
Partial autonomy is not new. FDA notes that robotic systems with autonomous capabilities have been on the U.S. market for years. The new territory is full autonomy and an operator who is not in the building.
It is closer than it sounds. MedTech Dive reported that in October a surgeon performed a robotic prostatectomy from about 35 miles away under an investigational device exemption.
Every robotic case I have seen has a person at the bedside who matters more than the console. They dock the arms. They swap instruments. When something goes wrong, they are the first pair of hands on the patient.
In a remote case that person is the whole contingency plan.
The paper's questions circle that moment without naming it. Question 6 asks about automation bias and delays in override and control transition. A later question asks how teams manage emergencies and convert to a manual procedure. Another asks what happens as the on-site clinician shifts from doing the operation to watching it.
A surgeon three states away can be brilliant. If the line goes quiet for four seconds with a vessel half-divided, the outcome belongs to whoever is scrubbed at the table, and to whether anyone ever rehearsed it.
| Operator location | Bedside backup | Licensure question | Network exposure |
|---|---|---|---|
| Next room, same hospital | Surgeon can walk in | None new | Internal network |
| Another hospital, same region | Local team only | Usually same state | Hospital-to-hospital link |
| Another state or country | Local team only | Interstate or international | Carrier and internet path |
The further the console, the more the outcome rests on people the remote surgeon has never worked with.
Read the paper. It is short and the questions are good.
Send FDA a number. If your surgeons and anesthesiologists have a view on the latency they would accept before they want a human hand on the instrument, the docket is where it counts. The agency asked and has no answer of its own yet.
Then run one tabletop drill with your robotics team: the console goes dark at minute 40. Who moves first?
If the console went dark at minute 40 tomorrow, who in your OR would move first, and have they ever practiced it?
Sources: FDA, "Evaluating Benefit-Risk in Robotic Medical Devices with Autonomous or Remote Teleoperation Capabilities," discussion paper, November 2026, docket FDA-2026-N-13135; AHA News, November 9, 2026; MedTech Dive, November 9, 2026.
Dr. Sarah Matt is a surgery-trained physician-executive currently practicing internal medicine (charity care). She advises health systems and digital health companies on clinical AI implementation, vendor contracting and operational strategy.
Weekly clinical reality on AI, governance, and what actually works inside health systems.