Release v0.32.0

Author: alexanderkiel

CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## v0.32.0
+
+### New Features
+
+* First Preview of Terminology Services ([#2377](https://github.com/samply/blaze/issues/2377))
+
+### Bugfixes
+
+* Fix Issues with Rebuilding the PatientLastChange Index ([#2372](https://github.com/samply/blaze/issues/2372))
+* Fix Negative Total Values in History Bundles Generated ([#2357](https://github.com/samply/blaze/issues/2357))
+
+### Documentation
+
+The generated documentation (https://samply.github.io/blaze/) was improved considerably and is now preferred over using direct Markdown files from the repository. 
+
+## UI
+
+* Add Logo and Lexend Font to UI ([#2323](https://github.com/samply/blaze/pull/2323))
+
 ## v0.31.0
 
 ### Enhancements

DEVELOPMENT.md

@@ -87,12 +87,13 @@ Documentation: [Environment Variables](docs/deployment/environment-variables.md)
 
 1. Create a release branch named `release-v<version>`, e.g., `release-v0.29.0`.
 2. Update all occurrences of the old version (e.g., `0.28.0`) to the new version (e.g., `0.29.0`).
-3. Update the `CHANGELOG.md` based on the milestone.
-4. Create a commit with the title `Release v<version>`.
-5. Create a PR from the release branch to `main`.
-6. Merge the PR.
-7. Create and push a tag named `v<version>`, e.g., `v0.13.1`, on `main` at the merge commit.
-8. Copy the release notes from the `CHANGELOG.md` into the GitHub release.
+3. Update `unreleased` badges in the documentation.
+4. Update the `CHANGELOG.md` based on the milestone.
+5. Create a commit with the title `Release v<version>`.
+6. Create a PR from the release branch to `main`.
+7. Merge the PR.
+8. Create and push a tag named `v<version>`, e.g., `v0.13.1`, on `main` at the merge commit.
+9. Copy the release notes from the `CHANGELOG.md` into the GitHub release.
 
 ## Code Conventions
 

Dockerfile

@@ -7,7 +7,7 @@ RUN apt-get update && apt-get upgrade -y && \
     rm -rf /var/lib/apt/lists/
 
 RUN mkdir -p /app/data && chown 1001:1001 /app/data
-COPY target/blaze-0.31.0-standalone.jar /app/
+COPY target/blaze-0.32.0-standalone.jar /app/
 
 WORKDIR /app
 USER 1001
@@ -20,4 +20,4 @@ ENV RESOURCE_DB_DIR="/app/data/resource"
 ENV ADMIN_INDEX_DB_DIR="/app/data/admin-index"
 ENV ADMIN_TRANSACTION_DB_DIR="/app/data/admin-transaction"
 
-CMD ["java", "-jar",  "blaze-0.31.0-standalone.jar"]
+CMD ["java", "-jar",  "blaze-0.32.0-standalone.jar"]

README.md

@@ -21,7 +21,7 @@ A demo installation can be found [here](https://blaze.life.uni-leipzig.de/fhir)
 
 Blaze is widely used in the [Medical Informatics Initiative](https://www.medizininformatik-initiative.de) in Germany and in [Biobanks](https://www.bbmri-eric.eu) across Europe. A 1.0 version is expected in the next months.
 
-Latest release: [v0.31.0][5]
+Latest release: [v0.32.0][5]
 
 ## Documentation
 
@@ -45,7 +45,7 @@ Unless required by applicable law or agreed to in writing, software distributed
 
 [3]: <https://cql.hl7.org/tests.html>
 [4]: <https://alexanderkiel.gitbook.io/blaze/deployment>
-[5]: <https://github.com/samply/blaze/releases/tag/v0.31.0>
+[5]: <https://github.com/samply/blaze/releases/tag/v0.32.0>
 [6]: <https://www.yourkit.com/java/profiler/>
 [7]: <https://www.yourkit.com/.net/profiler/>
 [8]: <https://www.yourkit.com/youmonitor/>

build.clj

@@ -5,7 +5,7 @@
    [java.time LocalDate]))
 
 (def lib 'samply/blaze)
-(def version "0.31.0")
+(def version "0.32.0")
 (def class-dir "target/classes")
 (def basis (b/create-basis {:project "deps.edn"}))
 (def uber-file (format "target/%s-%s-standalone.jar" (name lib) version))

docs/.vitepress/config.ts

@@ -30,7 +30,7 @@ export default defineConfig({
 		nav: [
 			{ text: 'Home', link: '/' },
 			{
-				text: 'v0.31.0',
+				text: 'v0.32.0',
 				items: [
 					{
 						text: 'Changelog',

docs/api.md

@@ -36,9 +36,9 @@ The following Operations are implemented:
 * [Measure $evaluate-measure](api/operation/measure-evaluate-measure.md)
 * [Patient $everything](api/operation/patient-everything.md) <Badge type="warning" text="v0.22.0"/>
 * [Patient $purge](api/operation/patient-purge.md) <Badge type="warning" text="v0.30.1"/>
-* [CodeSystem $validate-code](api/operation/code-system-validate-code.md) <Badge type="warning" text="unreleased"/>
-* [ValueSet $expand](api/operation/value-set-expand.md) <Badge type="warning" text="unreleased"/>
-* [ValueSet $validate-code](api/operation/value-set-validate-code.md) <Badge type="warning" text="unreleased"/>
+* [CodeSystem $validate-code](api/operation/code-system-validate-code.md) <Badge type="warning" text="v0.32.0"/>
+* [ValueSet $expand](api/operation/value-set-expand.md) <Badge type="warning" text="v0.32.0"/>
+* [ValueSet $validate-code](api/operation/value-set-validate-code.md) <Badge type="warning" text="v0.32.0"/>
 
 ## Asynchronous Requests
 

docs/api/operation/code-system-validate-code.md

@@ -1,4 +1,4 @@
-# Operation \$validate-code on CodeSystem <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="unreleased"/>
+# Operation \$validate-code on CodeSystem <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!CAUTION]
 > The operation \$validate-code on CodeSystem is currently **beta**. Only the parameters, described here, are implemented.

docs/api/operation/value-set-expand.md

@@ -1,4 +1,4 @@
-# Operation \$expand on ValueSet <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="unreleased"/>
+# Operation \$expand on ValueSet <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!CAUTION]
 > The operation \$expand on ValueSet is currently **beta**. Only the parameters, described here, are implemented.

docs/api/operation/value-set-validate-code.md

@@ -1,4 +1,4 @@
-# Operation \$validate-code on ValueSet <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="unreleased"/>
+# Operation \$validate-code on ValueSet <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!CAUTION]
 > The operation \$validate-code on ValueSet is currently **beta**. Only the parameters, described here, are implemented.

docs/deployment/standalone-backend.md

@@ -27,7 +27,7 @@ Blaze should log something like this:
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:67] - JVM version: 17.0.7
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:68] - Maximum available memory: 1738 MiB
 2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:69] - Number of available processors: 2
-2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:70] - Successfully started 🔥 Blaze version 0.31.0 in 9.0 seconds
+2023-06-09T08:30:30.126Z b45689460ff3 main INFO [blaze.core:70] - Successfully started 🔥 Blaze version 0.32.0 in 9.0 seconds
 ```
 
 In order to test connectivity, query the health endpoint:
@@ -47,7 +47,7 @@ that should return:
 ```json
 {
   "name": "Blaze",
-  "version": "0.31.0"
+  "version": "0.32.0"
 }
 ```
 

docs/terminology-service.md

@@ -1,4 +1,4 @@
-# Terminology Service <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="unreleased"/>
+# Terminology Service <Badge type="info" text="Feature: TERMINOLOGY_SERVICE"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!CAUTION]
 > The terminology service is currently **beta**. Only the basic functionality, described here, is implemented.

docs/terminology-service/fhir.md

@@ -1,4 +1,4 @@
-# FHIR Code Systems <Badge type="warning" text="unreleased"/>
+# FHIR Code Systems <Badge type="warning" text="v0.32.0"/>
 
 Blaze supports all FHIR CodeSystem resources stored in Blaze with `content` of either `complete` or `fragment`.
 

docs/terminology-service/loinc.md

@@ -1,4 +1,4 @@
-# LOINC <Badge type="info" text="Feature: TERMINOLOGY_LOINC"/> <Badge type="warning" text="unreleased"/>
+# LOINC <Badge type="info" text="Feature: TERMINOLOGY_LOINC"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!NOTE]
 > LOINC data is build into the Blaze image. Because LOINC support needs additional memory, it has to be enabled by setting the environment variable `ENABLE_TERMINOLOGY_LOINC` to `true`.

docs/terminology-service/snomed-ct.md

@@ -1,4 +1,4 @@
-# SNOMED CT <Badge type="info" text="Feature: TERMINOLOGY_SNOMED_CT"/> <Badge type="warning" text="unreleased"/>
+# SNOMED CT <Badge type="info" text="Feature: TERMINOLOGY_SNOMED_CT"/> <Badge type="warning" text="v0.32.0"/>
 
 > [!NOTE]
 > Because SNOMED CT has to be licensed, Blaze doesn't contain the SNOMED CT code system by default. However, by setting the environment variable `ENABLE_TERMINOLOGY_SNOMED_CT` to `true` and `SNOMED_CT_RELEASE_PATH` to a path of an official SNOMED CT release, Blaze will be able to offer terminology services on SNOMED CT. The release files are read into memory on each start of Blaze. So the release path has to be always available.

docs/terminology-service/ucum.md

@@ -1,4 +1,4 @@
-# UCUM <Badge type="warning" text="unreleased"/>
+# UCUM <Badge type="warning" text="v0.32.0"/>
 
 Blaze supports the [UCUM](http://unitsofmeasure.org/) terminology.