v1.6.2

Bugfixes

• Fix SNOMED CT CodeSystem Generation (#3456)
• Resolve Versions in Terminology Service (#3470)

The full changelog can be found here.

v1.6.1

Maintenance

• Update SNOMED CT Release Versions (#3435)

The full changelog can be found here.

v1.6.0

Enhancements

• Support Multiple Codings in Terminology Operations (#3347)

Bugfixes

• Fix Incomplete CQL Operator Normalization (#3386)

The full changelog can be found here.

v1.5.1

Bugfixes

• Fix FHIR _lastUpdated Inequality Search False Positives (#3367)
• Fix Missing FHIR Types in OperationOutcome (#3365)
• Fix CQL Operator InCodeSystem with external TS (#3349)
• Fix Sorting by _lastUpdated (#904)

The full changelog can be found here.

v1.5.0

Notes

The sizing of the resource cache is changed from count-based to size-based. The env var DB_RESOURCE_CACHE_SIZE is replaced by the env var DB_RESOURCE_CACHE_SIZE_RATIO. It's default is 0.25 so that 25 % of the Java Heap memory is used for the resource cache. That default should be safe for most deployments. It can be increased but not over 0.8 or 80 %. Please only increase the ratio if Monitoring is available.

Health checks are now officially supported via wget. In case you use curl for health checks, please replace it with wget. The curl command will be removed from the images in release v1.6.

Enhancements

• Switch Resource Cache Sizing from Count to Memory-Based (#3253)
• Implement $cql Operation (#3230)
• Implement CQL Operator InCodeSystem (#3157)
• Implement Basic VCL Support (#3275)
• Offer Health Checks (#3338)

Bugfixes

• Disable CompartmentResourceType Index Usage (#3294)

The full changelog can be found here.

v1.4.2

The security fix is relevant for the frontend. Please update.

Security

• Fix CVE-2025-15467: Out-of-bounds Write

v1.4.1

Security

• Fix CVE-2025-64756: glob Command Injection (#3212)

The full changelog can be found here.

v1.4.0

Notes

Review the new DB_SCALE_FACTOR configuration option. If your Blaze server stores more than 50,000 patients or 50 million resources, increase this factor following the Production Configuration Guide. Increasing the scale factor from 1 to 4 yielded approximately 1.5× faster transactions in our measurements. Additionally, this reduces the number of database files, which helps avoid ulimit issues.

Enhancements

• Introduce Scale Factor Config for Large Databases (#2434)
• Enable RocksDB WAL Sync (#3204)

Documentation

• Rename Tuning Guide (#3199)

The full changelog can be found here.

v1.3.1

Bugfixes

• Problem with :iterate and _revinclude in search parameters (#3143)
• Fix Startup Failure on BASE_URL with Trailing Slash (#3150)
• Fix Resolution of Overloaded CQL Functions (#3170)

The full changelog can be found here.

v1.3.0

Enhancements

• Implement ValueSet References (#110)
• Implement CQL Instance Expression for FHIR Types (#3126)
• Fail on Unsupported FHIR Search Modifier (#2951)

Performance

• Optimize Chained Queries (#3131)

The full changelog can be found here.