Operations
Three operations are available. Each requires a valid API key (see Authentication), and each returns the upstream FHIR resource as-is. See the API Reference for full parameters.GET /v1/terminology/$lookup(FHIRCodeSystem/$lookup): look up a code and get its display and properties.GET /v1/terminology/$expand(FHIRValueSet/$expand): expand a value set to its member codes, with an optional text filter and paging.GET /v1/terminology/$validate-code(FHIRValueSet/$validate-code): check whether a code is a member of a value set.
GET /v1/terminology/metadata endpoint returns the FHIR CapabilityStatement that declares
these operations.
Examples
Look up Hemoglobin A1c (4548-4):
4548-4 belongs to it:
url parameter is a value set canonical. It defaults to the implicit all-LOINC value set
(http://loinc.org/vs). Pass a LOINC Group (http://loinc.org/vs/{LG-code}) or answer list
(http://loinc.org/vs/{LL-code}) to scope to a specific set.
Responses and errors
Responses are passed through from the upstream terminology server verbatim, as standard FHIR:$lookupand$validate-codereturn a FHIRParametersresource.$expandreturns a FHIRValueSetwith itsexpansion.
400: invalid query parameters, for example a missingcode.401: missing or invalid API key.502: the upstream terminology server was unavailable or returned an error. Its FHIROperationOutcomeis included asoutcome.
200 with "result": false in the
Parameters, not an error.
Code systems
The service proxies LOINC today (http://loinc.org), backed by LOINC’s official FHIR
terminology server. Support for additional code systems, such as RxNorm, SNOMED CT, CVX, and
HCPCS, is planned.
For your first call, start with the Quickstart.