Once teams move into production, the harder questions start appearing around the platform itself: how to export large datasets, how to respect consent rules, how to keep analytical workflows close to FHIR data, how to understand search performance, and how to give operators better visibility into the database.
For payer-facing products, the same pressure appears in a different form: member matching, provider access, payer-to-payer exchange, prior authorization workflows, SMART app registration, and portal administration all need to work together.
Aidbox, Formbox, and Payerbox 2605 focus on these parts of the workflow.
Bulk Export with More Control
Bulk export often looks simple from the outside: select the data, run $export, send the result to storage. In practice, it has to handle more than data selection. Teams have to account for consent, route files to the right storage, and decide what happens when a single patient record causes an error.
Aidbox 2605 adds consent-aware export, with consent strategy handled as part of the export flow. Bulk export can now support opt-in and opt-out filtering, UDAP B2B token configuration, and DaVinci export-type mapping.
The release also adds the onPatientError parameter. Teams can keep the default behavior and fail the export when a patient-level error occurs, or skip the affected patients and continue. Those errors still remain visible in the status response as OperationOutcome records under patient-errors.
Storage configuration also becomes more flexible. Through _aidbox.* parameters, a single export request can override the destination bucket and storage type, including S3, Azure, or GCS, without changing the global Aidbox configuration.
SQL on FHIR as an Operational Workflow
Aidbox 2605 adds async $viewdefinition-export, a first-party operation for exporting SQL on FHIR ViewDefinitions to object storage. The job runs as a managed background task and can be cancelled when needed.
The release also adds $sqlquery-run, which runs a SQLQuery Library synchronously over ViewDefinition tables. It resolves relatedArtifact dependencies into named tables, binds input parameters to :name placeholders, and streams the result in the requested format.
This gives teams two different patterns.
For larger export workflows, ViewDefinitions can be materialized to storage in the background. For direct query execution, SQLQuery Libraries can run against ViewDefinition-based tables and return results immediately.
Search Performance Based on Real Usage
FHIR search performance is difficult to tune from theory alone. Different teams search by different parameters. Some workloads depend heavily on dates. Others rely on identifiers, references, codes, or combinations of search parameters. Indexing everything is not always practical, and guessing often leads to poor trade-offs.
Aidbox 2605 adds two important updates here.
Date search parameters can now use a tstzmultirange index path. This is useful for large datasets, overlapping date ranges, and resources with repeating date values. It also fixes ANY-match semantics for those repeating date values.
Aidbox now collects per-parameter usage and index-health statistics. These appear in usage reports and in the new Search Params Stats view, together with index suggestions based on observed query patterns.
Instead of treating search tuning as a manual investigation, teams can now see which search parameters are used and where indexes may help.
A Database Page for Operators
Aidbox 2605 adds a new database-focused page in the Aidbox UI at /u/database.
It has three areas. Schema Explorer shows tables, size, row count, and index usage. It can also run VACUUM, ANALYZE, and REINDEX on a selected table.
Running Queries shows active database queries and gives operators a way to cancel or terminate them.
Search Params Stats gives a sortable and filterable view of search-parameter usage.
These are practical tools for teams running Aidbox in production. When query behavior changes, when tables grow, or when a search pattern becomes expensive, operators get more visibility directly from the Aidbox UI.
Databricks Delta as a Destination
AidboxTopicDestination now supports Databricks Delta tables.
This is not just an export to another storage destination. AidboxTopicDestination streams FHIR resource changes into a Databricks Delta table, with rows flattened by a SQL on FHIR ViewDefinition. As a result, analytics teams can work with column-based tables instead of nested FHIR JSON.
Validation, Authentication, and Mapping Updates
System-level validation is now available through POST /fhir/$validate, alongside resource-scoped validation routes.
Password management has been expanded. Signed-in users can change their own passwords after confirming the current one, and all sessions are signed out after a successful change. Administrators can issue single-use reset links with a 15-minute lifetime. Reset flows can also include a TOTP step for users with 2FA enabled.
The login page now supports the standard OAuth login_hint parameter, so the username field can be pre-filled. Sign-in, 2FA, sessions, and grants screens have also been refreshed with a consistent visual style.
For integration and ETL workflows, Mapping resources now support skipReferenceValidation. This opt-in flag helps when data is loaded in stages and some references are only partially available during execution.
Formbox Updates
Formbox also received a set of updates around form usability, security, uploads, and multilingual configuration.
Date validation messages in NHS forms are now clearer, especially around min and max validation feedback. Entry mode layout has been adjusted so required field indicators appear more consistently.
For multi-organization environments, organization selection has been improved.
Formbox also updates AccessPolicy handling for form sessions through a backward-compatible migration that aligns policy matching with SDC-issued session tokens.
Group item population has also been expanded with support for FHIR Query configuration and variables.
The release improves Azure Blob Storage integration for file attachment uploads and adds automatic loading of the default language from configuration for multilingual forms.
Payerbox Updates
Payerbox 2605 expands payer-facing workflows across Interop APIs, Prior Auth APIs, and the FHIR App Portal.
For Provider Access, the release adds $provider-member-match for asynchronous demographic matching with treatment attestation and opt-out consent checks. It also adds $davinci-data-export, an asynchronous FHIR Bulk Data export over a member Group, used in Provider Access and Payer-to-Payer workflows.
For Payer-to-Payer exchange, Payerbox adds $bulk-member-match, with mandatory per-member HRex consent opt-in and separate results for matched, non-matched, and consent-constrained members.
Prior Auth APIs also received several updates. CDS Hooks support now includes discovery and the order-sign, order-select, order-dispatch, and appointment-book hooks. CRD adds custom-response mode, DTR uses $questionnaire-package to deliver questionnaires and rules, and PAS adds Claim/$submit, Claim/$inquire, and $submit-attachment.
The FHIR App Portal also moves forward with SMART app registration, backend service registration for bulk data APIs, app discovery and launch, connected-app review, and multi-organization support with role-based access control.
More Control Around Production FHIR Workflows
Aidbox 2605 is focused on the operational parts of working with FHIR data at scale.
Bulk export gets more control around consent, storage destinations, and patient-level errors. SQL on FHIR adds new ways to export ViewDefinitions and run reusable SQLQuery Libraries. Search tuning becomes more visible through usage statistics, index-health data, and index suggestions. Database operators get a dedicated UI page for schema visibility, active queries, and search-parameter stats.
Formbox follows the same direction on the forms side, with updates around validation messages, required field indicators, organization selection, SDC security, file uploads, and multilingual configuration.
Payerbox extends the release into payer-facing workflows, including Provider Access, Payer-to-Payer exchange, Prior Auth APIs, SMART app registration, app access, and multi-organization support.
Read the full release notes for Aidbox, Formbox and Payerbox, or join the discussion on Zulip.
