Release of the MII data-transfer process plugin used to transfer data-sets of an approved data usage project from a DIC to a DMS.
The documentation of the process including the description, the deployment and configuration guides as well as instructions on how to start a process instance can be found in the wiki. For a pre-built jar file, see assets: mii-process-data-transfer-1.1.0.0.jar.
General remarks:
- This release is compatible with the Data Sharing Framework version
>= 1.0.0. This release does not work with DSF versions< 1.0.0.
Features include:
- Error messages are now propagated using the camunda:errorMessageVariable extension in BPMN instead of setting additional process variables.
- Implemented the enhanced FHIR RESTful API for serving Binary resources, enabling direct streaming of Binary content to support larger data transfers in data use projects. It can be activated by setting the environment variable
DE_MEDIZININFORMATIK_INITIATIVE_DATA_TRANSFER_DIC_FHIR_SERVER_BINARY_STREAM_READ_ENABLEDtotruefor reading Binary resources by stream as DIC andDE_MEDIZININFORMATIK_INITIATIVE_DATA_TRANSFER_DMS_FHIR_SERVER_BINARY_STREAM_WRITE_ENABLEDfor writing Binary resources as stream for DMS. By default reading and writing Binary resources as stream is deactivated. For HAPI FHIR servers, the additional environment variableDE_MEDIZININFORMATIK_INITIATIVE_DATA_TRANSFER_DIC_FHIR_SERVER_BINARY_STREAM_READ_USE_HAPI_BLOB_STORAGE_OPERATIONhas to be set totrueif theblob-storageoperation is enabled. - DocumentReference resources can now include multiple attachments, allowing the transfer of multiple datasets in a single process execution.
- The environment variable
DE_MEDIZININFORMATIK_INITIATIVE_REPORT_DIC_FHIR_SERVER_OAUTH2_ISSUER_URLchanged toDE_MEDIZININFORMATIK_INITIATIVE_REPORT_DIC_FHIR_SERVER_OAUTH2_URL(withoutISSUER). It now matches its intended meaning and no longer requires setting the token URL. The same applies for the corresponding DMS configuration. See the Configuration Change section below. - Dependencies were updated where applicable.
- Updates CodeSystems of older process versions so that different versions of the process can be executed in parallel.
- The process can now be configured to add additional authorization rules based on the combination of
parent-organizationandrolein order to execute the process in different consortia. The default consortia is the MII with rolesDICfor sending andDMSfor receiving organizations, which cannot be removed. See DE_MEDIZININFORMATIK_INITIATIVE_DATA_TRANSFER_PROCESS_AUTHORIZATION_ADDITIONALLY_ALLOWED_SENDERS and DE_MEDIZININFORMATIK_INITIATIVE_DATA_TRANSFER_PROCESS_AUTHORIZATION_ADDITIONALLY_ALLOWED_RECEIVERS.
Configuration Change:
The environment variable DE_MEDIZININFORMATIK_INITIATIVE_REPORT_DIC_FHIR_SERVER_OAUTH2_ISSUER_URL changed to DE_MEDIZININFORMATIK_INITIATIVE_REPORT_DIC_FHIR_SERVER_OAUTH2_URL (without ISSUER). It now specifies the OIDC realm base endpoint instead of the OIDC token endpoint previously. The token endpoint is now automatically discovered using the OIDC discovery protocol. The discovery endpoint can be configured using the environment variable DE_MEDIZININFORMATIK_INITIATIVE_REPORT_DIC_FHIR_SERVER_OAUTH2_DISCOVERY_PATH, using a default value of /.well-known/openid-configuration. The same applies for the corresponding DMS configuration. Please update your configuration accordingly.
Issues closed:
- Use BPMN errorMessageVariable instead of specific self set variable #29
- Read Binary Content as Stream instead of a Binary Ressource #34
- Allow multiple attachments for DocumentReference resource #36
- Configuration parameters for OAuth2 token URLs incorrectly named issuer URLs #38
- Update Dependencies #42
- Deployment of process with different versions in parallel #44
- Process execution in different consortia #46
Contributors:
This release contains contributions @wetret, @schwzr, and @hhund.