Category: Terminology server

The cloud-versus-self-hosted question for a FHIR terminology server in 2026 looks different than it did three years ago. Cloud terminology services have matured to the point where most US healthcare deployments can credibly run on a managed

Real-time clinical autocomplete is the use case that pushes a terminology server hardest. The clinician types two characters, the UI fires a search, the dropdown has to render before the user notices the lag. Every operation in that path ma

Choosing between OntoServer and a Tx-Server style deployment is the kind of decision that gets made by mid-size US hospitals every year and quietly shapes terminology operations for the next five. Both are credible FHIR terminology servers.

RxNorm is the US medication terminology that most digital health stacks depend on for medication lookup, prescription entry, and downstream interaction checking. The release cadence is monthly, the model is denser than most code systems, an

The `$translate` operation is one of those FHIR features that everyone references and few teams stress-test until production exposes the gaps. ICD-10-CM workflows in US healthcare lean on it heavily: SNOMED CT problem lists need to map to I

Open-source code system tooling has matured to the point where a team can run a credible terminology layer without buying a commercial product. The trade-off is operational: you own the upgrades, the indexes, the loader scripts. For teams t

LOINC is the code system that most US lab workflows quietly depend on, and the one most terminology servers handle adequately rather than well. The release cycle is fast, the hierarchy is real but flat, and the answer lists that ride alongs

ValueSet expansion is the operation that quietly defines whether your terminology server is fit for production. Demos show a clean call to `$expand` against a tidy 200-concept value set and a response in 30 milliseconds. Production looks di

SNOMED CT is the code system that quietly decides whether your FHIR terminology server is going to be a good fit or a daily headache. Working with a small US Edition slice is fine on almost any tool. Running clinical problem lists, encounte