List a batch job's results
/fhir2omop/batch/{job_id}/resultsA lighter status page. Returns the same per-item status entries as
GET /fhir2omop/batch/{job_id}, but without the job record or counts,
and the entries carry result_size rather than any result content. Use
each entry's item_id to fetch that item's result from
GET /fhir2omop/batch/{job_id}/results/{item_id}.
Entries are listed in a stable order that is not upload order and is
the same across pages. Match each entry to your own records by its id
(your correlation label) or item_id (from the upload response),
never by position.
Path parameters
A page of per-item result statuses
Response fields
Server-assigned opaque item ID, used in result URLs.
The caller's correlation label, echoed back; omitted when none was supplied.
Number of processing attempts started so far. The service retries an item that was interrupted, or whose vocabulary lookups or concept inference were temporarily unavailable; any other mapping error fails the item without retry.
Size in bytes of the item's stored result. Present once the item has succeeded.
A job- or item-level failure. Never contains FHIR or patient content.
Short stable token to branch on. Item-level kinds: invalid_input
(POST /fhir2omop/create would reject the item with a 400; the
message is that response's message), processing_failed (the
item could not be mapped; the message says why), result_too_large
(the result exceeded 28 MiB), input_unavailable (the input could
not be read), and
retries_exhausted / attempts_exhausted (the item could not
complete after repeated interruptions or after vocabulary lookups
stayed unavailable; it may succeed if you upload it again in a new
job). Job-level kinds: timeout (the job did not
finish within 36 hours of creation).
Human-readable description of the failure.
When the item finished. Absent until then.
Cursor for the next page, when has_more is true.
Whether more results remain beyond this page.