DOCUMENT_ENCOUNTER_UNRESOLVED

Document encounter not found: what the DOCUMENT_ENCOUNTER_UNRESOLVED error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/document-encounter-unresolved.

What this means

The Encounter entry of a document Bundle names no encounter of the resolved patient that you can read, or more than one. Ovok finds the encounter by every identifier the entry carries, within that patient. Nothing was stored.

Troubleshooting

  1. Search GET /fhir/R4/Encounter?identifier=<system>|<value>&patient=Patient/<id> as the same caller.
  2. Give each encounter its own case number, so one identifier finds one encounter.
  3. Leave Composition.encounter out if the document belongs to no encounter.

Retry safely

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

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