Benjamin Kowalski
Why Active Users Are Not the Same as Concurrent Requests
Sizing meetings almost always start with a user count. The vendor asks how many users the FHIR API will serve; the answer becomes the target for the capacity plan; the plan is sized against that number. The trap is that active users and...
Predicting Concurrency for a FHIR API Before You Have Real Users
You are asked to size a FHIR API before it has any real users. The traffic is hypothetical, the workflows are being redesigned as you plan, and the partner integrations exist only as slides. That is a hard exercise, and the shortcut most...
Top 4 FHIR Code Lookup Services for American Clinical Apps
Clinical apps in 2026 lean heavily on FHIR code lookup services, whether they call them by that name or not. A doctor types into an autocomplete and the app calls $lookup or $expand. A care plan validates an entered ICD-10 code against a va
Open-Source vs Commercial Terminology Servers for US Hospitals
Open-source or commercial is the second-most-important question a US hospital terminology team answers, right after which code systems to host. The license cost is the visible difference, but the actual decision rests on operational load, g
How to Wire OASIS-E Home Health PROMs to a FHIR US Core Encounter
OASIS-E is the CMS-mandated assessment that every Medicare-certified home health agency in the US completes at start of care, resumption, recertification, and discharge. In practice, the OASIS-E patient-reported items are still lived in a…
5 FHIR Terminology Servers That Actually Implement $expand Well
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
Best Terminology Server Tools for ICD-10 to SNOMED Mapping
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
Top 5 Commercial Terminology Servers for US Hospital Networks
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 vs Snowstorm: Which Fits a US Hospital
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
CMS-0057-F and Beyond: Why a Point Solution Becomes Legacy on January 2 2027
Every US payer engineering roadmap right now has January 1, 2027 circled in red. That is the CMS-0057-F Prior Authorization API enforcement date, and the natural instinct is to solve it with the shortest possible path. The trouble is what…