A new FHIR server performance report quietly went public this week and has not yet made the rounds the way bigger interoperability news usually does. Health Samurai put four FHIR servers on the same hardware, the same data, and the same…
Multi-vocabulary mapping is one of the heavier loads a terminology server has to carry. The team needs ICD-10 to SNOMED CT translations, LOINC to local lab codes, RxNorm to NDC, and a half-dozen other ConceptMaps running in production. A te
$expand is the operation that separates polished demos from production-ready terminology servers. Expanding a small intent-of-use ValueSet looks easy. Expanding a million-concept SNOMED CT ValueSet under burst load is where the FHIR termino
LOINC and SNOMED CT are two of the most common code systems healthcare developers touch, and they are also two of the easiest to use badly. A LOINC lookup API that returns the right LOINC for "potassium serum" looks trivial in a demo and tu
CDS Hooks raises the latency bar for any terminology tool sitting underneath it. A clinical decision support service has a budget measured in hundreds of milliseconds; if a single $expand or $validate-code blows that budget, the whole hook
SMART on FHIR apps tend to need terminology lookups during the most latency-sensitive parts of the workflow. The clinician opens the app, the app fetches the patient context, and three terminology calls happen in the first second. A FHIR te
Transactional FHIR writes break in subtle ways when the upstream system replays a message. The pipeline thinks the write is new. The FHIR server happily creates a second Patient or a duplicate Encounter. A clinician opens the chart and…
API-first healthcare apps treat the terminology layer the same way they treat the rest of the stack: a service with a clean REST surface, predictable latency, and no surprises in the auth model. That is a higher bar than many older terminol
A FHIR terminology service is the quietest load-bearing piece of a modern healthcare stack. It rarely appears in product demos and almost always shows up in the first production incident. Picking one well in 2026 saves a year of small surpr
Healthcare startups hit the cloud-native vs self-hosted question for their FHIR form engine earlier than they expect. The first form lands fine on whichever option the founder picked over coffee. The third form, the first audit, and the fir
