Pseudonymisation - Revision history

JackBarker at 07:48, 14 May 2022

2022-05-14T07:48:23Z

← Older revision		Revision as of 07:48, 14 May 2022
Line 16:		Line 16:

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

			=== De-identification of the record ===
			This is how the Discovery Compass v2 databases are de-identified

			For each patient demographic record:

			if Subscriber Configuration -> isPseudonymised = true:

			* NHS number is blanked
			* Title, Firstname and Surname are blanked
			* Date of Birth is set as 01/MM/yyyy. NOTE: This can be extended further with a DOB mask to only include the year, i.e. 01/01/yyyy
			* Telecom/fax/email values are blanked
			* All address lines are blanked and only the postcode prefix is set, I.e. LS1
			* All UPRN address coordinates are blanked

			<br />

JoC at 10:04, 3 September 2020

2020-09-03T10:04:46Z

← Older revision		Revision as of 10:04, 3 September 2020
Line 15:		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 server and instead uses a manual approach to managing salt files. A true key server is planned for the future.		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.

JoC: /* Key server */

2020-09-03T10:04:18Z

Key server

← Older revision		Revision as of 10:04, 3 September 2020
Line 15:		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 key server is planned for the future.

JoC at 09:59, 3 September 2020

2020-09-03T09:59:07Z

← Older revision		Revision as of 09:59, 3 September 2020
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.

JoC at 09:58, 3 September 2020

2020-09-03T09:58:30Z

← Older revision		Revision as of 09:58, 3 September 2020
Line 1:		Line 1:
	Discovery uses the NHS standard ~~'''Open Pseudonymiser''' (~~https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, date of birth) and a salt file to generate a ~~psuedo~~ 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 ~~psueudo~~ 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 13:
	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 Server ,~~ Kambiz Boomla acts as the London DDS ~~"Key Server" in that~~ he's got all the salt files and can email them out to whoever needs them.		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.

	~~None of the above necessarily will make sense, but should be clearer if you have a quick read of the docs on the above website~~.

JoC at 09:55, 3 September 2020

2020-09-03T09:55:28Z

← Older revision		Revision as of 09:55, 3 September 2020
Line 1:		Line 1:
	Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, ~~DoB~~) and a salt file to ~~generates~~ a psuedo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF". By using different [[Pseudonymisation#salt\|salt files]] you can generate different pseudo IDs from the same ~~inputs, the idea being that different~~ research ~~projects would each use~~ a different salt~~, so would have~~ their own psueudo IDs generated for patient records they use.		Discovery uses the NHS standard '''Open Pseudonymiser''' (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, date of birth) and a salt file to generate a psuedo 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 psueudo IDs generated for patient records they use.

	Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration~~. Configuration allows generating pseudo IDs~~ 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.
	~~<span id="salt"></span>~~
	=== Salt files ===		=== Salt files ===
	~~Each customer/project can supply their own salt files (a~~ salt file is used to generate a pseudo ID from a given input~~, e.g. NHS number). Each subscriber database supports an unlimited number of pseudo IDs generated for each patient (e.g. CEG database has 30 pseudo IDs for each patient, each generated from the~~ NHS number ~~and a separate salt file)~~.		A salt file is used to generate a pseudo ID from a given input such as a NHS number.

	~~DDS doesn't currently provide a "Key Server" (~~an ~~API~~ for ~~securely sharing~~ salt ~~files)~~. A ~~Key Server~~ is ~~essentially~~ a website/API that ~~would allow a customer to store their~~ salt files ~~and allow us and other parties (e~~.~~g. researchers) to access them. Currently~~, Kambiz Boomla acts as the London DDS "Key Server" in that he's got all the salt files and can email them out to whoever needs them.		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 , Kambiz Boomla acts as the London DDS "Key Server" in that he's got all the salt files and can email them out to whoever needs them.

	None of the above necessarily will make sense, but should be clearer if you have a quick read of the docs on the above website.		None of the above necessarily will make sense, but should be clearer if you have a quick read of the docs on the above website.

JoC at 09:38, 3 September 2020

2020-09-03T09:38:32Z

← Older revision		Revision as of 09:38, 3 September 2020
Line 1:		Line 1:
	Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, DoB) and a salt file to generates a psuedo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF". By using different salt files you can generate different pseudo IDs from the same inputs, the idea being that different research projects would each use a different salt, so would have their own psueudo IDs generated for patient records they use.		Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, DoB) and a salt file to generates a psuedo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF". By using different [[Pseudonymisation#salt\|salt files]] you can generate different pseudo IDs from the same inputs, the idea being that different research projects would each use a different salt, so would have their own psueudo IDs generated for patient records they use.

	Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration. Configuration allows generating pseudo IDs from NHS number only or NHS number and date of birth.		Pseudo IDs are generated in DDS subscriber databases based on subscriber-specific configuration. Configuration allows generating pseudo IDs from NHS number only or NHS number and date of birth.
			<span id="salt"></span>
	Salt ~~Files~~		=== Salt files ===

	Each customer/project can supply their own salt files (a salt file is used to generate a pseudo ID from a given input, e.g. NHS number). Each subscriber database supports an unlimited number of pseudo IDs generated for each patient (e.g. CEG database has 30 pseudo IDs for each patient, each generated from the NHS number and a separate salt file).		Each customer/project can supply their own salt files (a salt file is used to generate a pseudo ID from a given input, e.g. NHS number). Each subscriber database supports an unlimited number of pseudo IDs generated for each patient (e.g. CEG database has 30 pseudo IDs for each patient, each generated from the NHS number and a separate salt file).

JoC: Created page with "Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, DoB) and a salt..."

2020-09-03T09:34:02Z

Created page with "Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, DoB) and a salt..."

New page

Discovery uses the NHS standard Open Pseudonymiser (https://www.openpseudonymiser.org/) to create pseudonymised data by taking one or more inputs (NHS number, DoB) and a salt file to generates a psuedo ID that looks like "A541CAF13D376B9AD1072C3096AE141CFF1E67B027CEB632D194D3C6577AB8BF". By using different salt files you can generate different pseudo IDs from the same inputs, the idea being that different research projects would each use a different salt, so would have their own psueudo IDs generated for patient records they use.

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

Salt Files

Each customer/project can supply their own salt files (a salt file is used to generate a pseudo ID from a given input, e.g. NHS number). Each subscriber database supports an unlimited number of pseudo IDs generated for each patient (e.g. CEG database has 30 pseudo IDs for each patient, each generated from the NHS number and a separate salt file).

DDS doesn't currently provide a "Key Server" (an API for securely sharing salt files). A Key Server is essentially a website/API that would allow a customer to store their salt files and allow us and other parties (e.g. researchers) to access them. Currently, Kambiz Boomla acts as the London DDS "Key Server" in that he's got all the salt files and can email them out to whoever needs them.

None of the above necessarily will make sense, but should be clearer if you have a quick read of the docs on the above website.