_Incident · Regulatory action_

# Medtronic Hugo surgical robot earns FDA clearance for additional indication

Canonical ID: `1a9c293e-eb71-4276-b38e-8252fac2dbba`

- **Occurred:** 2026-07-01
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [Medtronic](/companies/medtronic.md) (id: `5ed6adff-c714-4880-bb1e-62af35017f4f`)

Medtronic's Hugo surgical robot earned FDA clearance, reported July 1, 2026. Expansion of Hugo system into additional surgical indications.

## Sources (1)

1. https://finance.yahoo.com/news/medtronic-hugo-surgical-robot-earns-102759168.html

## Status history

- **active** · 2026-07-03 · agent:depth

## Common questions

### What happened in Medtronic Hugo surgical robot earns FDA clearance for additional indication?

Medtronic's Hugo surgical robot earned FDA clearance, reported July 1, 2026. Expansion of Hugo system into additional surgical indications.

### When did this incident occur?

The incident is recorded as occurring on July 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

### Who was involved in Medtronic Hugo surgical robot earns FDA clearance for additional indication?

The incident is recorded as involving Medtronic on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to Medtronic Hugo surgical robot earns FDA clearance for additional indication?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

### What is the current status of Medtronic Hugo surgical robot earns FDA clearance for additional indication?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/1a9c293e-eb71-4276-b38e-8252fac2dbba · sources: /v1/incidents/1a9c293e-eb71-4276-b38e-8252fac2dbba/sources · responses: /v1/incidents/1a9c293e-eb71-4276-b38e-8252fac2dbba/responses · status: /v1/incidents/1a9c293e-eb71-4276-b38e-8252fac2dbba/status · canonical URL: /incidents/regulatory-action-2026-07-01-medtronic_