Benjamin Kowalski
Top 5 FHIR Servers for US Hospitals in 2026
Choosing a FHIR server for a US hospital in 2026 means picking a system that has to satisfy three audiences at once: your developers, your compliance team, and the EHR vendors you connect to. The top tier of products has shifted a little si
FHIR RESTful API: 5 Design Patterns for Production Endpoints
Exposing a FHIR RESTful API to external consumers isn't just "turn on endpoints." Five design patterns cover most production challenges around auth, rate limits, versioning, and versioning strategy. Pattern 1: Auth server separated from resource server. SMART on FHIR mandates OAuth 2.0 with a distinct authorization server. Keycloak, Auth0, or purpose-built work. The resource server […]
FHIR Terminology Browsers: 4 Tools for Code Exploration
Clinicians and analysts frequently need to look up SNOMED CT concepts, LOINC codes, and ValueSet expansions. Four terminology browser tools cover most 2026 use cases. **1. Ontoserver Snowstorm.** CSIRO's terminology server ships with a browser UI. Supports full SNOMED CT hierarchy, ValueSet expansion visualization, and FHIR `$expand` operations. Best for enterprise deployments. **2. SNOMED International […]
FHIR Server Selection Checklist: 8 Questions Before You Sign
Signing a FHIR server contract without asking eight specific questions is where teams lose 6 months to unpicked-up-on gaps. The list below is what production teams actually verify before commitment. **1. Does it pass Inferno for your target profiles?** Not marketing claims — verified conformance against US Core, Da Vinci PDex, or whichever IGs matter. […]