Skip to content

Datatransfer DIC to GHT to CRR
Compare
Choose a tag to compare
@hhund hhund released this 07 Jul 16:30
· 301 commits to main since this release
v0.3.4
This tag was signed with the committer’s verified signature.
hhund Hauke Hund
GPG key ID: 15A40D58B4BF6C78
Learn about vigilant mode.
770dc1e
This commit was signed with the committer’s verified signature.
hhund Hauke Hund
GPG key ID: 15A40D58B4BF6C78
Learn about vigilant mode.

First release of the codex data-transfer processes supporting end-to-end data transfer from data integration centers (DIC) via the GECCO transfer hub (GTH) to the central research repository (CRR). The 0.3.4 release includes support to resolve Bloom Filters from the data integration center at the federated Trusted Third Party (fTTP). The connection to the fTTP can now be established via forwarding proxy server (corporate proxy). Bloom filters can be added to Patient resources as Identifier using the system http://www.netzwerk-universitaetsmedizin.de/sid/bloom-filter with the Bloom Filter base64 encoded as the identifier value. The 0.3.4 release improves support with ehrbase/fhir-bridge at the CRR, creating and updating resources now works. A connection test to the local GECCO FHIR server or fhir-bridge was added and handling of DNR Consent resources was fixed.

An installation guide for the DSF in NUM-CODEX can be found here: DSF Wiki NUM-CODEX Deployment.

A detailed description of the process can be found here: NUM-CODEX Wiki Description v0.3.4.

The DSF process plugin can be found here: codex-process-data-transfer-0.3.4.jar. This process-plugin requires hapi-fhir-client-5.1.0.jar to be installed as a regular DSF BPE plugin. Access to non DSF systems is simulated if not configured or implemented.

Upgrading from 0.3.2 or 0.3.3: 1.) Stop BPE, 2.) Delete codex-process-data-transfer-0.3.x.jar, 3.) Start BPE, 4.) Stop BPE, 5.) Add codex-process-data-transfer-0.3.4.jar, 6.) Start BPE

The deployment and configuration guide of the process can be found here: NUM-CODEX Wiki Deployment v0.3.4.

Example Task-Resources to start the trigger and send processes can be found here: NUM-CODEX Task-Resources. Transaction-Bundles with example Patient-Resources amongst others can be found here: NUM-CODEX Bundle-Resources. The Patient-Resources have either an identifier with a DIC pseudonym or Bloom Filter.

Assets 4
Loading