Aidbox is transitioning to the FHIR Schema engine. Existing zen and Entity/Attribute (EA) engines are deprecated and will be obsolete starting August 2025. July 2025 version will become LTS, supporting zen and Entity/Attributes for 2 years.
Migration Overview
The migration process involves six key steps:
Identify deprecated entities defined with zen and Entity/Attributes
Set up a parallel environment with FHIR Schema
Migrate profiles
Migrate custom resources
Migrate search parameters
Validate resources and resolve issues
Step 1: Identify Deprecated Capabilities
First, obtain a comprehensive list of all your zen and Entity/Attribute (EA) components that will need migration:
Step 2: Set Up Parallel Environment with FHIR Schema Engine
Launch a parallel Aidbox instance configured to use the FHIR Schema, connected to the same database and the same Zen configuration project (if you have one).
Below is an example of a docker-compose file with two Aidbox instances running on the same database: the first Aidbox (aidbox_zen) is configured with a zen configuration project and uses zen validation mode, while the second (aidbox_schema) is set up to use the FHIR Schema.
For detailed FHIR Schema engine configuration instructions, refer to the .
Since the FHIR Schema validation engine is more reliable and validates all the FHIR container cases, we need to validate existing data with FHIR Schema using .