Robotic Surgery Devices: FDA and EU MDR Regulatory Pathway Guide
Regulatory strategy guide for surgical robots, covering FDA pathways, EU MDR expectations, autonomy levels, software controls, human factors, and clinical evidence.
The Surgical Robotics Regulatory Landscape in 2026
Surgical robotics has evolved from a niche technology to a mainstream surgical platform. Intuitive Surgical alone reported over 3.1 million da Vinci procedures globally in 2025, an 18% year-over-year increase (including 15% US growth and 23% international growth), with revenue of $10.1 billion. New entrants — Medtronic Hugo, Johnson & Johnson's Ottava, CMR Surgical Versius — are intensifying competition and regulatory activity.
Yet the regulatory framework for surgical robots remains complex. These systems combine mechanical engineering, software, electrical safety, human factors, and increasingly AI/ML capabilities, each with its own regulatory expectations. This guide provides a comprehensive regulatory strategy for surgical robot manufacturers navigating FDA and EU MDR pathways.
Autonomy Levels and Regulatory Impact
A 2024 systematic review in npj Digital Medicine identified 49 FDA-cleared surgical robots and classified them using a 5-level autonomy scale. Understanding these levels is critical because they affect regulatory pathway selection, clinical evidence requirements, and post-market obligations.
| Level | Name | Definition | FDA Examples | Regulatory Implications |
|---|---|---|---|---|
| 1 | Robot Assistance | Surgeon directly controls all movements | da Vinci, Hugo, Versius | 510(k) pathway typical; Class II |
| 2 | Task Autonomy | Robot autonomously performs specific subtasks | Mako (Stryker), ROSA (Zimmer Biomet) | 510(k) or De Novo; requires task-specific validation |
| 3 | Conditional Autonomy | Robot makes decisions with surgeon oversight | TSolution One (Think Surgical) | De Novo more likely; higher evidence burden |
| 4 | High Autonomy | Robot performs tasks independently with human supervision | No cleared examples | PMA likely; extensive clinical trials expected |
| 5 | Full Autonomy | Robot performs complete procedures independently | No cleared examples | PMA required; novel regulatory territory |
Key finding: 86% of FDA-cleared surgical robots operate at Level 1, while only 6% have reached Level 3. Two systems have been recognized by FDA as having ML-enabled capabilities, though more claim these in marketing materials.
FDA Classification and Regulatory Pathway
Device Classification
FDA currently regulates all surgical robots as Class II (moderate risk) devices. The primary classification framework:
| Element | Details |
|---|---|
| Regulation | 21 CFR 876.1500 — Endoscope and Accessories |
| Product Code | NAY — System, Surgical, Computer Controlled Instrument |
| Classification | Class II |
| Review Panel | General & Plastic Surgery (also Orthopedic, Cardiovascular depending on indications) |
Additional product codes may apply depending on the specific surgical application:
KNS: System, Stereotactic, Neurosurgical
HWC: Prosthesis, Hip, Semi-Constrained, Cemented
KGF: Cutter, Bone, Power (for orthopedic robots)
Pathway Selection
| Pathway | When to Use | Review Timeline | Key Requirements |
|---|---|---|---|
| 510(k) | Substantial equivalence to predicate | ~90 days FDA review | Predicate comparison, bench testing, software documentation |
| De Novo | Novel device, no appropriate predicate | ~150 days FDA review | Full safety and effectiveness evidence, risk analysis |
| PMA | Class III (if reclassified), or highest-risk autonomous functions | ~180–360 days | Pivotal clinical trial, full panel review |
Historical context: The da Vinci was originally classified as Class III and initiated its clearance via PMA. FDA later advised Intuitive to convert to 510(k), and it was cleared as Class II — establishing the precedent that all subsequent surgical robots have followed.
Five surgical robots entered the market via De Novo:
AquaBeam Robotic System (Procept BioRobotics)
Anovo Surgical System (Momentis Surgical)
MARS Surgical System (Levita Magnetics)
Iotasoft Insertion System (iotaMotion)
Galen ES (Galen Robotics)
Recent FDA Activity
| Date | Device | Clearance Type | Notes |
|---|---|---|---|
| December 2025 | da Vinci SP | 510(k) | Expanded indications (inguinal hernia, cholecystectomy, appendectomy) |
| January 2026 | da Vinci 5 | 510(k) | Cardiac procedures cleared with non-Force Feedback instruments |
| March 2026 | da Vinci Force Feedback Instruments | 510(k) K253986 | Force Feedback instrument clearance |
| 2025 | Medtronic Hugo | 510(k) | First FDA clearance for Hugo system |
Software and Control System Requirements
IEC 62304: Software Lifecycle
Surgical robots typically contain Safety Class C software (the highest classification) due to the potential for serious injury or death from software failures. IEC 62304 requirements include:
| Requirement | Details |
|---|---|
| Software Development Plan | Define lifecycle model, deliverables, and traceability |
| Software Requirements Analysis | Functional, interface, and safety requirements |
| Software Architecture Design | Module decomposition, interfaces, SOUP identification |
| Software Detailed Design | Unit-level design for Safety Class B and C modules |
| Software Implementation | Coding standards, code reviews |
| Software Verification | Unit testing, integration testing |
| Software Validation | System-level testing against requirements |
| Software Maintenance | Patch management, SBOM updates |
With the 2026 revision of IEC 62304 under development, manufacturers should monitor changes to software classification and risk management integration requirements.
IEC 60601 Series: Electrical Safety
| Standard | Application |
|---|---|
| IEC 60601-1 | General safety and essential performance |
| IEC 60601-1-2 | Electromagnetic compatibility (EMC) |
| IEC 60601-1-3 | Radiation protection (if applicable) |
| IEC 60601-1-6 | Usability |
| IEC 60601-1-8 | Alarm systems |
| IEC 60601-2-4 | Cardiac defibrillators (if integrated) |
| IEC 60601-2-46 | Operating tables (if integrated) |
For surgical robots with force feedback, IEC 60601-1 essential performance must include accuracy of force measurement and transmission, as errors could cause tissue damage.
IEC 62366-1: Usability Engineering
Surgical robots require comprehensive usability engineering because of:
Complex user interfaces (surgeon console, patient-side cart, vision cart)
Multiple user roles (surgeon, bedside assistant, circulating nurse)
High-stakes consequences of use errors
Training requirements
Usability activities should include:
Use specification and user profiles
Use scenario analysis
User interface evaluation (formative and summative)
Human factors validation testing with representative users
Cybersecurity
Connected surgical robots must comply with FDA cybersecurity requirements:
| Requirement | Implementation |
|---|---|
| Threat model | Identify attack surfaces (network, USB, Bluetooth, console) |
| SBOM | Software Bill of Materials per Section 524B |
| Security architecture | Encryption, authentication, authorization |
| Penetration testing | Pre-market and post-market |
| Vulnerability monitoring plan | Coordinated vulnerability disclosure program |
| Incident response | PSIRT with surgical-robot-specific scenarios |
In K253986 (da Vinci Force Feedback Instruments, March 2026), Intuitive's 510(k) summary explicitly lists "Cybersecurity verification and penetration testing" as part of the submission content.
Clinical Evidence Requirements
FDA Expectations by Pathway
| Pathway | Clinical Evidence |
|---|---|
| 510(k) | Substantial equivalence demonstration; may rely on bench testing and predicate comparison; clinical data not always required but increasingly expected |
| De Novo | Clinical data typically required; may include clinical investigation or real-world evidence |
| PMA | Pivotal clinical trial; statistically powered study with safety and effectiveness endpoints |
For 510(k) surgical robot submissions, clinical evidence typically includes:
| Evidence Type | When Required |
|---|---|
| Bench testing | Always — mechanical performance, accuracy, repeatability |
| Cadaveric studies | Often — for new indications or significant design changes |
| Animal studies | Sometimes — for novel surgical approaches |
| Clinical data | Increasingly — for expanded indications, new autonomy levels |
| Real-world evidence | Supporting — from post-market registries |
EU MDR Clinical Evidence
EU MDR Article 61 requires clinical evaluation proportional to the device classification and risk. For surgical robots (typically Class IIb or III):
| Requirement | Details |
|---|---|
| Clinical Evaluation Plan | Per MDCG 2020-6 (for implantables) or MDCG 2020-13 |
| Clinical data | Sufficient for demonstrating safety and performance |
| Equivalence | Must meet all three criteria per MDCG 2020-5 |
| Literature review | Systematic search and appraisal |
| Clinical investigation | May be required for Class III or if equivalence cannot be established |
| PMCF | Post-market clinical follow-up plan required |
EU MDR Classification
Surgical robots are typically classified as Class IIb under MDR Annex VIII rules:
| Rule | Application | Typical Classification |
|---|---|---|
| Rule 9 | Invasive devices for transient use (surgical instruments) | Class IIa |
| Rule 11 | Software for providing information used to make decisions with diagnosis or therapeutic action | Class IIb or III |
| Rule 15 | Devices incorporating nanomaterial | Case-by-case |
| Rule 16 | Devices specifically for use in the upper airway | Class IIb |
The system as a whole is typically classified at the highest classification of its individual components. A surgical robot with software that provides real-time surgical guidance could be Class IIb under Rule 11, while the mechanical instruments are Class IIa under Rule 9.
Notified Body Selection
Not all notified bodies have expertise in surgical robotics. When selecting a notified body:
Confirm experience with robotic or computer-controlled surgical devices
Verify they have qualified reviewers for IEC 62304, IEC 60601, and IEC 62366
Understand their clinical evidence expectations for surgical robots
Confirm capacity and timelines (EU notified body timelines remain a challenge)
Training and Human Factors
Surgeon Training Requirements
Both FDA and EU MDR recognize that surgical robot safety depends on proper training. Expectations include:
| Element | FDA | EU MDR |
|---|---|---|
| Training program | Required as part of labeling (IFU) | Required per Annex I Section 23.4(s) |
| Training content | Device operation, emergency procedures, troubleshooting | Comprehensive instructions including training |
| Credentialing | Recommended; left to hospital credentialing committees | Not specified by MDR |
| Simulation | Often included as part of training system | Addressed in IFU |
| Learning curve data | May be required for novel systems | Not specified |
Intuitive's Training Model as Reference
Intuitive Surgical has established the most comprehensive training ecosystem in surgical robotics:
Simulation-based training: Dry labs, virtual reality simulators
Proctoring: On-site proctoring for first cases
Online learning: Didactic modules, case studies
Certification pathways: Progressive credentialing
Ongoing education: Continuing education, advanced technique training
For new manufacturers, demonstrating a comparable training infrastructure is increasingly expected by both FDA and notified bodies.
Post-Market Surveillance
FDA Post-Market Requirements
| Requirement | Details |
|---|---|
| MDR reporting (21 CFR Part 803) | Deaths, serious injuries, certain malfunctions |
| Medical Device Reports analysis | Trend analysis, complaint handling |
| Post-market studies | May be required as condition of approval |
| Cybersecurity monitoring | Per Section 524B vulnerability monitoring plan |
| Design changes | 510(k) for significant changes; 30-day notice for PMA supplements |
EU MDR Post-Market Requirements
| Requirement | Details |
|---|---|
| PMS Plan | Per MDR Article 84 |
| PSUR | Periodic Safety Update Report per Article 86 |
| PMCF | Post-market clinical follow-up per Article 61(11) and Annex XIV Part B |
| Vigilance | Serious incident reporting per Article 87 |
| Trend reporting | Per Article 88 |
| EUDAMED registration | UDI/device registration per Article 29 |
Submission Checklist: Surgical Robot
| Section | Content | Status |
|---|---|---|
| Executive summary | Device description, indications, technology overview | ☐ |
| Predicate comparison | Substantial equivalence analysis (for 510(k)) | ☐ |
| Indications for use | Specific procedures, patient populations, anatomy | ☐ |
| Device description | Mechanical, electrical, software architecture | ☐ |
| Performance testing | Bench testing: accuracy, repeatability, force, torque | ☐ |
| Electrical safety | IEC 60601 series testing reports | ☐ |
| EMC testing | IEC 60601-1-2 testing report | ☐ |
| Software documentation | IEC 62304: all lifecycle artifacts, SOUP list | ☐ |
| Cybersecurity | Threat model, SBOM, penetration testing, vulnerability plan | ☐ |
| Usability / human factors | IEC 62366-1 file, summative evaluation | ☐ |
| Biocompatibility | ISO 10993 for patient-contacting components | ☐ |
| Mechanical safety | Crush/pinch analysis, emergency stop, fail-safe modes | ☐ |
| Reprocessing | ISO 17664 validation (for reusable instruments) | ☐ |
| Sterilization | Validation per ISO 17665 or applicable method | ☐ |
| Clinical evidence | Clinical data, literature review, or equivalence rationale | ☐ |
| Labeling / IFU | Complete instructions for use including training | ☐ |
| Risk management | ISO 14971 risk management file | ☐ |
| Clinical training program | Description of training infrastructure | ☐ |
Key Takeaways
All FDA-cleared surgical robots are Class II, primarily cleared through 510(k). The De Novo pathway is increasingly used for novel systems without predicates.
Autonomy level drives regulatory complexity — Level 1 systems follow standard 510(k); Level 3+ systems face higher evidence burdens and may require PMA.
Software is Safety Class C under IEC 62304 for most surgical robots, requiring the most rigorous lifecycle documentation.
Cybersecurity is now mandatory — connected surgical robots must have SBOMs, threat models, penetration testing, and vulnerability monitoring plans per Section 524B.
Clinical evidence expectations are rising — even 510(k) submissions for surgical robots increasingly include clinical data, especially for new indications.
Training infrastructure is a de facto regulatory requirement — manufacturers must demonstrate comprehensive surgeon training programs.
Sources
Levels of autonomy in FDA-cleared surgical robots: a systematic review, npj Digital Medicine (2024)
FDA 510(k) K253986 — da Vinci Force Feedback Instruments (March 2026)
FDA 510(k) K252675 — da Vinci SP Surgical System (December 2025)
Intuitive Surgical 2025 Annual Report — 3.1M procedures, $10.1B revenue
FDA Guidance: Cybersecurity in Medical Devices (February 2026)
IEC 62304:2006+AMD1:2015 — Medical device software — Software life cycle processes
IEC 60601-1:2005+AMD1:2012 — Medical electrical equipment — General requirements
IEC 62366-1:2015+AMD1:2020 — Application of usability engineering to medical devices
EU MDR 2017/745 — Annex VIII Classification Rules
MDDI Online — Intuitive's da Vinci 5 Secures FDA Cardiac Clearance (January 2026)
MassDevice — Intuitive wins expanded FDA indications for da Vinci SP (December 2025)