De-Identification / Pseudonymisation Solutions
Facilitates compliance with legal and NHS data policy requirements on the treatment of Patient Identifiable Data (PID) for health care management, research and other secondary uses. Sapior solutions provide clear evidence of applying best practices to significantly reduce privacy breach risks.
All of our solutions are based on our de facto national standard Pseudonymisation engine, as used by the English NHS Spine Secondary Uses Service (SUS). They provide the most robust NHS-grade pseudonymisation to fully meet pseudonymisation functionality requirements for the Pseudonymisation Implementation Project (PIP).
Sapior Solutions de-identify and re-identify
De-identification – Sapior de-identifies PID by replacing it with shapeable pseudonyms. This is done on a consistent basis so that patient records are distinguishable and linkable, but not identifiable.
Re-identification – The ability to roll back to PID is given on a case-by-case permission basis to relevant users. This re-identification process is automated and eliminates manual, error-prone and time-consuming encryption key management issues.
Learn more about when and why should you de-identify. Read more…
We offer a range of De-identification solutions depending on how frequently and how much data you need to de-identify.
The following matrix is a guide to our solutions based on usage frequency:
| Daily Use | Appliance Read more… In-house or N3 web services appliance provides full pseudonymisation functionality for PIP e.g. Commissioning collaboratives, sensitive data enclaves, etc. |
|||||||
| Periodic Use
(3-50 times per year) |
SaaS
Remote software as a service provision via browser e.g. Medical/clinical audit, predictive modelling requiring regular data feeds (PARR/CPM), NHS & Social care interworking, etc. |
|||||||
| Occasional Use
(1-2 times per year) |
Pay-as-you-go internet-based service (limited configurability)
or Data harvesting service (fully configurable) Read more… e.g. research projects and other one-off data collections |
|||||||
FastTrack Pseudonymisation ServiceAll healthcare organisations need to protect Patient Identifiable Information. In some instances, this information must be shared with other organisations not directly involved with the provision of patient healthcare. In these instances, the data must be 'de-identified' i.e. that is the patient labels and other data items (that can be used to identify the patient) are modified so that the patients identity cannot be guessed. This process is known as Pseudonymisation.
What is Pseudonymisation ?Pseudonymisation is the technical process that modifies data containing Patient Identifiable Information making it 'effectively anonymous'. Once in this state, the data is safe and can be shared without breaching the 1998 Data Protection Act. Pseudonymisation is a complex computing technique that has to be applied with care. Pseudonymisation ensures that certain data fields that assist with revealing the identity of a patient are either removed or changed using special computer algorithms. In addition, the organisations needs to ensure that they are compliant with the security controls described in IGT, many of which are based on ISO 27001 guidelines. History of Pseudonymisation in the NHSPseudonymisation is widely used in the NHS. In 2004, a centralized system for the SPINE and Secondary Uses Service (SUS) was introduced using software provided by Sapior. SUS holds commissioning data sets (CDS) and Payment by Results (PbR) data for all hospitals in the country. Sapior Multipack PseudonymisationSapior Multipack enables organisations to provide pseudonymised datasets quickly and easily without the need for skilled IT programmers. Sapior Multipack simplifies the process by enabling the pseudonymised data to be created without investment in an expensive hardware and software solution. Sapior Multipack is available on a Pay-As-You-Go service for single use. Discounts for regular usage are available via the Multipack pricing. Delivery of Sapior Pay-As-You-Go and MultipackThe Sapior Pseudonymisation process is very straight forward:
Service
|
||||||||
