Skip to main content

Overview

Batch-resolve up to 100 FHIR Coding inputs in a single request. The batch never fails because one coding could not be resolved - failing items are reported inline in the results array with an error field, and the surrounding successful resolutions are still returned. Use this endpoint in ETL pipelines where you are iterating over a FHIR Bundle or exporting a FHIR dataset and need high-throughput code resolution.

Request Body

array
required
Array of FHIR coding inputs. Each item accepts the same fields as the single resolve endpoint: system, code, display, vocabulary_id. Maximum 100 items.
string
FHIR resource type applied to every item in the batch. Used for domain alignment checks and as the domain filter on semantic search fallbacks. Supported values match the single resolve endpoint.
boolean
default:"false"
Include Phoebe recommendations on every successful resolution.
integer
default:"5"
Maximum Phoebe recommendations per resolved concept (1–20).
boolean
default:"false"
Include a mapping_quality signal on every successful resolution.

Response Fields

boolean
Whether the batch operation completed.
object
Batch result.
array
One item per input coding, in request order.
object
Normalized coding input.
object | null
Resolved vocabulary, source/standard concepts, mapping method, target table, and alignment.
object | null
Per-item error when resolution failed.
object
Batch counts.
integer
Inputs processed.
integer
Inputs resolved.
integer
Inputs not resolved.
object
Request metadata.
string
Request correlation ID.
string
Response timestamp.
string
Vocabulary release used.

Response Shape

Each entry in results is either a successful resolution (same shape as POST /fhir/resolve) or an error entry:
The summary block reports totals to make monitoring easier: Optional enrichment failures do not increment failed. Each successful item has the same resolution.enrichment_status contract as single resolve, so quality validation or Phoebe recommendation degradation is reported per item while the core resolution and batch remain successful.

Errors

Per-item errors (e.g. concept_not_found, unknown_system, vocabulary_restricted) are returned inline in the results array and do not fail the batch.

See also