Release 2610 adds encryption for selected FHIR fields in Aidbox and tools for building patient matching models in MDMbox. Formbox carries confidentiality labels from forms into collected answers. Interbox 2.0 lets developers define integration pipelines as TypeScript steps, with further additions in versions 2.1 and 2.2.
Aidbox
Encryption for selected FHIR fields
Field-level encryption protects selected resource values at rest, such as patient names, birth dates, and identifiers. Aidbox decrypts these values when returning resources through read, search, and history operations.
Configure the fields to encrypt and select a key from the External Secrets vault. Aidbox also accepts values encrypted by an upstream system using the same key. An optional validation setting rejects values that Aidbox cannot decrypt.
ValueSets and ConceptMaps in SQL queries
SQLQuery and SQLView Libraries now support ValueSets and ConceptMaps as dependencies, making their contents available as tables in SQL. For example, a report could use a ValueSet to select a group of diagnoses or a ConceptMap to map codes between terminology systems, without listing the codes or mappings in the query itself. See terminology support in SQL on FHIR.
Bulk exports include offloaded files
Bulk exports now include binary data stored through base64Binary offload. For each resource type with offloaded data, $export produces a compressed archive alongside the NDJSON file, and exported resources reference the corresponding archive entries.
Application events in the audit stream
The new $aidbox-audit operation publishes an application’s own AuditEvents to the Aidbox audit topic. These events pass through the configured destinations and filters alongside events generated by Aidbox.
Streaming responses from apps
Aidbox now forwards responses from http-rpc Apps as they arrive, without buffering the entire response. CSV and NDJSON downloads begin before the service finishes generating the output, and server-sent events reach the client as they are emitted.
MDMbox uses this support for matching downloads and incremental Admin UI updates. Streaming requires Aidbox 2610.0 or later.
Formbox
Confidentiality labels stay with collected answers
Formbox now copies confidentiality labels from a Questionnaire to its QuestionnaireResponse and from individual questions to their answers. Labels that restrict access in the form renderer are preserved when the response is saved.
More detail in selection lists
Options, reference selectors, and terminology lookups now support multiple columns. Form authors configure the columns in the designer and calculate their values with FHIRPath. For example, a selection list could show an identifying code alongside a display name to help users distinguish similar options.
Prefill, extraction, and DTR updates
Formbox now warns users when an expression fails to prefill a field. Form authors also gain support for merge PATCH operations during data extraction, and deployments can specify which version of the DTR Implementation Guide to use.
MDMbox
Build and validate patient matching models
Teams now build, train, and validate patient matching models in the Admin UI using Model builder. They define matching fields with SQL on FHIR ViewDefinitions and inspect their values and statistics before configuring a model.
Automatic training produces a probabilistic model without labeled training pairs. Alternatively, teams can define deterministic matching rules in JavaScript.
Users review potential matches, inspect scores and explanations, and set thresholds for manual review and same-person decisions. They then save a versioned model for online $match, Bulk matching, or Continuous matching. Existing FHIR matching models remain supported.
Prometheus metrics and a Grafana dashboard
A dedicated Prometheus endpoint and Grafana dashboard report request rates, response codes, and latency, with breakdowns by route and status.
Interbox 2.0: Pipelines built from steps
Interbox, our healthcare integration engine, receives data from other systems, converts it into the format the destination expects, and delivers it. For example, a pipeline might transform incoming data into FHIR resources for Aidbox.
In version 2.0, you define the processing steps and their order in TypeScript instead of working within the fixed pipeline of earlier versions. Steps live in your own repository, so support for a new format does not require changes to the engine. Interbox includes Claude Code skills for developing these integrations.
A pipeline can pass its output to another pipeline for additional processing or delivery to a second destination. Interbox stores accepted messages, so failed messages can be retried using the current code.
The dashboard shows pipeline activity, live rates, and waiting or completed deliveries. A built-in AI assistant helps investigate failures.
Additions in versions 2.1 and 2.2
- File reading from SFTP, Amazon S3, Google Cloud Storage, and Azure Blob Storage.
- Support for custom data sources.
- OAuth database authentication on Databricks Lakebase Autoscaling, including when Interbox and Aidbox share a database.
- Per-pipeline retention settings for completed delivery records and, in delivery mode, stored delivery files. The default retention period is seven days.
Deployment and migration notes
Aidbox: check custom SMART patient compartments. Add {def} to the compartment’s Patient entry if you use a custom compartment. Without it, a patient-scoped app receives 404 when reading its own Patient record, an empty search result, and 403 on update.
Formbox: switch standalone deployments to the Aidbox image. The standalone Formbox image is no longer published. Formbox is included in aidboxone.
Interbox: migrate 1.x pipelines before upgrading. Existing 1.x pipelines must be migrated to the new step-based format before upgrading to 2.0. The upgrade guide includes a one-off script for moving HL7v2 message history from one 1.x channel to one 2.0 pipeline. Back up the data and plan downtime with all engines stopped during the migration.
Large deliveries to Aidbox now use parallel requests, which increases the load on the destination. Set INTERBOX_AIDBOX_CONCURRENCY=1 to disable parallel delivery; see the steps reference.
Read the full Aidbox and Formbox release notes, MDMbox release notes, and Interbox documentation.
