FHIR stores in 2026 innovate in specific areas. Understanding what actually ships in production shapes purchasing.
Innovation area 1: Bulk data at massive scale. Bulk Data IG $export at 100M+ resources with hourly incremental updates.
Innovation area 2: Streaming Subscription delivery. SubscriptionTopic-based delivery with reliable retry, dead-letter, back-pressure.
Innovation area 3: In-process terminology at scale. SNOMED CT, LOINC, RxNorm co-located with FHIR store.
Innovation area 4: Multi-tenant isolation. Single deployment serving multiple isolated tenants.
Innovation area 5: Federated cross-store queries. Multiple FHIR stores queried as one virtual store.
Vendor innovation (mid-2026)
| Store | Bulk at scale | Subscription | Terminology | Multi-tenant | Federated |
|---|---|---|---|---|---|
| Aidbox 2409 | Excellent | Native | In-process | Native | Add-on |
| Medplum 3.x | Excellent | Native | Basic | Add-on | External |
| HAPI JPA 7.x | Good with tuning | External | In-process | External | External |
| Microsoft FHIR | Native | Add-on | External | Azure | External |
| InterSystems IRIS | Enterprise | Enterprise | Enterprise | Enterprise | Enterprise |
Enterprise deployment considerations
1. Bulk data storage lifecycle. 2. Cross-tenant leakage prevention. 3. Terminology governance workflows. 4. Backup and DR procedures. 5. Observability at resource-type level.
Common FHIR store failures
1. Bulk data sync-only. 2. Subscription without retry. 3. External terminology latency. 4. Multi-tenant leakage. 5. Missing federated cross-store.
Investment tier
| Tier | Store options |
|---|---|
| Small deployment | HAPI open, Medplum |
| Moderate deployment | Aidbox, Medplum, HAPI + support |
| Enterprise deployment | Aidbox, InterSystems IRIS, Firely Suite |
| Cloud-native | Microsoft FHIR, Medplum Cloud |
FHIR store innovations focus on scale, reliability, and observability. Match store to your deployment tier and growth trajectory.