Benjamin Kowalski

The $expand operation is the FHIR terminology call you depend on without realizing it. Every dropdown that pulls a value set, every form rendering that needs an answer list, every dashboard that filters by code: all of it bottlenecks on $ex

ICD-10 to SNOMED CT mapping is one of the workflows that US hospitals run constantly without thinking about it: a diagnosis comes in as ICD-10-CM from claims, has to map to SNOMED CT for clinical decision support, and round-trips back to IC

A commercial terminology server is the right pick for US hospital networks that have outgrown the operational overhead of running open-source terminology in-house. The license cost is real, but so is the cost of a clinical informatics team

HAPI Terminology and Snowstorm are the two open-source terminology servers that come up most often in US hospital evaluations. They both expose FHIR terminology endpoints, both support SNOMED CT, and both are free in the licensing sense. Th

SNOMED CT is the deepest clinical terminology in widespread US use, and getting it right requires more than a generic terminology server. It needs proper handling of the international and US edition releases, support for the SNOMED CT expre

LOINC is the code system that ties US laboratory data together, and the terminology server that hosts it has to handle some specific challenges: large value sets for panel definitions, frequent code-version updates, and the kind of $expand