FDA Releases Draft Guidance on Robotically-Assisted Surgical Devices Premarket Submissions: Nonclinical, Clinical Data, and Labeling Requirements Form a Systematic Framework

FDA Releases Draft Guidance on Robotically-Assisted Surgical Devices Premarket Submissions

On September 25, 2026, the U.S. Food and Drug Administration (FDA) released the draft guidance Robotically-Assisted Surgical Devices—Premarket Submissions. On the same day, the Federal Register published a notice of availability at Vol. 91, No. 185, document number 2026-19704. The docket number is FDA-2026-N-9505, and the comment period closes on November 24, 2026. The draft is led by the Division of General Surgery Devices under CDRH.

The document states that it is a draft, not for implementation, and contains only nonbinding recommendations. Comments are due by November 24, 2026. In other words, the current discussion reflects FDA's preliminary thinking, not final requirements.

Devices Covered by the Draft Guidance

The draft defines RASD as a teleoperated, software-controlled system that integrates robotic technology and subcomponents to help a qualified surgeon accurately position and control one or more surgical instruments to perform open, minimally invasive, or endoluminal surgery. The system is used under the direct control or supervision of a qualified surgeon, uses a leader/follower control architecture, and may include a degree of automated functionality.

FDA describes three subcomponents:

• Surgeon console: displays the surgical field and controls the instruments and camera.
• Bedside/patient-side subcomponent (cart, column): includes a sterile/non-sterile interface and robotic arms used to manipulate the camera, instruments, accessories, and third-party devices within the body.
• Operating room personnel subcomponent (tower): includes an electrosurgical unit, suction/irrigation pumps, a secondary visual display, an insufflation unit, and an endoscopic light source.

Framework of Submission Recommendations

The draft organizes recommendations by type of premarket submission material. Topics include device description, comparison with marketed devices (510(k) only), accessories and compatible devices, RASD-specific nonclinical performance testing (system teleoperation, system control, kinematics and dynamics, visualization and display systems, other functional characteristics, reliability), software, cybersecurity, wireless technology, training, human factors, electrical safety and electromagnetic compatibility, optical radiation safety, sterility, reprocessing, shelf life and packaging, pyrogenicity, biocompatibility, in vivo evaluation, and labeling.

The in vivo evaluation section distinguishes nonclinical in vivo data from clinical data and has a separate section for postmarket clinical data. Appendix A provides an Umbrella and Covered Procedure Paradigm framework. Appendix B discusses 510(k) summaries. According to the glossary, a covered procedure and an umbrella procedure are in the same surgical specialty, with lower complexity and risk; an authorization may cite data from the umbrella procedure and may not require additional in vivo performance test data for the covered procedure.

Explicit Exclusions

The draft states that preoperative planning systems and stereotactic systems are not RASDs and are out of scope. Examples include orthopedic stereotactic instruments (product code OLO), neurological stereotactic devices (HAW), and ENT stereotactic instruments (PGW, 21 CFR 882.4560).

Also out of scope are RASDs used to assist the placement or use of interventional devices, such as interventional catheters; remotely teleoperated RASDs; and autonomous robots that independently perform important intraoperative tasks without relying on a qualified surgeon. The guidance notes that some nonclinical recommendations may still apply to these devices. In-scope 'endoluminal' use refers to use through existing lumens and does not include transvascular or intravascular multi-instrument positioning and control. For out-of-scope devices, FDA recommends communicating through the Q-Submission program.

Sources and Applicability

Source: U.S. Food and Drug Administration (FDA) draft guidance Robotically-Assisted Surgical Devices—Premarket Submissions, released September 25, 2026. Guidance page: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/robotically-assisted-surgical-devices-premarket-submissions. Full guidance PDF: https://www.fda.gov/media/194987/download. Federal Register notice of availability (Vol. 91, No. 185, 2026-19704, September 25, 2026): https://www.federalregister.gov/documents/2026/09/25/2026-19704/robotically-assisted-surgical-devices-premarket-submissions-draft-guidance-for-industry-and-food-and

Verification scope and access date: The FDA guidance page, full guidance PDF, and Federal Register notice page were accessed on September 29, 2026. The issuing office (CDRH), release date (September 25, 2026), docket number (FDA-2026-N-9505), comment deadline (November 24, 2026), scope and exclusions, glossary, and table of contents structure were checked.

Applicability note: This article interprets the public regulatory information above and does not constitute a conclusion or commitment for any specific product, company, or registration application. FDA guidance is recommendatory; this draft cannot be used for implementation, and the final version may change. The official original text prevails, and information may change with subsequent official updates.

AIMEILI Regulatory Interpretation

For manufacturers developing RASDs, the draft signals that FDA expects a structured, subsystem-based premarket package rather than isolated testing. The nonclinical expectations around teleoperation, system control, kinematics, visualization, reliability, software, cybersecurity, wireless, human factors, electrical safety, and EMC are likely to shape test plans, verification protocols, and submission summaries. Companies should map each requirement to the three subcomponents and to any accessories or compatible devices, because gaps in one area can delay a 510(k), De Novo, or PMA pathway.

The exclusions are equally important. Preoperative planning, stereotactic systems, interventional-device RASDs, remote teleoperation, and autonomous robots are outside the draft scope, but they are not necessarily outside FDA review. Sponsors of such devices should consider early Q-Submission meetings to confirm the applicable nonclinical and clinical evidence expectations. The Umbrella and Covered Procedure Paradigm in Appendix A may offer a data-leverage pathway for lower-risk covered procedures, but it requires careful justification that the procedures share the same surgical specialty and that the risk and complexity are lower.

For distributors, CROs, and regulatory affairs teams, the draft reinforces the need for traceable evidence linking device description, intended use, indications, user interface, training, reprocessing, and labeling. Labeling and training requirements may become a central review issue for systems that depend on surgeon console ergonomics, master-slave control, OR staff workflows, and compatibility with third-party devices.

Business Impact

• Earlier regulatory planning: RASD developers should align product architecture, risk management, and test strategy with the draft's subcomponent and nonclinical categories before finalizing design freeze or clinical study design.
• Higher evidence burden: Cybersecurity, wireless, software, human factors, EMC, and reliability data may need more integration, increasing internal resources and external testing costs.
• Opportunity for data leverage: The umbrella and covered procedure framework may reduce duplicate in vivo testing for certain lower-risk procedures if justified, potentially shortening timelines and lowering costs.
• Scope risk: Devices near the exclusion boundary, such as remote teleoperation, autonomy, or interventional-catheter RASDs, may face unclear expectations and should use pre-submission pathways to reduce review uncertainty.
• Global market access: Although this is U.S. draft guidance, its structure can inform EU MDR technical documentation, clinical evaluation, and cybersecurity and human-factors files, helping companies maintain one core regulatory narrative across markets.
• Stakeholder coordination: Regulatory affairs, R&D, quality, clinical, and commercial teams should track the comment period and prepare for potential changes in the final guidance before major submission commitments.