/v1/search
Discovery with evidence
Search returns bounded, ranked concept candidates and identifies how a term matched. It supports a clinician or application finding a concept; it does not make an autonomous coding decision.
Loading...
Loading...
ReasonHealth Terminology API packages a read-only API, finalized local terminology store, and matching retrieval model into one immutable image your team operates in its own environment.
Terminology content
Versioned local store
Retrieval
Matching local search model
API surface
Search and FHIR expansion
No runtime database, sync service, package loader, or network content dependency.
The installed knowledge layer
Each release brings the terminology systems, API behavior, and retrieval model together at a known version boundary. Your application can use that boundary for discovery and governed membership without building a runtime data pipeline around it.
Two deliberate operations
/v1/search
Search returns bounded, ranked concept candidates and identifies how a term matched. It supports a clinician or application finding a concept; it does not make an autonomous coding decision.
FHIR R4 ValueSet/$expand
Submit an explicit FHIR ValueSet and receive deterministic membership evaluated against the installed terminology release. Discovery never substitutes for a clinical definition.
Subscription access
A subscription provides license-gated delivery of one immutable OCI archive per release. Your team verifies the artifact, deploys the image digest, and retains the prior accepted digest for controlled rollback.
Lite
A redistributable, incomplete fixture image for integration and evaluation. It is not a complete production corpus.
Full
A qualified protected-content image for entitled customers with the applicable upstream terminology rights.
Ready for your environment
Talk with our team about your terminology systems, deployment boundary, and the workflows that need an auditable source of clinical meaning.