Tobias Krainer
A FHIR Vendor Just Forked a Rival's Benchmark: Here Is Why That Matters
For US health systems that have spent years asking FHIR vendors for trustworthy performance numbers, something small but real just happened. Health Samurai released an open-source FHIR server performance benchmark on June 29, 2026,…
Self-Hosted vs Managed FHIR Servers: Which Wins for US Hospitals
Self-hosted or managed is the second-most-important question a US hospital IT team has to answer when picking a FHIR server, right after which vendor they shortlist. The choice changes operational burden, cost structure, vendor lock-in post
6 FHIR Servers That Actually Handle US Core Profiles Right
US Core profile compliance is the kind of thing that a FHIR server vendor will check on a marketing slide, then quietly under-implement in production. American hospital teams discover the gap the first time they try to validate a real-world
A 2026 Buyer's Guide to FHIR Servers for US Health Systems
A FHIR server is the part of your stack that decides whether US Core data flows cleanly between an EHR, an analytics tool, and a patient app, or whether half your interfaces fall back to flat-file exports. The vendor pitches you hear in 202
EHR-to-FHIR Integration: 4 Real-World Migration Paths
Getting from a legacy EHR to a FHIR-first integration model rarely happens in one release cycle. Four migration paths cover most 2026 deployments; picking wrong forces re-work. Path 1: Sidecar FHIR facade. Keep the legacy EHR intact, run a FHIR facade in front that translates FHIR REST calls to the EHR's proprietary API. HAPI FHIR's […]
FHIR `$lookup`: Terminology Operation Patterns That Work
The FHIR `$lookup` operation returns metadata about a coded value — display name, definition, properties, designations. Four patterns cover most production use cases. Pattern 1: Display name resolution on read. When a client reads a Coding element (e.g., Observation.code), the code is present but display might be stale or missing. Client calls $lookup to get […]