PATIENT_READ_FAILED

Patient not readable: what the PATIENT_READ_FAILED error means and how to fix it.

HTTP 502. Problem type: https://docs.ovok.com/errors/patient-read-failed.

What this means

Ovok received an alert event from Signals for omni-channel alerts but could not read the alert's patient from the FHIR store. Nobody was told yet. You see this in the delivery log of the project's alerts subscriber, not in a user request.

Troubleshooting

  1. Wait for Signals to deliver the event again. It retries on its own.
  2. Check whether other FHIR reads for the project are failing too. If they are, the FHIR store is the cause, and the deliveries recover once it does.

Retry safely

Retrying is safe. Nothing was sent, so a repeated delivery tells each person once.

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