Remove a patient vital threshold

Method	Path
DELETE	/v1/slim/threshold/patient/:patientId/vitals/:code

Authentication · Access policies

Removes one resident's threshold for a single vital code in Signals, so that code no longer alerts for the resident.

Auth: Bearer token. The caller must be a practitioner, an admin, a super admin, or hold the "System Owner" access policy. The access policy must grant Goal:update (admins and super admins skip this check). Scope: The resident must be in the caller's project (from the token) or one of its sub-projects; otherwise 404.

Behaviour

• Answers 204 with no body once Signals confirms the removal. A 502 means Signals did not confirm; the call is safe to repeat.
• Codes the threshold routes own (for example SpO₂ and pulse rate) are refused with 400.
• code must be 1 to 64 characters from letters, digits, ., _ and -.

Example

curl -X DELETE 'https://api.sandbox.ovok.com/v1/slim/threshold/patient/3f1c2b7e-8d4a-4c1e-9b2f-6a7d5e4c3b21/vitals/59408-5' \
  -H "Authorization: Bearer ${OVOK_TOKEN}"

Successful response

204 — Signals confirmed the removal. No response body is returned.

Errors

Status	Meaning
400	code is not a vital code, or it is a code the /v1/slim/threshold and /v2/slim/threshold routes own.
401	Bearer token is missing, invalid or expired.
403	You are not a practitioner, admin or System Owner, or you lack Goal:update.
404	No patient with this id exists, or the patient is outside your project and its sub-projects or carries no project.
502	Signals did not confirm the removal. Nothing changed; send it again.