In 2025, Aidbox development was guided by three clear pillars: performance, FHIR conformance, and developer experience. Rather than chasing isolated features, the focus was on removing architectural bottlenecks, aligning more deeply with the FHIR ecosystem, and making core platform capabilities more transparent and inspectable.
This overview covers the most important architectural and platform changes in Aidbox in 2025.
Performance
Database & Infrastructure
- Read-only replica support: Aidbox can now delegate read-only workloads to a PostgreSQL read-only replica, enabling better resource utilization and horizontal scaling for analytics and reporting.
- CRUD optimization: Core CRUD operations now run 30% faster thanks to internal optimizations rolled out in December.
- Deprecated AidboxDB: We completed our transition to the official PostgreSQL distribution, simplifying deployment and maintenance.
Analytics & Real-Time Data
- ClickHouse integration: New AidboxTopicDestination for ClickHouse enables real-time analytics by exporting ViewDefinitions directly to ClickHouse.
- SQL-on-FHIR improvements: Implemented the $run operation for direct querying through ViewDefinitions, plus explicit materialization control for better resource management.
Subscriptions & Event Streaming
- AMQP support: Topic-based subscriptions now support AMQP message brokers as a destination channel.
- Change tracking functions: Introduced %previous and %current functions in AidboxSubscriptionTopic for precise version-to-version change tracking.
- FHIR-native subscriptions: Released full support for FHIR-native topic-based subscriptions in December.
- External audit repository: AuditEvents can now stream to an external FHIR AuditRecord Repository.
FHIR Conformance
FHIR Schema Engine
- New validation engine: We transitioned to the FHIR Schema engine, replacing the legacy Zen-based approach. This centralizes schema and validation logic using standard FHIR IGs and profiles.
- Migration tool: Published the FHIR Schema migration tool to help teams transition existing configurations.
FHIR Version Support
- FHIR R6 preview: Added support for FHIR 6.0.0-ballot3 and published a tutorial on running Aidbox with R6.
- DomainResource migration: Migrated system resources to the FHIR DomainResource model with comprehensive reference documentation.
Implementation Guide Management
- NPM registry integration: Added integration with external NPM package registries for IG loading.
- Dependency optimization: Introduced pinning and tree shaking for optimizing IG dependency resolution.
- FAR package API: Released the new FAR package management API for managing published IG artifacts.
- Init bundle tutorial: Published a guide on loading FHIR IGs via Init Bundle.
Terminology
- New terminology engine: Integrated a new Terminology engine supporting local operations while delegating to external Terminology Servers for external code systems.
- $translate operation: Added support for the $translate operation on ConceptMap resources.
Access Control & Certification
- SMART-on-FHIR v2: Added support for SMART-on-FHIR v2 scopes with search parameters.
- Hierarchical access control: Implemented Organization-based hierarchical access control in Topic-based Subscriptions.
- Inferno test guide: Published a comprehensive tutorial on passing Inferno tests for US Core 6.1.0/USCDI v3 and SMART App Launch 2.0.0.
Developer Experience
Configuration & API
- Settings surface: Introduced first-class Settings for instance configuration with a comprehensive reference surface.
- FHIRPath PATCH: Implemented FHIRPath PATCH for more expressive resource updates.
- FHIR factory API: Added support for the FHIR Factory API in the FHIRPath engine.
Code Generation & Frameworks
- Open-source code generator: Released an open-source code generator based on FHIR type schemas.
- Atomic EHR framework: Launched Atomic EHR, a TypeScript framework for building FHIR applications.
UI & Integrations
- New UI tech stack: Started migrating AidboxUI from ClojureScript to React and TypeScript, and began open-sourcing it to serve as an example of how to build production-grade applications on top of the Aidbox FHIR Server.
- MCP server module: Released the Aidbox MCP Server module, exposing Aidbox operations and metadata for external MCP clients and agents.
See Aidbox in Action
Interested in how Aidbox’s future-proof FHIR platform can accelerate your healthcare projects? We invite you to schedule a demo with our team and explore how Aidbox can support your next product milestone.




