To maximise data security and data subject confidentiality HIC anonymises the data used for research using a project-specific anonymisation procedure.
Step 1: Project Dataset
Every project dataset will be uniquely anonymised before being made available to an Approved Data User, unless identifiable data is required and is specifically approved by the Data Controller.
Step 2: Pro-CHI
The Pro-CHI is generated by the HIC Data Analyst to uniquely anonymise a typical NHS dataset CHI number. This capability is located on a secure server, accessible only by the HIC Data Analyst and the System Administrator.
Step3: Anonymisation Process
The anonymisation process removes all names and addresses from the dataset.
As standard it also:
- Uniquely anonymises the CHI into a project-specific pseudo-CHI (Pro-CHI)
- The date of birth – standard anonymisation is 3 months whereby the day will become ‘01’ and the month will become the middle of the appropriate quarter year e.g. 24/01/2005 will be anonymised as 01/02/2005).
- The postcode is restricted to postcode district / outward postcode only by removing the last 3 digits, e.g. DD1, DD10.
- The GP code, the GMC number (General Medical Council registration number), the GP Practice code and the Pharmacy code are all replaced by anonymous versions.
- If data is being provided via HIC Services that has already been effectively anonymised elsewhere, this procedure may not need to be repeated by HIC Services.
- Where there is no CHI a unique pseudo-anonymised identifier will be allocated to each individual.
- Aggregated data provided for study feasibility will not show values <5.
These steps will help ensure that identification of individual patients is not possible, while retaining the ability to link patient data across multiple data sets for a particular project.
Step 4: Data Request
Any request to the HIC Data Analyst for more detail about any of the Anonymised Data items listed above will be treated as a request for identifiable data, which will require study-specific Caldicott Guardian approval.
Step 5: Project Specific
The Pro-CHI is project-specific ensuring that data provided to any one project remains within the bounds of linkage as approved for that project.
Step 6: Traceability
The Pro-CHI allows traceability of any HIC Services Project Dataset to the source of the data and the subsequent Approved Data User for that data.