SEARCH_REFUSED
Search refused: what the SEARCH_REFUSED error means and how to fix it.
HTTP 400. Problem type: https://docs.ovok.com/errors/search-refused.
What this means
The FHIR store refused one of the searches that Observation/$lastn runs. $lastn passes every parameter it does not own to each search, so one parameter the store does not know, or one value it cannot read, refuses the whole request. status is the store's own: usually 400, but 403 or 404 when you cannot read the patient.
Troubleshooting
- Read
detail. It quotes the store's reason, such as an unknown search parameter or a value in the wrong format. - Check the extra parameters you send. Remove any that Observation does not define, and fix the values. Dates, tokens such as
system|code, and quantity prefixes must follow the FHIR search rules. - Check the patient when
statusis 403 or 404. The patient may not exist, or may be outside your project or access. Use a patient ID from your project, from an account that can read it.
Retry safely
Fix the search and send it again. The same search is refused again. $lastn only reads, so nothing changed.
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