Link Entities (Batch)
Links up to 5 free-text entities in a single call. All queries in a batch share the same ontology, version, top_k and metadata. The response contains one result block per query, in request order.
About this endpoint
POST /med-link/nel/link/batch links up to 5 free-text entities in a single
call. Every query in the batch shares the same ontology, version, top_k
and metadata.
The response results[] array contains one block per query, in request order —
each block has the same shape as a single
Link Entity response.
When to use it
- Coding several entities from the same document (e.g. all symptoms in a note).
- Reducing round-trips when the ontology and
metadataare identical.
metadata is shared across the whole batch, group queries that need
different hints — especially LOINC tests with different units or specimens —
into separate batches, or use the single
Link Entity endpoint.Limits
| Constraint | Value |
|---|---|
| Queries per request | 1–5 |
top_k | 1–10 (default 5) |
Authorizations
Bearer access token issued by the Eka authorization flow. See Authorization.
Body
List of free-text entities to link (1–5).
1 - 5 elementsOntology name applied to every query in the batch.
"snomed"
Ontology version applied to every query in the batch.
"20250401_extended"
Number of candidate results to return per query.
1 <= x <= 10Ontology-specific hints applied to every query in the batch.
Optional request ID. Generated automatically if omitted.
Response
One result block per query, in request order.
One NELResponse per query, in request order.

