SORMAS 2 SORMAS - Sharing process for data access across health departments

[markusmann-vg]

Situation Description & Motivation

Situation Description
The German health departments want to be able to share data between them.

Feature Description for brainstorming
There should be an option to either include the senstitive data or pseudonymize sensitive data.
There should be an option to decide wether the case or contact can be edited by the recipient or just viewed.
There should be an option to handover the ownership to the full case or contact or keep the ownership and allow the recipient to just view or edit.
If the ownership of the case or contact is given to the recipient, we could either:

keep the contact or case
delete the case or contact
If the ownership stays with the sender and the recipient is able to edit the case or contact, we should also allow to update the case or contact with the latest changes.

This process can be triggered manually but should also include a possibility to be triggered automatically.

Possible Alternatives
Improving the export / import functionality

Tasks

• [DRAFT] SORMAS 2 SORMAS Interface for cases and contacts  #2576
• [SORMAS2SORMAS] Creation of certificates to send and receive data [1] #2621
• [SORMAS2SORMAS] Setting up the TrustStore [1] #2622
• [SORMAS2SORMAS] Create list with server access data [1] #2623
• [SORMAS2SORMAS] REST Method for a certain REST-User to receive a case/contact [5] #2624
• [SORMAS2SORMAS] UI Tasks #2625
• [SORMAS2SORMAS] Add encryption [2] #2626
• [SORMAS2SORMAS] Add responses to the sending system [2] #2627
• [SORMAS2SORMAS] Manage Ownership  #2628
• [SORMAS2SORMAS] sending cases with related contacts #2629
• [SORMAS2SORMAS] Integrate encryption #2844
• [SORMAS2SORMAS] Share cases and contacts in bulk [3] #3136
• [SORMAS2SORMAS] Can't share cases with Home as Place of stay #3156
• [SORMAS2SORMAS] Transfer samples [3] #3210
• [SORMAS2SORMAS] Sending and receiving shared data should be possible [3] #3388
• [SORMAS2SORMAS] Sending and receiving shared data doesn't work when changing and adding data on the second server #3608
• Forward LabMessages to responsible health department via SORMAS2SORMAS [3] #3742
• [SORMAS2SORMAS] Trying to share samples results in an error #3762
• [SORMAS2SORMAS] Introduce Re-selecting an instance to re-share data [5] #3763
• [SORMAS2SORMAS] When sending and receiving shared data, some of the modified fields don't get shared back  #3817
• [SORMAS2SORMAS] Remove option to pseudonymize when ownership is sent [0.5] #4107
• [SORMAS2SORMAS] Resending data in bulk edit mode fails with unclear generic error message #4190
• [SORMAS2SORMAS] Add filter to show cases and contacts received by other health departments [1] #4203
• [SORMAS2SORMAS] Sharing data should work, even when the receiving SORMAS instance does not have the same facilities and sends back the case [2] #4309
• [SORMAS2SORMAS] SurvNet external tokens ("Aktenzeichen") are not globally unique  #4413
• Don't override the reporting user, when a case is sent back to the source system [SORMAS2SORMAS] #4414
• [SORMAS2SORMAS] As a recipient I want to be able to accept or reject a shared case from another SORMAS Instance [5] #4423
• [SORMAS 2 SORMAS] Symptom journal registrations are shared #5333
• [Sormas2Sormas] Returning cases without contacts or samples leaves contacts and samples disabled in both instances #5562
• Set up SORMAS X (eXchange) cert sharing [CONCEPT] #5597
• [S2S] Refactor and deduplicate S2S code #5599
• OPTION A: Report automatically to the reporting system when a case was sent to another instance of SORMAS [3?] #5630
• Simplify and cleanup AbstractSormasToSormasInterface  #5671
• SormasToSormasRestClient should handle authentication automatically #5679
• [S2S] Cases > Revoke Share results in error #5887
• [S2S] Merge the new S2S parts together #5890
• Add tests and runtime checks to enforce HTTPS in S2S  #5906
• [Sormas2Sormas] Automatic Sync with every instance, when a shared dataset changed [3] #6019
• [Sormas2Sormas] Feature configuration for events, cases & contacts, Lab-Messages [1] #6021
• [Sormas2Sormas] View share chain for each case shared/received trough S2S [5]  #6033
• [ Sormas2Sormas ] Sharing and rejecting multiple times results in server error #6067
• [SORMAS2SORMAS] Shares > Sorting by column Ownership handed over results in error #6086
• [SORMAS2SORMAS] Cases > Share > Share Samples doesn't include samples on first share #6092
• [SORMAS2SORMAS] Shares > Share Requests > Response Comment (reject/accept) [1] #6122
• [SORMAS2SORMAS] Shares > Share requests > Rejected items should delete preview data [1] #6180
• Share Entity > Popup window options rewording (English) #6192
• [S2S] Replace Redis with etcd #6214
• [S2S] Revoking accepted case results in inconsistent status of cases #6241
• S2S code is missinglog statements in some places #6421
• #5229 Add multiple variables to detailed and custom export #6341
• Naive sign then encrypt as we do in in S2S EncrpytionService is not secure #6433
• [S2S] Column header is not available for translation #6439
• [CI] GitHub made improvements to Java CIs #6693
• Returns do not trigger a share request but happen automatically instead [5] #6642
• Refactor S2S source directory #6496
• Samples have to be send when ownership is handed over #6684
• Add Configuration for S2S to exclude fields from sharing [3] #6875
• [S2S] When sharing a case the immunization and vaccination information should be shared as well  #6886
• Create missing history tables for S2S tables #6949
• [S2S] External ID of the pathogen test result is sent from Sormas A to Sormas B when ownership is handed over #7014
• Move the validation logic of core S2S entities to S2S validator classes #7132
• Fully split S2S processing from validation #7133
• Create S2S validator classes and move validation logic there #7136
• Add missing entities to database tables to the data dictionary and the database export [3] #7220
• Automatic deletion for S2S share info, origin and requests [2] #8010
• Add backend checks for Sormas2Sormas [5] #8540
• [S2S] Avoiding simultaneous work of two health departments - preventing sharing twice to the same target system as long as the target system has not yet accepted or rejected [2] #8576
• S2S_Processed lab messages should be transferred [3] #8950
• Reducing the risk that the link between case and associated contact gets lost in source and/or target system [2] #9125
• S2S_deactivate share parameter 'share associated contacts' (for cases) [2] #9146
• [S2S] Remove decision between "personal data" and "sensitive data" [1] #9521
• [S2S] Add a duplicate detection warning when sharing a case with another instance [5] #9527
• S2S_Revision of the 'share requests' directory_ Part 1 [3] #9755
• S2S_added sample after sharing a case/contact does not get shared [2] #9771
• S2S_Revision of the case directory and contact directory_Part 1 [1] #9787
• S2S_Documents should be visible, downloadable and deletable after share [5] #9804
• S2S_I simultaneous work possible_ II. no change of jurisdiction_ III: strange error message #9836
• S2S_contacts_change behaviour if share with hand over the ownership = true [0.5] #9840

Alternatives

Risks

Additional Information