PATIENT_NOT_FOUND

Signals patient not found: what the PATIENT_NOT_FOUND error means and how to fix it.

HTTP 404. Problem type: https://docs.ovok.com/errors/patient-not-found.

What this means

Signals has no patient with that ID in the tenant that you may read. The patient does not exist, was deleted or moved to another tenant, or is not in the project you sent. A client that may not read the patient's record gets the same answer. Nothing changed.

Troubleshooting

  1. Check which identifier the route takes: Signals' patient ID or your own refId. Look up Signals IDs from refId values with the patient IDs list.
  2. Check project. It must match the patient's project.
  3. Check that the patient is enrolled in Signals. A resident Ovok has not enrolled yet has no Signals patient.

Retry safely

An unchanged request returns the same error. Nothing changed, so a corrected request is safe to send.

If the problem persists

Share the HTTP status, problem type, request path, response timestamp and traceId with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The Error responses guide explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page