# Detach a patient from a submitter

Canonical page: https://docs.ovok.com/api/signals-api---patients/detach-a-patient-from-a-submitter

`DELETE /v1/signals/api/submitter/{id}/patients/{patientId}`

The submitter may no longer post readings for the patient.

### Through ovok

- **Who can call it:** Manager apps, and users whose access policy grants the capabilities.
- **Capabilities, all required:** `signals_associations:update`. Project admins have every capability; client applications get no admin bypass.
- Your project's own submitter stays attached to its patients.
- If your access covers only some patients (anyone but project admins, manager or submitter apps, and anyone whose Patient access has no criteria), the patient must be one you can update. A patient is named by its Signals id, or by its Medplum Patient id where Signals takes a `refId`; ovok asks Signals which patient a Signals id is.