Skip to content

BloomFilter, Proxy Server and FHIR-Bridge Support

Compare
Choose a tag to compare
@hhund hhund released this 06 Jul 19:41
· 320 commits to main since this release
v0.3.3
379785a

Unfortunately there is an error in the proxy configuration of the fTTP client. Do not use this release in production! - see v0.3.4

Third Test Release of the codex data-transfer processes for use with data integration centers (DIC), the GECCO transfer hub (GTH) and the central research repository (CRR). This 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 and the BloomFilter Base64 encoded as the value. The 0.3.3 release improves support with ehrbase/fhir-bridge.

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.3.

The DSF process plugin can be found here: codex-process-data-transfer-0.3.3.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: 1.) Stop BPE, 2.) Delete codex-process-data-transfer-0.3.2.jar, 3.) Start BPE, 4.) Stop BPE, 5.) Add codex-process-data-transfer-0.3.3.jar, 6.) Start BPE

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

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.