Choosing a terminology server involves a set of capability trade-offs. Seven features distinguish production-ready servers from checkbox-ready.
1. Full SNOMED CT US Edition support. Includes hierarchy navigation, cross-map integration, refset handling.
2. LOINC support with translation. LOINC parts, LOINC-to-SNOMED cross-map via `$translate`.
3. RxNorm support with weekly updates. RxNorm releases weekly; server must sync accordingly.
4. $expand performance at scale. Large ValueSets (10k+ concepts) expand in <2 seconds.
5. $validate-code inline latency. Sub-20ms per code validation.
6. $translate with ConceptMap. Full cross-terminology support (ICD-10 to SNOMED, RxNorm to NDC).
7. Bulk expansion for pipeline use. Batch mode for feeding downstream systems.
Vendor scorecard (mid-2026)
| Server | SNOMED | LOINC | RxNorm | Expand | Validate | Translate | Bulk |
|---|---|---|---|---|---|---|---|
| Ontoserver | Full | Full | Via UMLS | Fast | Fast | Full | Yes |
| HAPI terminology | Full | Full | Via UMLS | Medium | Fast | Full | Yes |
| Aidbox terminology | Full | Full | Via UMLS | Fast | Fast | Full | Yes |
| Cheap terminology alternatives | Basic | Basic | Basic | Slow | Slow | Basic | No |
Deployment considerations
1. UMLS license required for SNOMED CT US Edition and RxNorm. 2. Update cadence must be automated. 3. Server should be in-process or same subnet as FHIR server. 4. Redis or similar for expansion caching.
Cost profile
| Item | Annual cost |
|---|---|
| UMLS license | Free with registration |
| Ontoserver license | ~$80k (commercial) |
| HAPI open source | Dev/ops cost |
| Aidbox terminology | Bundled |
| Server compute | $10-30k (moderate) |
Terminology infrastructure is worth its own budget category. Cheaping out here creates data quality debt that compounds for years.