diff --git a/CHANGELOG.md b/CHANGELOG.md index d51348cac..445801488 100644 --- a/CHANGELOG.md +++ b/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 diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 382282704..031fd7f88 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -87,12 +87,13 @@ Documentation: [Environment Variables](docs/deployment/environment-variables.md) 1. Create a release branch named `release-v`, 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`. -5. Create a PR from the release branch to `main`. -6. Merge the PR. -7. Create and push a tag named `v`, 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`. +6. Create a PR from the release branch to `main`. +7. Merge the PR. +8. Create and push a tag named `v`, 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 diff --git a/Dockerfile b/Dockerfile index a72be4596..98fc1786e 100644 --- a/Dockerfile +++ b/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"] diff --git a/README.md b/README.md index 2b25fed4e..76ee251ce 100644 --- a/README.md +++ b/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]: [4]: -[5]: +[5]: [6]: [7]: [8]: diff --git a/build.clj b/build.clj index c23311d5f..72e33cfd6 100644 --- a/build.clj +++ b/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)) diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts index 7798d0c4c..68013d300 100644 --- a/docs/.vitepress/config.ts +++ b/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', diff --git a/docs/api.md b/docs/api.md index 6f0d14aa5..693cb544f 100644 --- a/docs/api.md +++ b/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) * [Patient $purge](api/operation/patient-purge.md) -* [CodeSystem $validate-code](api/operation/code-system-validate-code.md) -* [ValueSet $expand](api/operation/value-set-expand.md) -* [ValueSet $validate-code](api/operation/value-set-validate-code.md) +* [CodeSystem $validate-code](api/operation/code-system-validate-code.md) +* [ValueSet $expand](api/operation/value-set-expand.md) +* [ValueSet $validate-code](api/operation/value-set-validate-code.md) ## Asynchronous Requests diff --git a/docs/api/operation/code-system-validate-code.md b/docs/api/operation/code-system-validate-code.md index f5b628ae4..b7d5d7b7b 100644 --- a/docs/api/operation/code-system-validate-code.md +++ b/docs/api/operation/code-system-validate-code.md @@ -1,4 +1,4 @@ -# Operation \$validate-code on CodeSystem +# Operation \$validate-code on CodeSystem > [!CAUTION] > The operation \$validate-code on CodeSystem is currently **beta**. Only the parameters, described here, are implemented. diff --git a/docs/api/operation/value-set-expand.md b/docs/api/operation/value-set-expand.md index 76ab22897..3103983e1 100644 --- a/docs/api/operation/value-set-expand.md +++ b/docs/api/operation/value-set-expand.md @@ -1,4 +1,4 @@ -# Operation \$expand on ValueSet +# Operation \$expand on ValueSet > [!CAUTION] > The operation \$expand on ValueSet is currently **beta**. Only the parameters, described here, are implemented. diff --git a/docs/api/operation/value-set-validate-code.md b/docs/api/operation/value-set-validate-code.md index 21026241c..a35e1eb45 100644 --- a/docs/api/operation/value-set-validate-code.md +++ b/docs/api/operation/value-set-validate-code.md @@ -1,4 +1,4 @@ -# Operation \$validate-code on ValueSet +# Operation \$validate-code on ValueSet > [!CAUTION] > The operation \$validate-code on ValueSet is currently **beta**. Only the parameters, described here, are implemented. diff --git a/docs/deployment/standalone-backend.md b/docs/deployment/standalone-backend.md index fb0a1cd80..75b013f12 100644 --- a/docs/deployment/standalone-backend.md +++ b/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" } ``` diff --git a/docs/terminology-service.md b/docs/terminology-service.md index 57945bf94..1e8086a5a 100644 --- a/docs/terminology-service.md +++ b/docs/terminology-service.md @@ -1,4 +1,4 @@ -# Terminology Service +# Terminology Service > [!CAUTION] > The terminology service is currently **beta**. Only the basic functionality, described here, is implemented. diff --git a/docs/terminology-service/fhir.md b/docs/terminology-service/fhir.md index 27c536494..20a722fc8 100644 --- a/docs/terminology-service/fhir.md +++ b/docs/terminology-service/fhir.md @@ -1,4 +1,4 @@ -# FHIR Code Systems +# FHIR Code Systems Blaze supports all FHIR CodeSystem resources stored in Blaze with `content` of either `complete` or `fragment`. diff --git a/docs/terminology-service/loinc.md b/docs/terminology-service/loinc.md index 0c39cfc1b..363b84616 100644 --- a/docs/terminology-service/loinc.md +++ b/docs/terminology-service/loinc.md @@ -1,4 +1,4 @@ -# LOINC +# LOINC > [!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`. diff --git a/docs/terminology-service/snomed-ct.md b/docs/terminology-service/snomed-ct.md index 4998fcc03..eb548d9fc 100644 --- a/docs/terminology-service/snomed-ct.md +++ b/docs/terminology-service/snomed-ct.md @@ -1,4 +1,4 @@ -# SNOMED CT +# SNOMED CT > [!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. diff --git a/docs/terminology-service/ucum.md b/docs/terminology-service/ucum.md index 342fff0f9..6739df9df 100644 --- a/docs/terminology-service/ucum.md +++ b/docs/terminology-service/ucum.md @@ -1,4 +1,4 @@ -# UCUM +# UCUM Blaze supports the [UCUM](http://unitsofmeasure.org/) terminology.