FDA published draft guidance on 25 September 2026 laying out, in one document for the first time, what it wants to see in a premarket submission for a robotically-assisted surgical device (RASD) — the teleoperated, software-controlled systems that have quietly become standard equipment in operating rooms across urology, gynecology, general surgery and beyond. The draft covers nonclinical testing, clinical evidence, human-factors work, software interoperability, emergency procedures and cybersecurity, and it draws a deliberate line around what it does not yet reach: fully autonomous or remotely operated systems, which FDA is handling separately.

Why a guidance document, and why now

Robotic surgery is not new to FDA review — the agency has cleared systems in this category for close to three decades, mostly through the 510(k) pathway on a device-by-device basis. What has been missing is a single reference document telling sponsors, in one place, what FDA's current thinking looks like across nonclinical bench testing, the clinical evidence needed to support a new indication or platform, the human-factors validation work expected for a teleoperated control console, and the cybersecurity documentation now standard across networked medical devices. Submissions have instead been shaped case by case, through individual review interactions and a scattering of general device guidances. This draft consolidates that thinking specifically for RASDs, which the agency defines narrowly enough to leave real edge cases — and leaves them for a reason.

What counts as a robotically-assisted surgical device here

FDA's working definition is a teleoperated, software-controlled system built on a leader/follower control architecture, where a qualified practitioner remains in direct control or under direct supervision, using the robotic platform to precisely position and manipulate one or more surgical instruments. The draft allows for some automated functions layered on top to augment the practitioner's own capability — motion scaling, tremor filtration, and similar assistive features are the kind of thing this covers — but the practitioner stays the one driving the procedure.

The line FDA drew around autonomy and remote operation

Two categories are explicitly carved out. Pre-operative planning and stereotaxic navigation systems — computer interfaces, tracking sensors and navigated instruments used to locate anatomy in three dimensions before or during a procedure — are a different regulatory conversation and sit outside this guidance entirely. More consequentially, systems that are remotely teleoperated, or that perform significant portions of a procedure autonomously without a practitioner's direct, real-time control, are also excluded from this draft's core recommendations, even though the agency notes some of the same principles may still apply. That is not an oversight: FDA has a workshop scheduled for December specifically to work through the technical, safety and regulatory questions that remote and autonomous robotic surgery raises on its own terms, rather than folding a much harder problem into a guidance built around today's practitioner-controlled systems.

What submission teams should do with this now

  • Map current programs against the scope definition — a platform with any remote-operation or autonomous-function roadmap should not assume this draft's recommendations will carry over cleanly to that later submission.
  • Read the human-factors and cybersecurity sections closely — these are the areas the trade press covering this draft flagged as most fully fleshed out, and the areas most submissions have historically negotiated ad hoc with review staff.
  • File comments by 24 November 2026 if scope, testing expectations or the autonomous/remote carve-out affect a program in development — this is a draft, and FDA explicitly revises drafts based on what comment periods surface.
  • Watch the December workshop for the separate, harder conversation on autonomous and remote systems, which this guidance deliberately does not resolve.

Frequently asked questions

What did FDA publish on 25 September 2026?

Draft guidance titled "Robotically-Assisted Surgical Devices — Premarket Submissions," Docket No. FDA-2026-N-9505, on the nonclinical, clinical, human-factors and cybersecurity evidence FDA wants in a premarket submission for these devices.

How is FDA defining a robotically-assisted surgical device?

A teleoperated, software-controlled, leader/follower system that helps a qualified practitioner directly control surgical instruments during open, minimally invasive or endoluminal procedures, potentially with added automated functions.

What is explicitly out of scope?

Pre-operative planning and stereotaxic navigation systems, plus remotely teleoperated and fully autonomous robotic surgical systems — though FDA says some recommendations may still be relevant to those.

How do I comment, and what happens next?

Submit comments to Docket FDA-2026-N-9505 by 24 November 2026. A separate FDA workshop in December addresses autonomous and remote robotic surgical systems specifically.

Sources & further reading

  1. FDA, “Robotically-Assisted Surgical Devices—Premarket Submissions; Draft Guidance for Industry and Food and Drug Administration Staff; Availability,” Federal Register, 25 September 2026 (Docket No. FDA-2026-N-9505). federalregister.gov
  2. FDA, “Robotically-Assisted Surgical Devices - Premarket Submissions” guidance document page. fda.gov
  3. MD+DI, “FDA Releases Draft Guidance on Robotically-Assisted Surgery.” mddionline.com
  4. MobiHealthNews, “FDA releases draft guidance for robotic surgical devices.” mobihealthnews.com

Regulatory News reports on public regulatory documents. It is not legal advice, and the primary sources above govern. If we have made an error, we will say so in public: see corrections.