v0.28.0

!!! IMPORTANT !!!

This release contains database schema additions, so that the database can't be opened with older versions of Blaze. Downgrades are not possible.

Notes

A new index called PatientLastChange which will be automatically created and filled at the startup of Blaze. The index is used for the new CQL cache feature (#1051). Except for the caching, Blaze will work fully during index buildup. The index will be ready once the log message "Finished building PatientLastChange index of main node." appears.

After the index buildup, the CQL Cache can be activated by setting CQL_EXPR_CACHE_SIZE to a size of heap memory in MiB and restarting Blaze. A default of 128 MiB is recommended for instances with up to 100 k Patients and 1024 MiB for instances with 1 million patients.

New Features

• Cache Results of the Exists CQL Expression (#1051)

Bugfixes

• Fix JSON Rendering in UI (#1813)

The full changelog can be found here.

v0.28.0-rc.1

New Features

• Cache Results of the Exists CQL Expression (#1051)

Bugfixes

• Fix JSON Rendering in UI (#1813)

The full changelog can be found here.

v0.27.1

Enhancements

• Enable FHIR Search by _tag (#1801)

The full changelog can be found here.

v0.27.0

New Features

• Support Asynchronous Interaction Request Pattern (#1735)

Bugfixes

• Fix Delivering too Many Search Results in Some Cases (#1685)

Performance

• Lower Memory Consumption while Evaluating Stratifiers (#1723)

The full changelog can be found here.

v0.26.2

Operation

• Remove Need for FHIR Validator Local Package Cache (#1709)

The full changelog can be found here.

v0.26.1

Bugfixes

• Fix Rendering of Recursive FHIR Structures (#1552)
• Fix Rendering of Primitive Extensions (#1552)

The full changelog can be found here.

v0.26.0

Notes

This version of Blaze comes the first time with a frontend (Web UI). That frontend is required to use the new Job System which starts with a job for incremental update of indices. The deployment documentation including the new frontend container can be found here.

If the frontend is not needed, nothing will change for the deployment of the Blaze container.

This version will also create two new directories in the data volume called admin-index and admin-transaction. That directories will contain the administrative database storing the jobs of the job system. That database works identically to the main database but is separated in order to not interfere with the normal FHIR resources.

Enhancements

• Implement Incremental Update of Indices (#1442)

• Implement a Persistent Job Scheduler (#1486)

• Implement Date Ranges for Patient $everything (#1581)

Changes

Only relevant if the integrated frontend was already used.

• Separate Frontend from Blaze (#1569)

The full changelog can be found here.

v0.25.0

Notes

If you don't have referential integrity disabled, with v0.25.0, you will no longer be able to delete resources which are referenced by other resources.

Enhancements

• Maintain Referential Integrity while Deleting Resources (#543)

Bugfixes

• Fix XML Output for Resources with Control Chars (#1552)
• Make History Paging Stable (#1509)

The full changelog can be found here.

v0.24.1

Notes

Please update from v0.24.0 if you use variable length logical id's.

Bugfixes

• Fix Error While Reading Non-Existent Resource (#1475)

The full changelog can be found here.

v0.24.0

Notes

This release contains performance improvements for FHIR search and CQL. Counting the number of resources by using _summary=count in FHIR search with more than one search parameter uses all cores now and so is up to 10 times faster than before. CQL queries which test the existence of multiple condition codes are up to twice as fast.

Enhancements

• Implement Below Modifier for Canonical References (#1418)
• Add Admin UI (#1408)

Bugfixes

• Fix FHIR Search Combination of Sorting and Token Search (#1431)
• FHIR Search _id Queries Should Not Return Deleted Patients (#1415)

Performance

• Improve FHIR Search Count Performance (#1466)

The full changelog can be found here.