First Release Candidate for 1.6.0
Pre-release
Pre-release
General remarks:
- This is a pre-release for DSF 1.6.0, do not use in production.
Features:
- The execution performance of FHIR rest update operations for
OrganizationandOrganizationAffiliationresource has been improved.
Bug Fixes:
- The DSF BPE missed
TaskandQuestionnaireResponseresources received by the DSF FHIR server during a connection outage between the DSF FHIR and DSF BPE servers. MissedTaskandQuestionnaireResponseare now always downloded after the connection is reestablished. See #233. - The OIDC provider URL could not be configured as a "no proxy" URL if a general forward proxy was configured for the DSF FHIR or DSF BPE servers. The responsible logic error in the code was fixed. See #232
QuestionnaireResponseand correspondingQuestionnaireresource could not be created together in atransactionBundle. The reference check for theQuestionnaireResponse.questionnairecanoncial reference was move to the correcttransactionBundleexecution phase. See #226- A wrong resource type in the
getLocalVersionlessAbsoluteUrlmethod of the plugin API classQuestionnaireResponseHelperImplwas fixed. See #224
Docker containers for this release can be access via the GitHub Docker registry - ghcr.io:
- bpe: ghcr.io/datasharingframework/bpe:1.6.0-RC1
- bpe_proxy: ghcr.io/datasharingframework/bpe_proxy:1.6.0-RC1
- fhir: ghcr.io/datasharingframework/fhir:1.6.0-RC1
- fhir_proxy: ghcr.io/datasharingframework/fhir_proxy:1.6.0-RC1
Issues closed:
- Upgrade Dependencies #236
- BPE Misses Task and QuestionnaireResponse Resources if Network Disconnects #233
- OIDC Provider Can’t Be Excluded From Configured Forwarding-Proxy #232
- Improve Performance of Organization and OrganizationAffiliation Updates #230
- A Questionnaire and corresponding QuestionnaireResponse resource cannot be posted to the FHIR server at the same time in a transaction Bundle #226
- QuestionnaireResponseHelperImpl Uses Wrong Resource Type in getLocalVersionlessAbsoluteUrl Method #224
- Start New Development Cycle #219
This release contains contributions from @hhund, @jaboehri, @schwzr and @wetret.