Preparations for HiGHmed Data Sharing Process

[wetret]

• Split the openEHR ResultSet translators into one translator for RBF calculation and one translator for RSA encryption
• Create a consent client stub implementation that returns the openEHR ResultSet as it is
• Create a pseudonymisation client stub implementation that returns the openEHR ResultSet as it is
• Adapt the MPI client and the openEHR client to the new property naming structure
• Replace the MPI client pkcs#12 keystore with a PEM encoded certificate and private key file
• Replace the openEhr client pkcs#12 truststore with e PEM encoded truststore file

We should also discuss, if the translators and client implementations (not the interfaces and stubs) should be moved into the highmed-processes repository. @hhund What do you think?

[wetret]

The following three points were implemented with commit 4e7bdb8895e94d9e20f8c352c337ed60550944d9:

• Adapt the MPI client and the openEHR client to the new property naming structure
• Replace the MPI client pkcs#12 keystore with a PEM encoded certificate and private key file
• Replace the openEhr client pkcs#12 truststore with e PE encoded truststore file

[wetret]

The point

• Split the openEHR ResultSet translators into one translator for RBF calculation and one translator for RSA encryption

was implemented with commit 3e8076ae85556eb1ef8ba3cd2aed1dab3e0938a7.

[wetret]

The point

• Create a consent client stub implementation that returns the openEHR ResultSet as it is

was implemented with commit c9e720a5ad517ce1506b97d4c323f298240cceb8.

[wetret]

163b89fcd1a409a38a3f54fa59cbdcd90f3ae9af implements the point:

• Create a pseudonymisation client stub implementation that returns the openEHR ResultSet as it is