_Incident · Regulatory action_

# ROBODOC Surgical System receives FDA 510(k) marketing clearance

Canonical ID: `65a3cd51-917a-482b-be0b-b49867c3483d`

- **Occurred:** 2026-06-30
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [ROBODOC](/companies/robodoc.md) (id: `5f99b08a-d0a3-4d07-ab99-24eba572366a`)

DigiMatch n ROBODOC Surgical System received FDA 510(k) marketing clearance for its orthopedic surgical robot platform.

## Sources (1)

1. https://www.biospace.com/digimatch-tm-n-robodoc-surgical-system-receives-u-s-fda-510-k-marketing-clearance

## Status history

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

## Common questions

### What happened in ROBODOC Surgical System receives FDA 510(k) marketing clearance?

DigiMatch n ROBODOC Surgical System received FDA 510(k) marketing clearance for its orthopedic surgical robot platform.

### When did this incident occur?

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

### Who was involved in ROBODOC Surgical System receives FDA 510(k) marketing clearance?

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

### Has anyone responded to ROBODOC Surgical System receives FDA 510(k) marketing clearance?

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 ROBODOC Surgical System receives FDA 510(k) marketing clearance?

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


_API: GET /v1/incidents/65a3cd51-917a-482b-be0b-b49867c3483d · sources: /v1/incidents/65a3cd51-917a-482b-be0b-b49867c3483d/sources · responses: /v1/incidents/65a3cd51-917a-482b-be0b-b49867c3483d/responses · status: /v1/incidents/65a3cd51-917a-482b-be0b-b49867c3483d/status · canonical URL: /incidents/regulatory-action-2026-06-30-robodoc_