Skip to content
  • Terminology server
  • Medical form builder
  • Ehr development
  • Emr development
WV United

WV United

EHR development notes on FHIR APIs, terminology server infrastructure, and clinical data interoperability.

WV United

WV United

EHR development notes on FHIR APIs, terminology server infrastructure, and clinical data interoperability.

  • Terminology server
  • Medical form builder
  • Ehr development
  • Emr development

Fhir Concurrency

Why Active Users Are Not the Same as Concurrent Requests
Posted on July 12, 2026July 13, 2026 by 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...

  • Fhir Concurrency
Predicting Concurrency for a FHIR API Before You Have Real Users
Posted on July 12, 2026July 13, 2026 by Benjamin Kowalski

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...

  • Fhir Concurrency

Capacity planning

Capacity planning

Approaching your RPS ceiling? the concurrency p99 predictor projects tail-latency using an M/M/1 approximation.

Recent Posts

  • Why Active Users Are Not the Same as Concurrent Requests
  • Predicting Concurrency for a FHIR API Before You Have Real Users
  • Top 4 FHIR Code Lookup Services for American Clinical Apps
  • Open-Source vs Commercial Terminology Servers for US Hospitals
  • How to Wire OASIS-E Home Health PROMs to a FHIR US Core Encounter

Categories

  • Ehr development
  • Emr development
  • Fhir Concurrency
  • Medical form builder
  • Terminology server
Copyright © 2025