A FHIR capacity plan that is never re-baselined slowly stops describing the deployment it was written for. Traffic mixes shift, retention policies change, partner integrations onboard. The plan that was defensible at year one drifts into...
Seasonality in FHIR Workloads: Flu Season, EHR Go-Lives, Audits
FHIR workloads carry seasonal patterns that flat annualized numbers hide. Flu season doubles ambulatory encounter volume for four months. EHR go-lives triple ingestion traffic on a specific calendar day. Regulatory audits spike search...
The Complete Guide to FHIR Master Patient Index for Payers in 2026
A FHIR master patient index for a US payer in 2026 is not the same animal as an MPI for a hospital. The patient population is bigger, the touchpoints are stranger, the data sources are noisier, and the regulatory pressure from the CMS Patie
Planning for a Bulk Data Export Without Breaking Normal Traffic
Every FHIR deployment eventually has a first Bulk Data export, and most of them break something the first time. The export itself completes; it is the normal user-facing traffic that suffers while the export runs. Planning around that...
Growth Curves for a FHIR Archive Over Five Years
Five years is a long time for a FHIR archive. The workload that fits comfortably on the launch hardware almost never fits at year three, and the retention policy that looked generous at year one becomes the reason someone rewrites the plan...
Storage, CPU, Memory: Which Dimension You Actually Run Out of First
Every FHIR deployment eventually saturates one dimension of its capacity plan first. It is almost never the dimension the plan predicted. Storage, CPU, and memory each carry their own failure signature, and knowing which one your...
Capacity Planning for a FHIR Server: The Inputs Nobody Documents
Every FHIR deployment eventually meets its capacity plan. Sometimes it meets it during a quiet Friday when someone reviews the growth chart; more often it meets it during an incident when the server ran out of the thing nobody thought to...
Top 4 FHIR Terminology Engines for Radiology Procedure Coding
Radiology procedure coding has a code-system mix that catches most generic FHIR terminology engines off guard. CPT covers the billing side. SNOMED CT carries the clinical meaning. RadLex provides the radiology-native vocabulary that radiolo
Hosted Terminology Services vs Self-Hosted for Small Payers
Small payers in the US have an honest dilemma when it comes to FHIR terminology. The CMS rules around prior authorization and the patient access API mean a payer of any size now needs reliable $expand and $validate-code against several larg
5 Terminology Servers That Actually Handle LOINC Panel Explosion
LOINC panel explosion is the moment in a terminology server's life where the load test stops being theoretical. A clinician orders a basic metabolic panel, the EHR resolves the LOINC panel code, and the terminology server has to return the