_Incident · Regulatory action_

# THINK Surgical receives FDA 510(k) clearance for TMINI 1.1

Canonical ID: `568e84d3-d723-4e72-be68-025e42d681a9`

- **Occurred:** 2026-06-15
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [THINK Surgical](/companies/think-surgical.md) (id: `fcbc42cb-7267-41d7-ab02-10d4838d2a93`)

THINK Surgical received second FDA 510(k) clearance for TMINI 1.1 Miniature Robotic System in less than 15 months.

## Sources (1)

1. https://thinksurgical.com/think-surgical-receives-fda-510k-clearance-for-tmini-miniature-robotic-system-tmini-1-1/

## Status history

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

## Common questions

### What happened in THINK Surgical receives FDA 510(k) clearance for TMINI 1.1?

THINK Surgical received second FDA 510(k) clearance for TMINI 1.1 Miniature Robotic System in less than 15 months.

### When did this incident occur?

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

### Who was involved in THINK Surgical receives FDA 510(k) clearance for TMINI 1.1?

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

### Has anyone responded to THINK Surgical receives FDA 510(k) clearance for TMINI 1.1?

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 THINK Surgical receives FDA 510(k) clearance for TMINI 1.1?

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


_API: GET /v1/incidents/568e84d3-d723-4e72-be68-025e42d681a9 · sources: /v1/incidents/568e84d3-d723-4e72-be68-025e42d681a9/sources · responses: /v1/incidents/568e84d3-d723-4e72-be68-025e42d681a9/responses · status: /v1/incidents/568e84d3-d723-4e72-be68-025e42d681a9/status · canonical URL: /incidents/regulatory-action-2026-06-15-think-surgical_