De-identified data in TSD

The data provider then requires the mapping between de-identified and identified person IDs  - the koblingsn?kkel - to be stored in a safe location with access control.
TSD provides the following alternatives for storing this mapping. Which one to be used by your project depends on the access requirements set by the data provider.

Definitions/roles

• Data provider: the institution which provides the register data
• Service provider: in this case TSD
• Project administrator: person responsible for the TSD research project
• Project member: researcher in the project

Access, storage and procedures

Alternative 1: Koblingsn?kkel handled by data provider

Project administrator, project memebers and TSD have no access to the koblingsn?kkel.

Procedure:

1. Project administrator creates a TSD account for the data provider.
2. Data provider creates a PGP key-pair.
3. Data provider encrypts mapping.
4. Data provider uploads encrypted data to the TSD project.
5. Project administrator and/or project members request access from the data provider.
6. TSD has no direct operational involvement.

Alternative 2: Koblingsn?kkel handled by project administrator

Project members and TSD have no access to the koblingsn?kkel.

Procedure:

1. Project administrator creates a TSD account for the data provider.
2. Data provider creates a PGP key-pair.
3. Data provider encrypts mapping.
4. Data provider uploads encrypted data to the TSD project.
5. Data provider gives the private key to the project admninistrator.
6. Project administrator moves the encrypted data to their home directory.
7. Project administrator administers access themselves in TSD.

Alternative 3: Koblingsn?kkel handled by TSD

TSD grants access to data from requests.

Procedure:

1. Project administrator creates a TSD account for the data provider.
2. TSD creates a PGP key-pair. The private key is protected by a password created by TSD, outside project.
3. TSD gives the public key to the data provider.
4. Data provider encrypts the mapping between de-identified and identified data with the public key.
5. Data provider uploads encrypted data to TSD.
6. Project admnistrator requests access from TSD. 
7. TSD decrypts the data in a folder with limited access rights.
8. TSD can optionally store the decrypted data in a database if needed by the project