Pseudonymisation: Difference between revisions

From Discovery Data Service
Jump to navigation Jump to search
No edit summary
No edit summary
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Discovery uses the NHS standard [https://www.openpseudonymiser.org/ Open Pseudonymiser] to create pseudonymised data by taking one or more inputs (NHS number, date of birth) and a salt file to generate a pseudo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF". By using different [[Pseudonymisation#salt|salt files]] you can generate different pseudo IDs from the same data input; each research project uses a different salt to create their own pseudo IDs generated for patient records they use.
Discovery uses the NHS standard [https://www.openpseudonymiser.org/ Open Pseudonymiser] to create pseudonymised data by taking one or more inputs (NHS number, date of birth) and a salt file to generate a pseudo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF".  
 
By using different [[Pseudonymisation#salt|salt files]] you can generate different pseudo IDs from the same data input; each research project uses a different salt to create their own pseudo IDs generated for patient records they use.


Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration; from NHS number only or NHS number and date of birth.  
Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration; from NHS number only or NHS number and date of birth.  
Line 13: Line 15:
A key server is a website or API that securely stores and shares salt files.
A key server is a website or API that securely stores and shares salt files.


Discovery doesn't currently provide a key kerver; Kambiz Boomla acts as the London DDS key server - he's got all the salt files and can email them out to whoever needs them.
Discovery doesn't currently provide a key server and instead uses a manual approach to managing salt files. A true automated key server is planned for the future.

Revision as of 10:04, 3 September 2020

Discovery uses the NHS standard Open Pseudonymiser to create pseudonymised data by taking one or more inputs (NHS number, date of birth) and a salt file to generate a pseudo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF".

By using different salt files you can generate different pseudo IDs from the same data input; each research project uses a different salt to create their own pseudo IDs generated for patient records they use.

Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration; from NHS number only or NHS number and date of birth.

Salt files

A salt file is used to generate a pseudo ID from a given input such as a NHS number.

Each customer/project can supply their own salt files, and each subscriber database supports an unlimited number of pseudo IDs generated for each patient. For example, the CEG database has 30 pseudo IDs for each patient, each generated from the NHS number and a separate salt file.

For more information see https://www.openpseudonymiser.org/FAQ.aspx

Key server

A key server is a website or API that securely stores and shares salt files.

Discovery doesn't currently provide a key server and instead uses a manual approach to managing salt files. A true automated key server is planned for the future.