# DOCUMENT_PATIENT_UNRESOLVED

Canonical page: https://docs.ovok.com/errors/document-patient-unresolved

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/document-patient-unresolved`](https://docs.ovok.com/errors/document-patient-unresolved).

## What this means [#what-this-means]

The Patient entry of a `document` Bundle names no patient you can read, or more than one. Ovok finds the patient by every identifier the entry carries, so a patient matches only if it has all of them. Nothing was stored.

## Troubleshooting [#troubleshooting]

1. Search `GET /fhir/R4/Patient?identifier=<system>|<value>` for each identifier in the entry, as the same caller.
2. Send only identifiers the stored patient carries, such as the hospital's patient number and the KVNR.
3. If two patients carry the same identifiers, merge or correct them before sending the document.

## Retry safely [#retry-safely]

Safe to send again once the patient can be found; a document stored once is never stored twice.

## 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.
