# PATIENT_NOT_FOUND

Canonical page: https://docs.ovok.com/errors/patient-not-found

**HTTP 404.** Problem type: [`https://docs.ovok.com/errors/patient-not-found`](https://docs.ovok.com/errors/patient-not-found).

## What this means [#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 [#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 [#retry-safely]

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

## If the problem persists [#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](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
