A stereotaxic system isn't a RASD

FDA has cleared robotically-assisted surgical systems for two decades without ever publishing a dedicated premarket framework for the category. On September 25, 2026, that changed: a draft guidance, Robotically-Assisted Surgical Devices – Premarket Submissions, announced by Federal Register notice under docket FDA-2026-N-9505, with comments open through November 24, 2026. We flagged this guidance last week as one of the FY2027 A-list’s seven final-guidance commitments; the draft FDA owes before that final version is the one now on the street. For a team building or evaluating a surgical robot, the draft’s most load-bearing work isn’t its testing recommendations. It’s the line it draws around what the document is even about.

What a RASD is

FDA defines a Robotically-Assisted Surgical Device (RASD) as a teleoperated, software-controlled system that integrates robotic technologies and subassemblies to help a qualified practitioner precisely position and control one or more surgical instruments — in open, minimally invasive, or endoluminal procedures, with the practitioner present at a console driving the instrument in real time. That is the category the draft’s recommendations on non-clinical testing, clinical data, and labeling are written for.

Four things the same document says it isn’t

The draft is explicit about where that definition stops, and the stopping points are worth checking a device against before reading another page of testing recommendations:

• Pre-operative planning and stereotaxic systems. A stereotaxic system resolves to tracking sensors and navigated instruments that locate a three-dimensional position against anatomical landmarks — a navigation problem, not a teleoperated manipulator. It is excluded because it is a different mechanism, not a lesser version of the same one.
• Interventional procedures using catheters or other interventional devices. RASD recommendations are written for instrument-positioning robotics, not for the catheter-based delivery systems a separate submission type already covers.
• Remotely teleoperated RASDs. A console in the same room as the patient and a console across a network connection raise different failure modes — latency, connectivity loss, a practitioner who isn’t physically present to intervene — and the draft says so by excluding true telesurgery from its primary scope, while noting that some of its recommendations may still be relevant to one.
• Autonomous robots performing significant procedure steps independent of a practitioner. Same caveat, same reason: a system making its own intraoperative decisions is a different risk profile than one a practitioner is actively driving, even if the hardware looks identical from across the room.

The guidance didn’t fail to anticipate telesurgery and autonomous robotics. It named them, and declined to write their rules yet.

What the exclusion is not

None of the four exclusions is a statement that FDA won’t review a device in that bucket, or will hold it to a lighter standard. It’s a statement that this particular document’s recommendations weren’t written with that device in mind. A stereotaxic system still clears through whatever framework already governs navigation systems; a remotely teleoperated or autonomous surgical robot still needs FDA to decide what applies to it — the draft just declines to be that decision. FDA says as much itself: a sponsor with a device outside the defined scope is directed to the Q-Submission Program for feedback specific to that file, not to wait for a future version of this guidance to say so.

The practical read for a submission team

If your device is a console-driven, co-located instrument-positioning system, this draft is about to become the recommendations FDA reviews your non-clinical and clinical package against — worth a line-by-line comparison against your current test plan before the comment window closes. If it sits in any of the four excluded buckets, the absence of a written framework is not a gap you get to leave open; it’s a reason to raise the question in a Q-Sub now, while FDA is actively working this document, rather than discover the answer inside a deficiency letter later. Which bucket a specific device falls into, and what that means for its own submission strategy, is a determination for your regulatory team to make on that device’s own facts — this is regulatory intelligence and method, never regulatory advice.