FHIR, interoperability, and healthcare infrastructure blog

How Aidbox handles concurrent requests through its HTTP queue — three load scenarios, common failure modes, and how to tune worker capacity for stable performance.

Aidbox 2604 brings HIPAA Safe Harbor de-identification in SQL-on-FHIR, Databricks Lakebase token auth, a reworked SQL Console, and Formbox SMART on FHIR integration.

We're benchmarking popular open-source FHIR servers and Aidbox across CRUD, batch processing, and search workloads. Here's what we're testing and why.

Aidbox 2603 brings BigQuery streaming, Databricks Lakebase support, FHIR package dependency overrides, and Formbox improvements.

How Aidbox moved canonical resolution from runtime to configuration time — with pinning, tree-shaking, and a deterministic candidate selection algorithm.

Benchmarking Aidbox with 8 CPU cores: single instance vs multiple. 2×4 loses only 6% RPS but adds redundancy and better P99.

R6 moves immature resources out of core into incubator IGs. Here is how additional resources work, what changed, and what it means for implementers.

Bug report → full test report in 10 minutes. See how LLM agents reproduce bugs, generate tests, and validate Aidbox automatically.

We load-tested Aidbox pool settings. 80 configs show how web threads and DB pools affect throughput and latency.

Token Introspection is the critical bridge between Authentication and Authorization. When a client presents a token to access FHIR resources, the server must check if the token is valid.