NHS Digital Data Release Register - reformatted

NHS Enfield Ccg projects

Project 1

423 data files in total were disseminated unsafely (information about files used safely is missing for TRE/"system access" projects).

🚩 NHS Enfield Ccg was sent multiple files from the same dataset, in the same month, both with optouts respected and with optouts ignored. NHS Enfield Ccg may not have compared the two files, but the identifiers are consistent between datasets, and outside of a good TRE NHS Digital can not know what recipients actually do.

Project 1 — NIC-41640-G0C5N

Opt outs honoured: N, Y, No - data flow is not identifiable, Yes - patient objections upheld (Excuses: Does not include the flow of confidential data)

Legal basis: Health and Social Care Act 2012, Section 251 approval is in place for the flow of identifiable data, Health and Social Care Act 2012 – s261(1) and s261(2)(b)(ii), National Health Service Act 2006 - s251 - 'Control of patient information'.

Purposes: ()

Sensitive: Sensitive

When:2017.06 — 2017.05.

Access method: Ongoing, Frequent Adhoc Flow

Data-controller type:

Sublicensing allowed:

Datasets:

Children and Young People's Health Services Data Set
Improving Access to Psychological Therapies Data Set
Local Provider Data - Acute
Local Provider Data - Ambulance
Local Provider Data - Community
Local Provider Data - Demand for Service
Local Provider Data - Diagnostic Services
Local Provider Data - Emergency Care
Local Provider Data - Experience Quality and Outcomes
Local Provider Data - Mental Health
Local Provider Data - Other not elsewhere classified
Local Provider Data - Population Data
Local Provider Data - Primary Care
Mental Health and Learning Disabilities Data Set
Mental Health Minimum Data Set
Mental Health Services Data Set
SUS Accident & Emergency data
SUS Admitted Patient Care data
SUS Outpatient data
Local Provider Data - Public Health & Screening services
Maternity Services Dataset
SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
SUS for Commissioners
Public Health and Screening Services-Local Provider Flows
Primary Care Services-Local Provider Flows
Population Data-Local Provider Flows
Other Not Elsewhere Classified (NEC)-Local Provider Flows
Mental Health-Local Provider Flows
Maternity Services Data Set
Experience, Quality and Outcomes-Local Provider Flows
Emergency Care-Local Provider Flows
Diagnostic Services-Local Provider Flows
Diagnostic Imaging Dataset
Demand for Service-Local Provider Flows
Community-Local Provider Flows
Children and Young People Health
Ambulance-Local Provider Flows
Acute-Local Provider Flows
Community Services Data Set
National Cancer Waiting Times Monitoring DataSet (CWT)
SUS (Accident & Emergency, Inpatient and Outpatient data)
Local Provider Data - Acute, Ambulance, Community, Demand for Service, Diagnostic Services, Emergency Care, Experience Quality and Outcomes, Mental Health, Other not elsewhere classified, Population Data, Primary Care

Type of data:

Objectives:

Invoice Validation
As an approved Controlled Environment for Finance (CEfF), the data processor receives SUS data identifiable at the level of NHS number according to S.251 CAG 7-07(a) and (c)/2013, to undertake invoice validation on behalf of the CCG. NHS number is only used to confirm the accuracy of backing-data sets and will not be shared outside of the CEfF. The CCG are advised by the CSU whether payment for invoices can be made or not.

Pseudonymised – SUS, Local Flows, Mental Health, IAPT, CYPHS and DIDs
To use pseudonymised data for the following datasets to provide intelligence to support commissioning of health services :
- SUS
- Local Flows
- Mental Health Minimum Data Set (MHMDS)
- Mental Health Learning Disability Data Set (MHLDDS)
- Mental Health Services Data Set (MHSDS)
- Maternity Services Data Set (MSDS)
- Improving Access to Psychological Therapy (IAPT)
- Child and Young People Health Service (CYPHS)
- Diagnostic Imaging Data Set (DIDS)
The pseudonymised data is required to ensure that analysis of health care provision can be completed to support the needs of the health profile of the population within the CCG area based on the full analysis of multiple pseudonymised datasets.

No record level data will be linked other than as specifically detailed within this application/agreement. Data will only be shared with those parties listed and will only be used for the purposes laid out in the application/agreement. The data to be released from NHS Digital will not be national data, but only that data relating to the specific locality of interest of the applicant.

Expected Benefits:

Invoice Validation
1. Financial validation of activity
2. CCG Budget control
3. Commissioning and performance management
4. Meeting commissioning objectives without compromising patient confidentiality
5. The avoidance of misappropriation of public funds to ensure the ongoing delivery of patient care

Pseudonymised SUS, Local Flows, Mental Health, Maternity, IAPT, CYPHS and DIDs
1. Supporting Quality Innovation Productivity and Prevention (QIPP) to review demand management, Integrated care and pathways.
a. Analysis to support full business cases.
b. Develop business models.
c. Monitor In year projects.
2. Supporting Joint Strategic Needs Assessment (JSNA) for specific disease types.
3. Health economic modelling using:
a. Analysis on provider performance against targets.
b. Learning from and predicting likely patient pathways for certain conditions, in order to influence early interventions and other treatments for patients.
c. Analysis of outcome measures for differential treatments, accounting for the full patient pathway.
4. Commissioning cycle support for grouping and re-costing previous activity.
5. Enables monitoring of:
a. CCG outcome indicators.
b. Non-financial validation of activity.
c. Successful delivery of integrated care within the CCG.
d. Checking frequent or multiple attendances to improve early intervention and avoid admissions.
e. Case management.
f. Care service planning.
g. Commissioning and performance management.
h. List size verification by GP practices.
i. Understanding the care of patients in nursing homes.
6. Feedback to NHS service providers on data quality at an aggregate and individual record level – only on data initially provided by the service providers.

Outputs:

Invoice Validation
1. Addressing poor data quality issues
2. Production of reports for business intelligence
3. Budget reporting
4. Validation of invoices for non-contracted events

Pseudonymised datasets:
1. Commissioner reporting:
a. Summary by provider view - plan & actuals year to date (YTD).
b. Summary by Patient Outcome Data (POD) view - plan & actuals YTD.
c. Summary by provider view - activity & finance variance by POD.
d. Planned care by provider view - activity & finance plan & actuals YTD.
e. Planned care by POD view - activity plan & actuals YTD.
f. Provider reporting.
g. Statutory returns.
h. Statutory returns - monthly activity return.
i. Statutory returns - quarterly activity return.
j. Delayed discharges.
k. Quality & performance referral to treatment reporting.
2. Readmissions analysis.
3. Production of aggregate reports for CCG Business Intelligence.
4. Production of project / programme level dashboards.
5. Monitoring of mental health quality matrix.
6. Clinical coding reviews / audits.
7. Budget reporting down to individual GP Practice level.
8. GP Practice level dashboard reports include high flyers.

Processing:

North East London DSCRO will apply Type 2 objections before any identifiable data leaves the DSCRO.
Invoice Validation
1. SUS Data is obtained from the SUS Repository to DSCRO North East London.
2. North East London DSCRO pushes a one-way data flow of SUS data into the Controlled Environment for Finance (CEfF) in the North East London CSU.
3. The CSU carry out the following processing activities within the CEfF for invoice validation purposes:
a. Checking the individual is registered to a particular Clinical Commissioning Group (CCG) and associated with an invoice from the national SUS data flow to validate the corresponding record in the backing data flow
b. Once the backing information is received, this will be checked against national NHS and local commissioning policies as well as being checked against system access and reports provided by NHS Digital to confirm the payments are:
i. In line with Payment by Results tariffs
ii. are in relation to a patient registered with a CCG GP or resident within the CCG area.
iii. The health care provided should be paid by the CCG in line with CCG guidance.
4. The CCG are notified that the invoice has been validated and can be paid. Any discrepancies or non-validated invoices are investigated and resolved between the CSU CEfF team and the provider meaning that no identifiable data needs to be sent to the CCG. The CCG only receives notification to pay and management reporting detailing the total quantum of invoices received pending, processed etc.

Pseudonymised – SUS, Local Flows, Mental Health, IAPT, CYPHS and DIDs
1. Data Services for Commissioners Regional Office (DSCRO) obtains a flow of data identifiable at the level of NHS number for SUS, Local Flows, Mental Health (MHSDS, MHMDS, MHLDDS), Maternity (MSDS), IAPT, CYPHS and DIDs for commissioning purposes.
2. Data quality management and pseudonymisation of data is completed by DSCRO North East London and the pseudonymised data is then passed securely to North East London CSU for the addition of derived fields, linkage and analysis.
3. North East London CSU then pass the processed, pseudonymised linked data to the CCG.
4. The CCG analyses the data to see patient journeys for pathway or service design, re-design and de-commissioning
5. Aggregation of required data for CCG management use will be completed by the CSU or the CCG as instructed by the CCG
6. Patient level data will not be shared outside of the CCG and will only be shared within the CCG on a need to know basis, as per the purposes stipulated within the Data Sharing Agreement. External aggregated reports only with small number suppression can be shared where contractual arrangements are in place.