Stakeholder groups we consulted
We followed best practice guidance of the consultation in the HES privacy assessment.
The Information Commissioner’s Office (ICO) code of practice sets out the main steps to follow:
- Identify the need for a PIA.
- Describe the information flows.
- Identify the privacy and related risks.
- Identify and evaluate the privacy solutions.
- Sign off and record the PIA outcomes.
- Integrate the outcomes into the project plan.
- Consult with internal and external stakeholders throughout the process.
We carried all these steps as part of this project, except the second to last step, which will be carried out once the project is finished. We may need significant resources and the involvement of a variety of the Health and Social Care Information Centre (HSCIC) staff.
Processing and collecting data
To show a clear legal basis for processing, collecting, analysing or disclosing your personal data, the Secretary of State for Health directed us to:
- collect the Commissioning Data Sets (CDS)
- process this data in the Secondary Uses Services (SUS)
- publish it as the Hospital Episode Statistics (HES)
Find out more information from the spine services direction 2.
Find out how we use your personal data from the HES and information governance pages of our website.
These tables explain why we collect and process all data.
Personal data
Data categories
|
Yes |
N/A |
Justifications
|
Name |
|
X |
May be flowed by the provider to SUS if the NHS number is not known; never received in HES. |
Address
|
|
X |
May be flowed by the provider to SUS if the NHS number is not known; never received in HES.
|
Postcode
|
X |
|
Postcode is required for various geographical analyses; these derivations are performed during processing and only the postcode area and derived geographies are available for analysis, not the full postcode. |
DOB |
X |
|
It is important to know the age of people accessing NHS services for planning and commissioning purposes. Various “age at” derivations are performed during processing and it is those derivations which are made available for analysis, not the date of birth.
|
Age |
X |
|
Derived, not flowed. (see note on DOB).
|
Sex |
|
X |
|
Marital status
|
|
X |
|
Gender |
X |
|
It is important to know the gender of people accessing NHS Services for planning and commissioning purposes.
|
Living habits
|
|
X |
|
Professional training / awards
|
|
X |
|
Income / financial / tax situation
|
|
X |
|
Email address
|
|
X |
|
Physical description
|
|
X |
|
General identifier for example NHS number
|
x |
|
The NHS number is collected by SUS but is converted into a consistent, anonymised identifier which is then used for analytical purposes. Data containing NHS number is available for analysis but access is for specific purposes e.g. linkage to other data, only.
|
Home phone number
|
|
X |
|
Sharing and merging personal data
HES is routinely linked with other data sets to reduce the data burden on the NHS of submitting the same data several times. It's routinely linked with the ONS, mortality data, Diagnostic Imaging Data Set, Patient Reported Outcomes Monitoring data and Patient Level Information Costing System data.
Linkage is either directed by NHS England or the Department of Health, or performed under the terms of the Health and Social Care Information Centre Commencement Order. It can be linked with other data for external customers. Details of these disseminations can be found in the data release register.
How long we retain personal data
Data retention is in line with NHS guidance (30 years) and reviewed annually.
Achieving and maintaining data quality standards
Overview of the HES cleansing process

Full information about HES data quality can be found at the processing cycle.
HES data quality note
When Hospital Episode Statistics (HES) is published, additional data quality information and explanatory notes are also made available. For HES system users and those requesting extracts, data quality notes are published highlighting any specific known issues with the data to be considered when analysing the data.
HES data quality note content
The HES data quality notes are updated for each extract published and are available from 2007-08 data year onwards.
A typical note will contain:
- issues with specific fields
- issue with fields for a specific provider
- coverage issues
- processing errors
- mapping issues / duplicates missed / Auto clean error
- errors at SUS Ops stage / XML
- anything else that is considered useful for users to be made aware of
Where possible each entry will highlight the impact on analysis of the area it relates to and give a timescale of when this issue will be resolved.
Each note records the issues that are found at the time of publication. If additional issues are found post-publication, the note will be updated to reflect this.
Making people aware of their rights
NHS opt out – how it has been considered
Patients can either opt out with their health care provider (up to 10) and is recognised using the withheld identity reason code or using the opt out available through their GP practice. All identifiable disseminations of data have objections recorded at a GP Practice applied. Find more information about opting out of sharing your health records.
How individual rights are upheld
Patients can either opt out with their health care provider (up to 10) and is recognised using the withheld identity reason code. All identifiable disseminations of data have objections recorded at a GP Practice applied. Information about that process is found at opting out of sharing your confidential patient information webpage.
Technical and organisational controls for “information security”
HES is housed in a corporate data centre with an approved System Level Security policy. All internal access to HES is controlled via the internal Electronic Clear Data Access (eCDA) system. External access is controlled via the Data Access Request Service (DARS) process and Information Group Advising on the release of data (IGARD).
Last edited: 22 March 2023 1:02 pm