NHS Digital Data Release Register - reformatted

NHS South Warwickshire Ccg projects

DSfC - NHS South Warwickshire - Comm (GP federation)
DSfC - NHS South Warwickshire CCG; IV
GDPPR COVID-19 CCG - Pseudo
Project 4
Project 5
Project 6
Project 7
Project 8
Project 9

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

🚩 NHS South Warwickshire Ccg was sent multiple files from the same dataset, in the same month, both with optouts respected and with optouts ignored. NHS South Warwickshire 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.

DSfC - NHS South Warwickshire - Comm (GP federation) — DARS-NIC-168692-Y5S4C

Type of data: information not disclosed for TRE projects

Opt outs honoured: No - data flow is not identifiable, Anonymised - ICO Code Compliant (Section 251, Does not include the flow of confidential data)

Legal basis: Health and Social Care Act 2012 – s261(1) and s261(2)(b)(ii), Health and Social Care Act 2012 s261(1) and s261(2)(b)(ii), Health and Social Care Act 2012 s261(2)(b)(ii)

Purposes: No (Clinical Commissioning Group (CCG), Sub ICB Location)

Sensitive: Sensitive

When:DSA runs 2019-05-01 — 2022-04-30 2018.06 — 2021.03.

Access method: Frequent adhoc flow, Frequent Adhoc Flow, One-Off

Data-controller type: NHS COVENTRY AND WARWICKSHIRE CCG, NHS COVENTRY AND WARWICKSHIRE ICB - B2M3M

Sublicensing allowed: No

Datasets:

Acute-Local Provider Flows
Ambulance-Local Provider Flows
Children and Young People Health
Community Services Data Set
Community-Local Provider Flows
Demand for Service-Local Provider Flows
Diagnostic Imaging Dataset
Diagnostic Services-Local Provider Flows
Emergency Care-Local Provider Flows
Experience, Quality and Outcomes-Local Provider Flows
Improving Access to Psychological Therapies Data Set
Maternity Services Data Set
Mental Health and Learning Disabilities Data Set
Mental Health Minimum Data Set
Mental Health Services Data Set
Mental Health-Local Provider Flows
National Cancer Waiting Times Monitoring DataSet (CWT)
Other Not Elsewhere Classified (NEC)-Local Provider Flows
Population Data-Local Provider Flows
Primary Care Services-Local Provider Flows
Public Health and Screening Services-Local Provider Flows
SUS for Commissioners
Civil Registration - Births
Civil Registration - Deaths
National Cancer Waiting Times Monitoring DataSet (NCWTMDS)
Improving Access to Psychological Therapies Data Set_v1.5
Civil Registrations of Death
Community Services Data Set (CSDS)
Diagnostic Imaging Data Set (DID)
Improving Access to Psychological Therapies (IAPT) v1.5
Mental Health and Learning Disabilities Data Set (MHLDDS)
Mental Health Minimum Data Set (MHMDS)
Mental Health Services Data Set (MHSDS)

Objectives:

Commissioning
To use pseudonymised data to provide intelligence to support the commissioning of health services. The data (containing both clinical and financial information) is analysed so that health care provision can be planned to support the needs of the population within the CCG area.
The CCGs commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.
The following pseudonymised datasets are required to provide intelligence to support commissioning of health services:
- Secondary Uses Service (SUS+)
- Local Provider Flows
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
- Mental Health Services Data Set (MHSDS)
- Maternity Services Data Set (MSDS)
- Improving Access to Psychological Therapy (IAPT)
- Child and Young People Health Service (CYPHS)
- Community Services Data Set (CSDS)
- Diagnostic Imaging Data Set (DIDS)
- National Cancer Waiting Times Monitoring Data Set (CWT)
The pseudonymised data is required to for the following purposes:
§ Population health management:
• Understanding the interdependency of care services
• Targeting care more effectively
• Using value as the redesign principle
§ Data Quality and Validation – allowing data quality checks on the submitted data
§ Thoroughly investigating the needs of the population, to ensure the right services are available for individuals when and where they need them
§ Understanding cohorts of residents who are at risk of becoming users of some of the more expensive services, to better understand and manage those needs
§ Monitoring population health and care interactions to understand where people may slip through the net, or where the provision of care may be being duplicated
§ Modelling activity across all data sets to understand how services interact with each other, and to understand how changes in one service may affect flows through another
§ Service redesign
§ Health Needs Assessment – identification of underlying disease prevalence within the local population
§ Patient stratification and predictive modelling - to identify specific patients at risk of requiring hospital admission and other avoidable factors such as risk of falls, computed using algorithms executed against linked de-identified data, and identification of future service delivery models

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.
Processing for commissioning will be conducted by the CCG’s own analysts or by NHS Arden and Greater East Midlands Commissioning Support Unit.

Yielded Benefits:

The benefits of linking in primary care data have been realised as expected. The inclusion of primary care data enables achievement to be assessed more accurately, and to make more targeted commissioning decisions.

Expected Benefits:

Commissioning
There are several key benefits of having a linked dataset:
1. Better forecasting and demand modelling: Having a linked dataset enables more robust demand modelling through having a joined up picture of service usage. A linked dataset will inform and enable decisions about adapting and prioritising the delivery of services between the individual providers of South Warwickshire CCG.
2. Financial planning: A linked dataset will allow better analysis of the costs of different types of care that are currently being delivered. This will allow the most efficient and optimal mix of care to be planned and subsequently provided. It will also support the delivery of new contract types, covering multiple providers.
3. Linked data will provide a more accurate picture of health and care service usage by individuals across the CCG, thus enabling services to be adapted and delivered in a way which targets those at greatest risk and aims to reduce their likelihood of having a significant health event or deteriorating.
4. Better monitoring of performance: A linked dataset will enable more accurate monitoring of the overall health and care system across South Warwickshire, from a patient / service user perspective. This will ensure that patients / service-users are at the centre of the health and care system and also enable alternative measures of performance and more effective monitoring to be put in place.
5. Performance monitoring for the Outcomes Framework for the Out of Hospital programme: A linked data set will support the key Out of Hospital objective of moving towards a whole-population Outcomes Framework. In order to contract and monitor achievement of outcomes accurately, measurement of outcomes must be robust but, without a linked dataset, outcomes can only be partially captured based on a specific service or care setting. This means that outcomes measurement will not be as robust.

All of the above will contribute towards the delivery of a more joined up, more efficient and higher quality care service and improved population outcomes.

Outputs:

Commissioning
Commissioner reporting:
• Re-ablement
• Emergency admissions analysis
• Reduction in length of stay and transfer of care delays
• Planned care by POD view - activity plan & actuals YTD.
• Identify baselines to measure future new service
• Production of aggregated reports for integrated business intelligence
• Production of project / programme level dashboards
• Patient population profiling

1. Supporting Quality Innovation Productivity and Prevention (QIPP) to review demand management and pathways
2. Supporting Joint Strategic Needs Assessment (JSNA) for specific disease types
3. Health economic modelling using:
a. Analysis on provider performance against 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC).
4. Enables monitoring of: CCG outcome measures
a. Non-financial validation of activity
b. Successful delivery of integrated care
c. Checking frequent or multiple attendances to improve early intervention and avoid admission
d. Case Management
e. Care service planning
f. Commissioning and performance management
g. List size verification by GP provider
h. Understanding care of patients in nursing homes

Processing:

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

The Data Controller and any Data Processor will only have access to records of patients of residence and registration within the CCG.

Patient level data will not be shared outside of the CCG unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.
All access to data is managed under Roles-Based Access Controls

No patient level data will be linked other than as specifically detailed within this 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 and that data required by the applicant.
NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract ie: employees, agents and contractors of the Data Recipient who may have access to that data)

Segregation
Where the Data Processor and/or the Data Controller hold both identifiable and pseudonymised data, the data will be held separately so data cannot be linked.

All access to data is auditable by NHS Digital.

Commissioning
The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
1. SUS+
2. Local Provider Flows (received directly from providers)
a. Acute
b. Ambulance
c. Community
d. Demand for Service
e. Diagnostic Service
f. Emergency Care
g. Experience, Quality and Outcomes
h. Mental Health
i. Other Not Elsewhere Classified
j. Population Data
k. Primary Care Services
l. Public Health Screening
3. Mental Health Services Data Set (MHSDS)
4. Maternity Services Data Set (MSDS)
5. Improving Access to Psychological Therapy (IAPT)
6. Child and Young People Health Service (CYPHS)
7. Community Services Data Set (CSDS)
8. Diagnostic Imaging Data Set (DIDS)
9. National Cancer Waiting Times Monitoring Data Set (CWT)
Data quality management and pseudonymisation is completed within the DSCRO using the Open Pseudonymiser tool and is then disseminated as follows:
Data Processor 1 – NHS Arden and Greater East Midlands Commissioning Support Unit
1. Pseudonymised SUS+, Local Provider data, Mental Health data (MHMDS), Maternity data (MSDS), Improving Access to Psychological Therapies data (IAPT), Child and Young People’s Health data (CYPHS), Community Services Data Set (CSDS). Diagnostic Imaging data (DIDS) and National Cancer Waiting Times Monitoring Data Set (CWT) only is securely transferred from the DSCRO to NHS Arden and Greater East Midlands Commissioning Support Unit
2. NHS Arden and Greater East Midlands Commissioning Support Unit land the data only in the secure management environment. The data is then sent directly to the CCG.
3. Identifiable GP Data (primary care data) is securely sent from the GP systems to South Warwickshire GP Federation Ltd. South Warwickshire GP Federation Ltd act as data processor on behalf of the GP practices.
4. South Warwickshire GP Federation Ltd pseudonymise the primary care data using the Open Pseudonymiser tool, on behalf of the GP Practices, using the encryption key provided by the DSCRO specific to each project.
5. South Warwickshire GP Federation Ltd then pass the pseudonymised primary care data in consistently pseudonymised form at patient level to the CCG via secure FTP.
6. The CCG undertake linkage of the data.
7. Allowed linkage is between the data sets contained within point 1 and 6.
8. The CCG analyse the data to:
a. See patient journeys for pathways or service design, re-design and de-commissioning.
b. Check recorded activity against contracts or invoices and facilitate discussions with providers.
c. Undertake population health management
d. Undertake data quality and validation checks
e. Thoroughly investigate the needs of the population
f. Understand cohorts of residents who are at risk
g. Conduct Health Needs Assessments
h. Produce high level reports
9. Aggregation of required data for CCG management use will be completed by the CCG.
10. 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 as set out within NHS Digital guidance applicable to each data set.
The CCG will be responsible for linking the data but will not have access to the pseudonymisation tool, and will have no means or requirement to re-identify any data. The Encryption key will only be shared by the DSCRO with South Warwickshire GP Federation, who will have documented responsibility to use the key to ensure that the agreed data for linkage is pseudonymised. These individuals are contractually bound to adhere to organisational policies and procedures for safe management of the data.

South Warwickshire GP Federation will not receive any record level output from the linked data; only aggregate with small number suppression

DSfC - NHS South Warwickshire CCG; IV — DARS-NIC-82404-V2S5B

Type of data: information not disclosed for TRE projects

Opt outs honoured: Yes - patient objections upheld, No - DSfC for Invoice Validation Purposes, Identifiable (Section 251, Does not include the flow of confidential data, Section 251 NHS Act 2006)

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

Purposes: No (Clinical Commissioning Group (CCG), Sub ICB Location)

Sensitive: Sensitive

When:DSA runs 2019-06-08 — 2022-06-07 2018.06 — 2021.03.

Access method: Frequent adhoc flow, Frequent Adhoc Flow, One-Off

Data-controller type: NHS COVENTRY AND WARWICKSHIRE CCG, NHS COVENTRY AND WARWICKSHIRE ICB - B2M3M

Sublicensing allowed: No

Datasets:

SUS for Commissioners

Objectives:

Invoice Validation

Invoice validation is part of a process by which providers of care or services get paid for the work they do.

Invoices are submitted to the Clinical Commissioning Group (CCG) so they are able to ensure that the activity claimed for each patient is their responsibility. This is done by processing and analysing Secondary User Services (SUS+) data, which is received into a secure Controlled Environment for Finance (CEfF). The SUS+ data is identifiable at the level of NHS number. The NHS number is only used to confirm the accuracy of backing-data sets and will not be used further.

The legal basis for this to occur is under Section 251 of NHS Act 2006.

Invoice Validation with be conducted by Arden and GEM CSU.
The CCG are advised by Arden and GEM CSU whether payment for invoices can be made or not.

Risk Stratification

Risk stratification is a tool for identifying and predicting which patients are at high risk or are likely to be at high risk and prioritising the management of their care in order to prevent worse outcomes.

To conduct risk stratification Secondary User Services (SUS+) data, identifiable at the level of NHS number is linked with Primary Care data (from GPs) and an algorithm is applied to produce risk scores. Risk Stratification provides focus for future demands by enabling commissioners to prepare plans for patients. Commissioners can then prepare plans for patients who may require high levels of care. Risk Stratification also enables General Practitioners (GPs) to better target intervention in Primary Care.

The legal basis for this to occur is under Section 251 of NHS Act 2006 (CAG 7-04(a)).

Risk Stratification will be conducted by Arden and GEM CSU.

Yielded Benefits:

.

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

Risk Stratification
Risk stratification promotes improved case management in primary care and will lead to the following benefits being realised:
1. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these.
2. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services thus allowing early intervention.
3. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required.
4. Supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework by allowing for more targeted intervention in primary care.
5. Better understanding of local population characteristics through analysis of their health and healthcare outcomes
All of the above lead to improved patient experience through more effective commissioning of services.

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

Risk Stratification
1. As part of the risk stratification processing activity detailed above, GPs have access to the risk stratification tool which highlights patients for whom the GP is responsible and have been classed as at risk. The only identifier available to GPs is the NHS numbers of their own patients. Any further identification of the patients will be completed by the GP on their own systems.
2. Output from the risk stratification tool will provide aggregate reporting of number and percentage of population found to be at risk.
3. Record level output will be available for commissioners (of the CCG), pseudonymised at patient level.
4. GP Practices will be able to view the risk scores for individual patients with the ability to display the underlying SUS+ data for the individual patients when it is required for direct care purposes by someone who has a legitimate relationship with the patient.
5. The CCG will be able to target specific patient groups and enable clinicians with the duty of care for the patient to offer appropriate interventions. The CCG will also be able to:
o Stratify populations based on: disease profiles; conditions currently being treated; current service use; pharmacy use and risk of future overall cost
o Plan work for commissioning services and contracts
o Set up capitated budgets
o Identify health determinants of risk of admission to hospital, or other adverse care outcomes.

Processing:

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

Patient level data will not be shared outside of the CCG unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.

All access to data is managed under Roles-Based Access Controls.

No patient level data will be linked other than as specifically detailed within this 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 and that data required by the applicant.

NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract ie: employees, agents and contractors of the Data Recipient who may have access to that data)

Data for the purpose of Invoice Validation is kept within the CEfF, and only used by staff properly trained and authorised for the activity. Only CEfF staff are able to access data in the CEfF and only CEfF staff operate the invoice validation process within the CEfF. Data flows directly in to the CEfF from the DSCRO and from the providers – it does not flow through any other processors.

Invoice Validation
1. Identifiable SUS+ Data is obtained from the SUS+ Repository to the Data Services for Commissioners Regional Office (DSCRO).
2. The DSCRO pushes a one-way data flow of SUS+ data into the Controlled Environment for Finance (CEfF) in the Arden and GEM CSU.
3. The CSU carry out the following processing activities within the CEfF for invoice validation purposes:
a. Validating that the Clinical Commissioning Group is responsible for payment for the care of the individual by using SUS+ and/or backing flow data.
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 Arden and GEM 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.

Risk Stratification
1. Identifiable SUS+ data is obtained from the SUS Repository to the Data Services for Commissioners Regional Office (DSCRO).
2. Data quality management and standardisation of data is completed by the DSCRO and the data identifiable at the level of NHS number is transferred securely to Arden and GEM CSU, who hold the SUS+ data within the secure Data Centre on N3.
3. Identifiable GP Data is securely sent from the GP system to Arden and GEM CSU.
4. SUS+ data is linked to GP data in the risk stratification tool by the data processor.
5. As part of the risk stratification processing activity, GPs have access to the risk stratification tool within the data processor, which highlights patients with whom the GP has a legitimate relationship and have been classed as at risk. The only identifier available to GPs is the NHS numbers of their own patients. Any further identification of the patients will be completed by the GP on their own systems.
6. Once Arden and GEM CSU has completed the processing, the CCG can access the online system via a secure connection to access the data pseudonymised at patient level.

GDPPR COVID-19 CCG - Pseudo — DARS-NIC-390198-L6W9C

Type of data: information not disclosed for TRE projects

Opt outs honoured: No - Statutory exemption to flow confidential data without consent, Anonymised - ICO Code Compliant (Statutory exemption to flow confidential data without consent)

Legal basis: CV19: Regulation 3 (4) of the Health Service (Control of Patient Information) Regulations 2002, CV19: Regulation 3 (4) of the Health Service (Control of Patient Information) Regulations 2002; Health and Social Care Act 2012 - s261(5)(d)

Purposes: No (Clinical Commissioning Group (CCG), Sub ICB Location)

Sensitive: Sensitive

When:DSA runs 2020-09-01 — 2021-03-31 2021.01 — 2021.02.

Access method: One-Off, Frequent Adhoc Flow

Data-controller type: NHS COVENTRY AND WARWICKSHIRE CCG, NHS COVENTRY AND WARWICKSHIRE ICB - B2M3M

Sublicensing allowed: No

Datasets:

GPES Data for Pandemic Planning and Research (COVID-19)
COVID-19 General Practice Extraction Service (GPES) Data for Pandemic Planning and Research (GDPPR)

Objectives:

NHS Digital has been provided with the necessary powers to support the Secretary of State’s response to COVID-19 under the COVID-19 Public Health Directions 2020 (COVID-19 Directions) and support various COVID-19 purposes, the data shared under this agreement can be used for these specified purposes except where they would require the reidentification of individuals.

GPES data for pandemic planning and research (GDPPR COVID 19)
To support the response to the outbreak, NHS Digital has been legally directed to collect and analyse healthcare information about patients from their GP record for the duration of the COVID-19 emergency period under the COVID-19 Directions.
The data which NHS Digital has collected and is providing under this agreement includes coded health data, which is held in a patient’s GP record, such as details of:
• diagnoses and findings
• medications and other prescribed items
• investigations, tests and results
• treatments and outcomes
• vaccinations and immunisations

Details of any sensitive SNOMED codes included in the GDPPR data set can be found in the Reference Data and GDPPR COVID 19 user guides hosted on the NHS Digital website. SNOMED codes are included in GDPPR data.
There are no free text record entries in the data.

The Controller will use the pseudonymised GDPPR COVID 19 data to provide intelligence to support their local response to the COVID-19 emergency. The data is analysed so that health care provision can be planned to support the needs of the population within the CCG area for the COVID-19 purposes.

Such uses of the data include but are not limited to:

• Analysis of missed appointments - Analysis of local missed/delayed referrals due to the COVID-19 crisis to estimate the potential impact and to estimate when ‘normal’ health and care services may resume, linked to Paragraph 2.2.3 of the COVID-19 Directions.

• Patient risk stratification and predictive modelling - to highlight patients at risk of requiring hospital admission due to COVID-19, computed using algorithms executed against linked de-identified data, and identification of future service delivery models linked to Paragraph 2.2.2 of the COVID-19 Directions. As with all risk stratification, this would lead to the identification of the characteristics of a cohort that could subsequently, and separately, be used to identify individuals for intervention. However the identification of individuals will not be done as part of this data sharing agreement, and the data shared under this agreement will not be reidentified.

• Resource Allocation - In order to assess system wide impact of COVID-19, the GDPPR COVID 19 data will allow reallocation of resources to the worst hit localities using their expertise in scenario planning, clinical impact and assessment of workforce needs, linked to Paragraph 2.2.4 of the COVID-19 Directions:

The data may only be linked by the Data Controller or their respective Data Processor, to other pseudonymised datasets which it holds under a current data sharing agreement only where such data is provided for the purposes of general commissioning by NHS Digital. The Health Service Control of Patient Information Regulations (COPI) will also apply to any data linked to the GDPPR data.
The linked data may only be used for purposes stipulated within this agreement and may only be held and used whilst both data sharing agreements are live and in date. Using the linked data for any other purposes, including non-COVID-19 purposes would be considered a breach of this agreement. Reidentification of individuals is not permitted under this DSA.

LEGAL BASIS FOR PROCESSING DATA:
Legal Basis for NHS Digital to Disseminate the Data:
NHS Digital is able to disseminate data with the Recipients for the agreed purposes under a notice issued to NHS Digital by the Secretary of State for Health and Social Care under Regulation 3(4) of the Health Service Control of Patient Information Regulations (COPI) dated 17 March 2020 (the NHSD COPI Notice).
The Recipients are health organisations covered by Regulation 3(3) of COPI and the agreed purposes (paragraphs 2.2.2-2.2.4 of the COVID-19 Directions, as stated below in section 5a) for which the disseminated data is being shared are covered by Regulation 3(1) of COPI.

Under the Health and Social Care Act, NHS Digital is relying on section 261(5)(d) – necessary or expedient to share the disseminated data with the Recipients for the agreed purposes.

Legal Basis for Processing:
The Recipients are able to receive and process the disseminated data under a notice issued to the Recipients by the Secretary of State for Health and Social Care under Regulation 3(4) of COPI dated 20th March (the Recipient COPI Notice section 2).

The Secretary of State has issued notices under the Health Service Control of Patient Information Regulations 2002 requiring the following organisations to process information:

Health organisations

“Health Organisations” defined below under Regulation 3(3) of COPI includes CCGs for the reasons explained below. These are clinically led statutory NHS bodies responsible for the planning and commissioning of health care services for their local area

The Secretary of State for Health and Social Care has issued NHS Digital with a Notice under Regulation 3(4) of the National Health Service (Control of Patient Information Regulations) 2002 (COPI) to require NHS Digital to share confidential patient information with organisations permitted to process confidential information under Regulation 3(3) of COPI. These include:

• persons employed or engaged for the purposes of the health service

Under Section 26 of the Health and Social Care Act 2012, CCG’s have a duty to provide and manage health services for the population.

Regulation 7 of COPI includes certain limitations. The request has considered these limitations, considering data minimisation, access controls and technical and organisational measures.

Under GDPR, the Recipients can rely on Article 6(1)(c) – Legal Obligation to receive and process the Disclosed Data from NHS Digital for the Agreed Purposes under the Recipient COPI Notice. As this is health information and therefore special category personal data the Recipients can also rely on Article 9(2)(h) – preventative or occupational medicine and para 6 of Schedule 1 DPA – statutory purpose.

Expected Benefits:

• Manage demand and capacity
• Reallocation of resources
• Bring in additional workforce support
• Assists commissioners to make better decisions to support patients
• Identifying COVID-19 trends and risks to public health
• Enables CCGs to provide guidance and develop policies to respond to the outbreak
• Controlling and helping to prevent the spread of the virus

Outputs:

• Operational planning to predict likely demand on primary, community and acute service for vulnerable patients due to the impact of COVID-19
• Analysis of resource allocation
• Investigating and monitoring the effects of COVID-19
• Patient Stratification in relation to COVID-19, such as:
o Patients at highest risk of admission
o Frail and elderly
o Patients that are currently in hospital
o Patients with prescriptions related to COVID-19
o Patients recently Discharged from hospital
For avoidance of doubt these are pseudonymised patient cohorts, not identifiable.

Processing:

PROCESSING CONDITIONS:
Data must only be used for the purposes stipulated within this Data Sharing Agreement. Any additional disclosure / publication will require further approval from NHS Digital.

Data Processors must only act upon specific instructions from the Data Controller.

All access to data is managed under Role-Based Access Controls. Users can only access data authorised by their role and the tasks that they are required to undertake.

Patient level data will not be linked other than as specifically detailed within this Data Sharing Agreement.

NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract i.e.: employees, agents and contractors of the Data Recipient who may have access to that data).

The Recipients will take all required security measures to protect the disseminated data and they will not generate copies of their cuts of the disseminated data unless this is strictly necessary. Where this is necessary, the Recipients will keep a log of all copies of the disseminated data and who is controlling them and ensure these are updated and destroyed securely.

Onward sharing of patient level data is not permitted under this agreement. Only aggregated reports with small number suppression can be shared externally.

The data disseminated will only be used for COVID-19 GDPPR purposes as described in this DSA, any other purpose is excluded.

SEGREGATION:
Where the Data Processor and/or the Data Controller hold both identifiable and pseudonymised data, the data will be held separately so data cannot be linked.

AUDIT
All access to data is auditable by NHS Digital in accordance with the Data Sharing Framework Contract and NHS Digital terms.
Under the Local Audit and Accountability Act 2014, section 35, Secretary of State has power to audit all data that has flowed, including under COPI.

DATA MINIMISATION:
Data Minimisation in relation to the data sets listed within the application are listed below:

• Patients who are normally registered and/or resident within the CCG region (including historical activity where the patient was previously registered or resident in another commissioner area).
and/or
• Patients treated by a provider where the CCG is the host/co-ordinating commissioner and/or has the primary responsibility for the provider services in the local health economy.
and/or
• Activity identified by the provider and recorded as such within national systems (such as SUS+) as for the attention of the CCG.

The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
- GDPPR COVID 19 Data
Pseudonymisation is completed within the DSCRO and is then disseminated as follows:
1. Pseudonymised GDPPR COVID 19 data is securely transferred from the DSCRO to the Data Controller / Processor
2. Aggregation of required data will be completed by the Controller (or the Processor as instructed by the Controller).
3. Patient level data may not be shared by the Controller (or any of its processors).

Project 4 — DARS-NIC-147943-C4Q5L

Type of data: information not disclosed for TRE projects

Opt outs honoured: No - data flow is not identifiable (Does not include the flow of confidential data)

Legal basis: Health and Social Care Act 2012 – s261(1) and s261(2)(b)(ii)

Purposes: ()

Sensitive: Sensitive

When:2018.06 — 2019.04.

Access method: Frequent adhoc flow, Frequent Adhoc Flow

Data-controller type:

Sublicensing allowed:

Datasets:

Acute-Local Provider Flows
Ambulance-Local Provider Flows
Community Services Data Set
Community-Local Provider Flows
Demand for Service-Local Provider Flows
Diagnostic Services-Local Provider Flows
Emergency Care-Local Provider Flows
Experience, Quality and Outcomes-Local Provider Flows
Mental Health-Local Provider Flows
National Cancer Waiting Times Monitoring DataSet (CWT)
Other Not Elsewhere Classified (NEC)-Local Provider Flows
Population Data-Local Provider Flows
Primary Care Services-Local Provider Flows
Public Health and Screening Services-Local Provider Flows
SUS for Commissioners

Objectives:

Commissioning
To use pseudonymised data to provide intelligence to support the commissioning of health services. The data (containing both clinical and financial information) is analysed so that health care provision can be planned to support the needs of the population within the CCG area.
The CCG commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.
The following pseudonymised datasets are required to provide intelligence to support commissioning of health services:
- Secondary Uses Service (SUS)
- Local Provider Flows
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
The pseudonymised data is required to for the following purposes:
§ Population health management:
• Understanding the interdependency of care services
• Targeting care more effectively
• Using value as the redesign principle
• Ensuring we do what we should
§ Data Quality and Validation – allowing data quality checks on the submitted data
§ Thoroughly investigating the needs of the population, to ensure the right services are available for individuals when and where they need them
§ Understanding cohorts of residents who are at risk of becoming users of some of the more expensive services, to better understand and manage those needs
§ Monitoring population health and care interactions to understand where people may slip through the net, or where the provision of care may be being duplicated
§ Modelling activity across all data sets to understand how services interact with each other, and to understand how changes in one service may affect flows through another
§ Service redesign
§ Health Needs Assessment – identification of underlying disease prevalence within the local population
§ Patient stratification and predictive modelling - to identify specific patients at risk of requiring hospital admission and other avoidable factors such as risk of falls, computed using algorithms executed against linked de-identified data, and identification of future service delivery models

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.
Processing for commissioning will be conducted by NHS Midlands and Lancashire Commissioning Support Unit (CSU)

Yielded Benefits:

Any future application for extension or renewal beyond 31/05/2019 should include detail of any outputs produced or benefits achieved through use of DSfC Data

Expected Benefits:

Commissioning
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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC).
4. Commissioning cycle support for grouping and re-costing previous activity.
5. Enables monitoring of:
a. CCG outcome indicators.
b. Financial and 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.
7. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these.
8. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services and early intervention of appropriate care.
9. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required.
10. Potentially reduced premature mortality by more targeted intervention in primary care, which supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework.
11. Better understanding of the health of and the variations in health outcomes within the population to help understand local population characteristics.
12. Better understanding of contract requirements, contract execution, and required services for management of existing contracts, and to assist with identification and planning of future contracts
13. Insights into patient outcomes, and identification of the possible efficacy of outcomes-based contracting opportunities.

Outputs:

Commissioning
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 acute / community / 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.
9. Comparators of CCG performance with similar CCGs as set out by a specific range of care quality and performance measures detailed activity and cost reports
10. Data Quality and Validation measures allowing data quality checks on the submitted data
11. Contract Management and Modelling
12. Patient Stratification, such as:
o Patients at highest risk of admission
o Most expensive patients (top 15%)
o Frail and elderly
o Patients that are currently in hospital
o Patients with most referrals to secondary care
o Patients with most emergency activity
o Patients with most expensive prescriptions
o Patients recently moving from one care setting to another
i. Discharged from hospital
ii. Discharged from community

Processing:

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

All access to data is managed under Roles-Based Access Controls

No patient level data will be linked other than as specifically detailed within this 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 and that data required by the applicant.

NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract ie: employees, agents and contractors of the Data Recipient who may have access to that data)

Segregation
Where the Data Processor and/or the Data Controller hold both identifiable and pseudonymised data, the data will be held separately so data cannot be linked.
All access to data is auditable by NHS Digital.
Commissioning
The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
1. SUS
2. Local Provider Flows (received directly from providers)
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
Data quality management and pseudonymisation is completed within the DSCRO and is then disseminated as follows:
Data Processor 1 – NHS Midlands and Lancashire Commissioning Support Unit (CSU)
1) Pseudonymised SUS and Local Provider data only is securely transferred from the DSCRO to NHS Midlands and Lancashire Commissioning Support Unit.
2) NHS Midlands and Lancashire Commissioning Support Unit add derived fields, link data and provide analysis to:
o See patient journeys for pathways or service design, re-design and de-commissioning
o Check recorded activity against contracts or invoices and facilitate discussions with providers
o Undertake population health management
o Undertake data quality and validation checks
o Thoroughly investigate the needs of the population
o Understand cohorts of residents who are at risk
o Conduct Health Needs Assessments
3) Allowed linkage is between the data sets contained within point 1.
4) NHS Midlands and Lancashire Commissioning Support Unit then pass the processed, pseudonymised and linked data to the CCG. The CCG analyse the data to:
5) Aggregation of required data for CCG management use will be completed by NHS Midlands and Lancashire Commissioning Support Unit 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.

Project 5 — DARS-NIC-120057-H3L3B

Type of data: information not disclosed for TRE projects

Opt outs honoured: No - data flow is not identifiable (Does not include the flow of confidential data)

Legal basis: Health and Social Care Act 2012 – s261(1) and s261(2)(b)(ii)

Purposes: ()

Sensitive: Sensitive

When:2018.06 — 2019.04.

Access method: Frequent adhoc flow, Frequent Adhoc Flow

Data-controller type:

Sublicensing allowed:

Datasets:

Acute-Local Provider Flows
Ambulance-Local Provider Flows
Children and Young People Health
Community-Local Provider Flows
Demand for Service-Local Provider Flows
Diagnostic Imaging Dataset
Diagnostic Services-Local Provider Flows
Emergency Care-Local Provider Flows
Experience, Quality and Outcomes-Local Provider Flows
Improving Access to Psychological Therapies Data Set
Maternity Services Data Set
Mental Health and Learning Disabilities Data Set
Mental Health Minimum Data Set
Mental Health Services Data Set
Mental Health-Local Provider Flows
Other Not Elsewhere Classified (NEC)-Local Provider Flows
Population Data-Local Provider Flows
Primary Care Services-Local Provider Flows
Public Health and Screening Services-Local Provider Flows
SUS for Commissioners

Objectives:

To use pseudonymised data to provide intelligence to support the commissioning of health services. The data (containing both clinical and financial information) is analysed so that health care provision can be planned to support the needs of the population within the CCG area.

The CCGs commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.

The following pseudonymised datasets are required to provide intelligence to support commissioning of health services:
- Secondary Uses Service (SUS+)
- Local Provider Flows
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
- 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 for the following purposes:
§ Population health management:
• Understanding the interdependency of care services
• Targeting care more effectively
• Using value as the redesign principle
§ Data Quality and Validation – allowing data quality checks on the submitted data
§ Thoroughly investigating the needs of the population, to ensure the right services are available for individuals when and where they need them
§ Understanding cohorts of residents who are at risk of becoming users of some of the more expensive services, to better understand and manage those needs
§ Monitoring population health and care interactions to understand where people may slip through the net, or where the provision of care may be being duplicated
§ Modelling activity across all data sets to understand how services interact with each other, and to understand how changes in one service may affect flows through another
§ Service redesign
§ Health Needs Assessment – identification of underlying disease prevalence within the local population
§ Patient stratification and predictive modelling - to identify specific patients at risk of requiring hospital admission and other avoidable factors such as risk of falls, computed using algorithms executed against linked de-identified data, and identification of future service delivery models

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.

Processing for commissioning will be conducted by Arden and GEM CSU.

*****The following CCGs are able to share record level data between the CCGs to enable collaborative reporting by their respective CCG analysts and Data Processor Analysts (Arden and GEM CSU):
- NHS South Warwickshire CCG
- NHS Coventry and Rugby CCG
- NHS Warwickshire North CCG
The CCGs work together on a collaborative basis across to support each other in delivering their commissioning agendas. For example, they wish to carry out contract monitoring, e.g. SUS SLAM (Service Level Agreement Monitoring) reconciliation, for all the CCGs in their group where they are lead commissioner; or where a CCG provides a contract monitoring service for another CCG. The CCGs request approval (through this DARS amendment) to share the following datasets on a collaborative basis across their group, to be used for collaborative reporting in any combination of CCGs in the group, or at individual CCG level reporting as required; both by a CCG’s in house BI/Contract Analysts and by their Data Processor Analysts, Arden and GEM CSU:
• SUS and Local Provider Flows (for commissioning)
• Mental Health
• Maternity Services
• IAPT
• CYPHS
• DIDS

The 3 CCGs may access the pseudonymised data of each CCG for the purpose of commissioning only. The data listed in Annex A of the DSA is the data that the CCGs will be allowed to access.******

Expected Benefits:

Commissioning
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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC).
4. Commissioning cycle support for grouping and re-costing previous activity.
5. Enables monitoring of:
a. CCG outcome indicators.
b. Financial and 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.
7. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these.
8. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services and early intervention of appropriate care.
9. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required.
10. Potentially reduced premature mortality by more targeted intervention in primary care, which supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework.
11. Better understanding of the health of and the variations in health outcomes within the population to help understand local population characteristics.
12. Better understanding of contract requirements, contract execution, and required services for management of existing contracts, and to assist with identification and planning of future contracts
13. Insights into patient outcomes, and identification of the possible efficacy of outcomes-based contracting opportunities.

*****Further expected benefits include :
- a reduction in duplication,
- a reduction in misinterpretation,
- less analytical resource being used on an already complex area
- Joining together aggregate reports will give a full picture in relation to contracts regarding the Sustainability Transformation Plan boundary.******

Outputs:

Commissioning
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 acute / community / 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.
9. Comparators of CCG performance with similar CCGs as set out by a specific range of care quality and performance measures detailed activity and cost reports
10. Data Quality and Validation measures allowing data quality checks on the submitted data
11. Contract Management and Modelling
12. Patient Stratification, such as:
o Patients at highest risk of admission
o Most expensive patients (top 15%)
o Frail and elderly
o Patients that are currently in hospital
o Patients with most referrals to secondary care
o Patients with most emergency activity
o Patients with most expensive prescriptions
o Patients recently moving from one care setting to another
i. Discharged from hospital
ii. Discharged from community

****Further expected outputs as a result of sharing data between the CCGs include: provider level contract monitoring for activity and finance reports; whole system analysis; and monitoring as a result of collaborative commissioning and contracting. Opportunity identification, baselining, analysis and monitoring related to STP plans and delivery interventions would also need to be completed based on a collaborative footprint and therefore shared data repositories are fundamental to this.******

Processing:

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

The Data Controller and any Data Processor will only have access to records of patients of residence and registration within the CCG.

Patient level data will not be shared outside of the CCG unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.

All access to data is managed under Roles-Based Access Controls.
No patient level data will be linked other than as specifically detailed within this 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 and that data required by the applicant.

NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract ie: employees, agents and contractors of the Data Recipient who may have access to that data).

All access to data is auditable by NHS Digital.

Commissioning
The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
1. SUS+
2. Local Provider Flows (received directly from providers)
a. Acute
b. Ambulance
c. Community
d. Demand for Service
e. Diagnostic Service
f. Emergency Care
g. Experience, Quality and Outcomes
h. Mental Health
i. Other Not Elsewhere Classified
j. Population Data
k. Primary Care Services
l. Public Health Screening
3. Mental Health Minimum Data Set (MHMDS)
4. Mental Health Learning Disability Data Set (MHLDDS)
5. Mental Health Services Data Set (MHSDS)
6. Maternity Services Data Set (MSDS)
7. Improving Access to Psychological Therapy (IAPT)
8. Child and Young People Health Service (CYPHS)
9. Diagnostic Imaging Data Set (DIDS)

Data quality management and pseudonymisation is completed within the DSCRO and is then disseminated as follows:
Data Processor 1 – Midlands and Lancashire CSU
1. Pseudonymised SUS+, Local Provider data, Mental Health data (MHSDS, MHMDS, MHLDDS), Maternity data (MSDS), Improving Access to Psychological Therapies data (IAPT), Child and Young People’s Health data (CYPHS). Diagnostic Imaging data (DIDS) only is securely transferred from the DSCRO to Midlands and Lancashire CSU.
2. Midlands and Lancashire CSU add derived fields, link data and provide analysis to:
a. See patient journeys for pathways or service design, re-design and de-commissioning.
b. Check recorded activity against contracts or invoices and facilitate discussions with providers.
c. Undertake population health management
d. Undertake data quality and validation checks
e. Thoroughly investigate the needs of the population
f. Understand cohorts of residents who are at risk
g. Conduct Health Needs Assessments
3. Allowed linkage is between the data sets contained within point 1.
4. Midlands and Lancashire CSU then pass the processed, pseudonymised and linked data to the CCG.
5. Aggregation of required data for CCG management use will be completed by Midlands and Lancashire 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 as set out within NHS Digital guidance applicable to each data set.

Project 6 — NIC-82404-V2S5B

Type of data: information not disclosed for TRE projects

Opt outs honoured: N ()

Legal basis: Health and Social Care Act 2012

Purposes: ()

Sensitive: Sensitive

When:2018.03 — 2018.05.

Access method: Ongoing

Data-controller type:

Sublicensing allowed:

Datasets:

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
Mental Health Services Data Set
Mental Health Minimum Data Set
Mental Health and Learning Disabilities Data Set
Maternity Services Data Set
Improving Access to Psychological Therapies 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

Objectives:

Commissioning
To use pseudonymised data to provide intelligence to support commissioning of health services. 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.
The CCGs commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.
The following pseudonymised datasets are required to provide intelligence to support commissioning of health services:
- Secondary Uses Service (SUS)
- Local Provider Flows
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
- 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.
Processing for commissioning will be conducted by Arden and Greater East Midlands (AGEM) Commissioning Support Unit

The following CCGs are able to share record level data between the CCGs to enable collaborative reporting by their respective CCG analysts and Data Processor Analysts (Arden and GEM CSU):
- NHS South Warwickshire CCG
- NHS Coventry and Rugby CCG
- NHS Warwickshire North CCG
The CCGs work together on a collaborative basis across to support each other in delivering their commissioning agendas. For example, they wish to carry out contract monitoring, e.g. SUS SLAM (Service Level Agreement Monitoring) reconciliation, for all the CCGs in their group where they are lead commissioner; or where a CCG provides a contract monitoring service for another CCG. The CCGs request approval (through this DARS amendment) to share the following datasets on a collaborative basis across their group, to be used for collaborative reporting in any combination of CCGs in the group, or at individual CCG level reporting as required; both by a CCG’s in house BI/Contract Analysts and by their Data Processor Analysts, Arden and GEM CSU:
• SUS and Local Provider Flows (for commissioning)
• Mental Health
• Maternity Services
• IAPT
• CYPHS
• DIDS

The 3 CCGs may access the pseudonymised data of each CCG for the purpose of commissioning only. The data listed in Annex A of the DSA is the data that the CCGs will be allowed to access.

Expected Benefits:

Commissioning
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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC).
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.

Further expected benefits include :
- a reduction in duplication,
- a reduction in misinterpretation,
- less analytical resource being used on an already complex area
- Joining together aggregate reports will give a full picture in relation to contracts regarding the Sustainability Transformation Plan boundary.

Outputs:

Commissioning
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 acute / community / 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.
Further expected outputs as a result of sharing data between the CCGs include: provider level contract monitoring for activity and finance reports; whole system analysis; and monitoring as a result of collaborative commissioning and contracting. Opportunity identification, baselining, analysis and monitoring related to STP plans and delivery interventions would also need to be completed based on a collaborative footprint and therefore shared data repositories are fundamental to this.

Processing:

The CCGs listed within the agreement are Data Controllers in Common and as such have access to data from each CCG for the purposes listed within the agreement .

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

The Data Controller and any Data Processor will only have access to records of patients who are resident and registration within the CCG area. Access is limited to those substantive employees with authorised user accounts used for identification and authentication.

Patient level data will not be shared outside of the CCGs listed within the Data Sharing Agreement unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.

CCGs should work with general practices within their CCG to help them fulfil data controller responsibilities regarding flow of identifiable data into risk stratification tools.

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.

Commissioning
The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
1. SUS
2. Local Provider Flows (received directly from providers)
a. Acute
b. Ambulance
c. Community
d. Demand for Service
e. Diagnostic Service
f. Emergency Care
g. Experience, Quality and Outcomes
h. Mental Health
i. Other Not Elsewhere Classified
j. Population Data
k. Primary Care Services
l. Public Health Screening
3. Mental Health Minimum Data Set (MHMDS)
4. Mental Health Learning Disability Data Set (MHLDDS)
5. Mental Health Services Data Set (MHSDS)
6. Maternity Services Data Set (MSDS)
7. Improving Access to Psychological Therapy (IAPT)
8. Child and Young People Health Service (CYPHS)
9. Diagnostic Imaging Data Set (DIDS)
Data quality management and pseudonymisation is completed within the DSCRO and is then disseminated as follows:
Data Processor 1 – AGEM Commissioning Support Unit
1. Pseudonymised SUS, Local Provider data, Mental Health data (MHSDS, MHMDS, MHLDDS), Maternity data (MSDS), Improving Access to Psychological Therapies data (IAPT), Child and Young People’s Health data (CYPHS) and Diagnostic Imaging data (DIDS) only is securely transferred from the DSCRO to AGEM Commissioning Support Unit
2. AGEM Commissioning Support Unit add derived fields, link data and provide analysis.
3. Allowed linkage is between the data sets contained within point 1.
4. AGEM Commissioning Support Unit then pass the processed, pseudonymised and linked data to each CCG listed within the agreement. The CCG analyse the data to see patient journeys for pathways or service design, re-design and de-commissioning.
5. Aggregation of required data for CCG management use will be completed by AGEM Commissioning Support Unit 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.

Project 7 — NIC-120057-H3L3B

Type of data: information not disclosed for TRE projects

Opt outs honoured: N ()

Legal basis: Health and Social Care Act 2012

Purposes: ()

Sensitive: Sensitive

When:2017.12 — 2018.02.

Access method: Ongoing

Data-controller type:

Sublicensing allowed:

Datasets:

SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
Improving Access to Psychological Therapies Data Set
Mental Health Minimum 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 - Mental Health
Local Provider Data - Other not elsewhere classified

Objectives:

Objective for processing:
Commissioning
To use pseudonymised data to provide intelligence to support commissioning of health services. 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.
The CCGs commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.
The following pseudonymised datasets are required to provide intelligence to support commissioning of health services:
- Secondary Uses Service (SUS)
- Local Provider Flows
o Acute
o Ambulance
o Community
o Demand for Service
o Diagnostic Service
o Emergency Care
o Experience, Quality and Outcomes
o Mental Health
o Other Not Elsewhere Classified
o Population Data
o Primary Care Services
o Public Health Screening
- 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.
Processing for commissioning will be conducted by Arden and Greater East Midlands (AGEM) Commissioning Support Unit

The following CCGs are able to share record level data between the CCGs to enable collaborative reporting by their respective CCG analysts and Data Processor Analysts (Arden and GEM CSU):
- NHS South Warwickshire CCG
- NHS Coventry and Rugby CCG
- NHS Warwickshire North CCG
The CCGs work together on a collaborative basis across to support each other in delivering their commissioning agendas. For example, they wish to carry out contract monitoring, e.g. SUS SLAM (Service Level Agreement Monitoring) reconciliation, for all the CCGs in their group where they are lead commissioner; or where a CCG provides a contract monitoring service for another CCG. The CCGs request approval (through this DARS amendment) to share the following datasets on a collaborative basis across their group, to be used for collaborative reporting in any combination of CCGs in the group, or at individual CCG level reporting as required; both by a CCG’s in house BI/Contract Analysts and by their Data Processor Analysts, Arden and GEM CSU:
• SUS and Local Provider Flows (for commissioning)
• Mental Health
• Maternity Services
• IAPT
• CYPHS
• DIDS

The 3 CCGs may access the pseudonymised data of each CCG for the purpose of commissioning only. The data listed in Annex A of the DSA is the data that the CCGs will be allowed to access.

Expected Benefits:

Expected measurable benefits to health and/or social care including target date:
Commissioning
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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC).
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.

Further expected benefits include:
- a reduction in duplication,
- a reduction in misinterpretation,
- less analytical resource being used on an already complex area
- Joining together aggregate reports will give a full picture in relation to contracts regarding the Sustainability Transformation Plan boundary.

Outputs:

Specific outputs expected, including target date:
Commissioning
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 acute / community / 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.
Further expected outputs as a result of sharing data between the CCGs include: provider level contract monitoring for activity and finance reports; whole system analysis; and monitoring as a result of collaborative commissioning and contracting. Opportunity identification, baselining, analysis and monitoring related to STP plans and delivery interventions would also need to be completed based on a collaborative footprint and therefore shared data repositories are fundamental to this.

Processing:

Processing activities:
The CCGs listed within the agreement are Data Controllers in Common and as such have access to data from each CCG for the purposes listed within the agreement.

Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

The Data Controller and any Data Processor will only have access to records of patients who are resident and registration within the CCG area. Access is limited to those substantive employees with authorised user accounts used for identification and authentication.

Patient level data will not be shared outside of the CCGs listed within the Data Sharing Agreement unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.

CCGs should work with general practices within their CCG to help them fulfil data controller responsibilities regarding flow of identifiable data into risk stratification tools.

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.
Commissioning
The Data Services for Commissioners Regional Office (DSCRO) obtains the following data sets:
1. SUS
2. Local Provider Flows (received directly from providers)
a. Acute
b. Ambulance
c. Community
d. Demand for Service
e. Diagnostic Service
f. Emergency Care
g. Experience, Quality and Outcomes
h. Mental Health
i. Other Not Elsewhere Classified
j. Population Data
k. Primary Care Services
l. Public Health Screening
3. Mental Health Minimum Data Set (MHMDS)
4. Mental Health Learning Disability Data Set (MHLDDS)
5. Mental Health Services Data Set (MHSDS)
6. Maternity Services Data Set (MSDS)
7. Improving Access to Psychological Therapy (IAPT)
8. Child and Young People Health Service (CYPHS)
9. Diagnostic Imaging Data Set (DIDS)
Data quality management and pseudonymisation is completed within the DSCRO and is then disseminated as follows:
Data Processor 1 – AGEM Commissioning Support Unit
1. Pseudonymised SUS, Local Provider data, Mental Health data (MHSDS, MHMDS, MHLDDS), Maternity data (MSDS), Improving Access to Psychological Therapies data (IAPT), Child and Young People’s Health data (CYPHS) and Diagnostic Imaging data (DIDS) only is securely transferred from the DSCRO to AGEM Commissioning Support Unit
2. AGEM Commissioning Support Unit add derived fields, link data and provide analysis.
3. Allowed linkage is between the data sets contained within point 1.
4. AGEM Commissioning Support Unit then pass the processed, pseudonymised and linked data to each CCG listed within the agreement. The CCG analyse the data to see patient journeys for pathways or service design, re-design and de-commissioning.
5. Aggregation of required data for CCG management use will be completed by AGEM Commissioning Support Unit 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.

Project 8 — NIC-82404-V2S5B

Type of data: information not disclosed for TRE projects

Opt outs honoured: N, Y ()

Legal basis: Health and Social Care Act 2012, Section 251 approval is in place for the flow of identifiable data

Purposes: ()

Sensitive: Sensitive

When:2017.12 — 2018.02.

Access method: Ongoing

Data-controller type:

Sublicensing allowed:

Datasets:

SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
Improving Access to Psychological Therapies Data Set
Mental Health Minimum 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 - Mental Health
Local Provider Data - Other not elsewhere classified

Objectives:

Objective for processing:
This is an amended application for the following purposes:
Invoice Validation
As an approved Controlled Environment for Finance (CEfF), Arden and GEM CSU (Data Processor 1) 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.
In addition to the invoice validation undertaken via the CEfF, the CCG will undertake invoice validation using pseudonymised SUS and local flows of provider data, for example for high volume activity such as Any Qualified Provider (AQP). The pseudonymised NHS number will be used to confirm accuracy and where necessary the LPI will used to communicate with providers.
Identifiable and pseudonymised data will be kept separately and must not be linked.

Risk Stratification
To use SUS data identifiable at the level of NHS number according to S.251 CAG 7-04(a)/2013 (and Primary Care Data) for the purpose of Risk Stratification. Risk Stratification provides a forecast of future demand by identifying high risk patients. This enables commissioners to initiate proactive management plans for patients that are potentially high service users. Risk Stratification enables GPs to better target intervention in Primary Care

Expected Benefits:

Expected measurable benefits to health and/or social care including target date:
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

Risk Stratification
Risk stratification promotes improved case management in primary care and will lead to the following benefits being realised:
1. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these.
2. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services and early intervention of appropriate care.
3. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required.
4. Potentially reduced premature mortality by more targeted intervention in primary care, which supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework.
5. Better understanding of the health of and the variations in health outcomes within the population to help understand local population characteristics.
All of the above lead to improved patient experience through more effective commissioning of services.

Outputs:

Specific outputs expected, including target date:
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

Risk Stratification
1. As part of the risk stratification processing activity detailed above, GPs have access to the risk stratification tool which highlights patients for whom the GP is responsible and have been classed as at risk. The only identifier available to GPs is the NHS numbers of their own patients. Any further identification of the patients will be completed by the GP on their own systems.
2. Output from the risk stratification tool will provide aggregate reporting of number and percentage of population found to be at risk.
3. Record level output will be available for commissioners (of the CCG) aggregate with small number suppression
4. GP Practices will be able to view the risk scores for individual patients with the ability to display the underlying SUS data for the individual patients when it is required for direct care purposes by someone who has a legitimate relationship with the patient.
5. The CCG will be able to target specific patient groups and enable clinicians with the duty of care for the patient to offer appropriate interventions. The CCG will also be able to:
o Stratify populations based on: disease profiles; conditions currently being treated; current service use; pharmacy use and risk of future overall cost
o Plan work for commissioning services and contracts
o Set up capitated budgets
o Identify health determinants of risk of admission to hospital, or other adverse care outcomes.

Processing:

Processing activities:
Data must only be used as stipulated within this Data Sharing Agreement.

Data Processors must only act upon specific instructions from the Data Controller.

Data can only be stored at the addresses listed under storage addresses.

The Data Controller and any Data Processor will only have access to records of patients who are resident and registration within the CCG area. Access is limited to those substantive employees with authorised user accounts used for identification and authentication.

Patient level data will not be shared outside of the CCG unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.

CCGs should work with general practices within their CCG to help them fulfil data controller responsibilities regarding flow of identifiable data into risk stratification tools.

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.
The DSCRO (part of NHS Digital) will apply Type 2 objections before any identifiable data leaves the DSCRO.

Invoice Validation (Identifiable data)
1. Identifiable SUS Data is obtained from the SUS Repository to the Data Services for Commissioners Regional Office (DSCRO).
2. The DSCRO pushes a one-way data flow of SUS data into the Controlled Environment for Finance (CEfF) in the Arden and GEM 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 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

Invoice Validation (pseudonymised data)
1. Greater East Midlands Data Services for Commissioners Regional Office (GEM DSCRO) receives a flow of SUS identifiable data for the CCG from the SUS Repository and also receives identifiable local provider data for the CCG directly from Providers.
2. Data quality management and pseudonymisation of data is completed by the DSCRO and the pseudonymised data is then passed securely to Arden & GEM CSU for the addition of any derived fields.
3. Arden & GEM CSU then pass the processed, pseudonymised data to the CCG who conduct the following processing activities for invoice validation purposes:
a. Checking the registration of patients to the Clinical Commissioning Group (CCG) by using the derived commissioner field in SUS or within the local provider data flow
b. Validating activity and services against invoices and against local commissioning policies to ensure that invoices/payments:
i. are In line with Payment by Results tariff
ii. are in relation to a patient registered with the CCG GP or resident within the CCG area
iii. to ensure that there is no duplication of activity/charges
iv. that the health care provided should be paid by the CCG in line with CCG guidance.
4. The CCG will then establish that invoices have been validated and can be paid. Any discrepancies or non-validated invoices will be investigated and resolved using the LPI.

Risk Stratification (Arden and GEM CSU - Data Processor 1)
1. Identifiable SUS data is obtained from the SUS Repository to GEM Data Services for Commissioners Regional Office (DSCRO).
2. Data quality management and standardisation of data is completed by GEM DSCRO and the data identifiable at the level of NHS number is transferred securely to Arden and GEM CSU. who hold the SUS data within the secure Data Centre on N3.
3. Identifiable GP Data is securely sent from the GP system to Arden and GEM CSU.
4. SUS data is linked to GP data in the risk stratification tool by the data processor.
5. As part of the risk stratification processing activity, GPs have access to the risk stratification tool within the data processor, which highlights patients with whom the GP has a legitimate relationship and have been classed as at risk. The only identifier available to GPs is the NHS numbers of their own patients. Any further identification of the patients will be completed by the GP on their own systems.
6. Arden and GEM CSU who hosts the risk stratification system that holds SUS data is limited to those administrative staff with authorised user accounts used for identification and authentication.
7. Once Arden and GEM CSU has completed the processing, the CCG can access the online system via a secure N3 connection to access aggregate with small number suppression
8. The CCGs will produce collaborative commissioning risk stratification reports across their group of CCGs (as listed at the beginning of Section 5). (Note that this only relates to risk stratification for commissioning and will have no impact on risk stratification for case finding.)

Project 9 — NIC-47167-H3M4V

Type of data: information not disclosed for TRE projects

Opt outs honoured: N, Y ()

Legal basis: Health and Social Care Act 2012, Section 251 approval is in place for the flow of identifiable data

Purposes: ()

Sensitive: Sensitive

When:2017.06 — 2017.05.

Access method: Ongoing

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 - Public Health & Screening services
Local Provider Data - Mental Health
Local Provider Data - Other not elsewhere classified
Local Provider Data - Population Data
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
Maternity Services Dataset
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, Public Health & Screening services

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.

Risk Stratification
To use SUS data identifiable at the level of NHS number according to S.251 CAG 7-04(a) (and Primary Care Data) for the purpose of Risk Stratification. Risk Stratification provides a forecast of future demand by identifying high risk patients. This enables commissioners to initiate proactive management plans for patients that are potentially high service users. Risk Stratification enables GPs to better target intervention in Primary Care

Pseudonymised – SUS and Local Flows
To use pseudonymised data to provide intelligence to support commissioning of health services. 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.
The CCGs commission services from a range of providers covering a wide array of services. Each of the data flow categories requested supports the commissioned activity of one or more providers.

Pseudonymised – Mental Health, Maternity, IAPT, CYPHS and DIDS
To use pseudonymised data for the following datasets to provide intelligence to support commissioning of health services :
- 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 the HSCIC 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 misapproproation of public funds to ensure the on-going delivery of patient care

Risk Stratification
Risk stratification promotes improved case management in primary care and will lead to the following benefits being realised:
1. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these.
2. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services and early intervention of appropriate care.
3. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required.
4. Potentially reduced premature mortality by more targeted intervention in primary care, which supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework.
5. Better understanding of the health of and the variations in health outcomes within the population to help understand local population characteristics.
All of the above lead to improved patient experience through more effective commissioning of services.

Pseudonymised – SUS and Local Flows
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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC) flows.
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. .

Pseudonymised – 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 18 weeks wait 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.
d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC) flows.
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

Risk Stratification
1. As part of the risk stratification processing activity detailed above, GPs have access to the risk stratification tool which highlights patients for whom the GP is responsible and have been classed as at risk. The risk stratification presents pseudonymised data to the GPs. GPs are able to re-identify information only for their own patients for the purpose of direct care.
2. Output from the risk stratification tool will provide aggregate reporting of number and percentage of population found to be at risk.
3. Record level output will be available for commissioners pseudonymised at patient level and aggregated at patient level.
4. GP Practices will be able to view the risk scores for individual patients with the ability to display the underlying SUS data for the individual patients when it is required for direct care purposes by someone who has a legitimate relationship with the patient.

Pseudonymised – SUS and Local Flows
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 acute / community / 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.

Pseudonymised – Mental Health, Maternity, IAPT, CYPHS and DIDS
1. 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 acute / community / 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:

Prior to the release of identifiable data by North West DSCRO, Type 2 objections will be applied and the relevant patient’s data redacted.
Invoice Validation
1. SUS Data is sent from the SUS Repository to GEM DSCRO.
2. GEM DSCRO pushes a one-way data flow of SUS data into the Controlled Environment for Finance (CEfF) in the Arden & GEM 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 the HSCIC 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.

Risk Stratification
1. SUS Data is sent from the SUS Repository to GEM Data Services for Commissioners Regional Office (DSCRO) to the data processor.
2. SUS data identifiable at the level of NHS number regarding hospital admissions, A&E attendances and outpatient attendances is delivered securely from GEM DSCRO to the data processor.
3. Data quality management and standardisation of data is completed by GEM DSCRO and the data identifiable at the level of NHS number is transferred securely to Arden & GEM CSU), who hold the SUS data within the secure Data Centre on N3.
4. Identifiable GP Data is securely sent from the GP system to Arden & GEM CSU.
5. SUS data is linked to GP data in the risk stratification tool by the data processor.
6. As part of the risk stratification processing activity, GPs have access to the risk stratification tool within the data processor, which highlights patients with whom the GP has a legitimate relationship and have been classed as at risk. The risk stratification presents pseudonymised data to the GPs. GPs are able to re-identify information only for their own patients for the purpose of direct care.
7. Arden & GEM CSU who hosts the risk stratification system that holds SUS data is limited to those administrative staff with authorised user accounts used for identification and authentication.
8. Once Arden & GEMCSU has completed the processing, the CCG can access the online system via a secure N3 connection to access the data pseudonymised at patient level and aggregated reports.

Pseudonymised – SUS and Local Flows
Data Processor 1 – Arden & GEM CSU:
1. GEM Data Services for Commissioners Regional Office (DSCRO) receives a flow of SUS identifiable data for the CCG from the SUS Repository. GEM DSCRO also receives identifiable local provider data for the CCG directly from Providers.
2. Data quality management and pseudonymisation of data is completed by the DSCRO and the pseudonymised data is then passed securely to Arden & GEM CSU for the addition of derived fields, linkage of data sets and analysis.
3. Arden & GEM CSU then pass the processed, pseudonymised and linked data to the CCG who analyse the data to see patient journeys for pathways or service design, re-design and de-commissioning.
4. 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 in line with the HES analysis guide.

Data Processor 1 – South Warwickshire GP Limited:
• South Warwickshire CCG requires South Warwickshire GP Ltd to work on their pseudonymised SUS and local flows data, in the capacity of a data processor to the CCG.
• They will undertake analysis upon the request and instruction of the CCG.
• The CCG and South Warwickshire GP Ltd are fully aware that the SUS and local provider flows is only to be used for the purposes that will be stated in the Data Sharing Agreement to be issued soon between NHS Digital and the CCG. There will be no attempt to re-identify any of the data and no attempt to link it to any other data to which South Warwickshire GP Ltd may have access to, such as primary care data.

1. GEM Data Services for Commissioners Regional Office (DSCRO) receives a flow of SUS identifiable data for the CCG from the SUS Repository. GEM DSCRO also receives identifiable local provider data for the CCG directly from Providers.
2. Data quality management and pseudonymisation of data is completed by the DSCRO and the pseudonymised data is then passed securely to South Warwickshire GP Limited for the addition of derived fields, linkage of data sets and analysis.
3. South Warwickshire GP Limited then pass the processed, pseudonymised and linked data to the CCG who analyse the data to see patient journeys for pathways or service design, re-design and de-commissioning.
4. 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 in line with the HES analysis guide.
Pseudonymised – Mental Health, MSDS, IAPT, CYPHS and DIDS
1. GEM Data Services for Commissioners Regional Office (DSCRO) receives a flow of data identifiable at the level of NHS number for Mental Health (MHSDS, MHMDS, and MHLDDS) and Maternity (MSDS). GEM DSCRO also receive a flow of pseudonymised patient level data for each CCG for Improving Access to Psychological Therapies (IAPT), Child and Young People’s Health (CYPHS) and Diagnostic Imaging (DIDS) for commissioning purposes
2. Data quality management and pseudonymisation of data is completed by GEM DSCRO and the pseudonymised data is then passed securely to Arden & GEM CSU for the addition of derived fields, linkage of data sets and analysis.
3. Arden & GEM CSU then pass the processed, pseudonymised and linked data to the CCG who analyse the data to see patient journeys for pathways or service design, re-design and de-commissioning.
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 can be completed by the CSU or 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 in line with the HES analysis guide.

NHS Digital Data Release Register - reformatted

NHS South Warwickshire Ccg projects

DSfC - NHS South Warwickshire - Comm (GP federation) — DARS-NIC-168692-Y5S4C

DSfC - NHS South Warwickshire CCG; IV — DARS-NIC-82404-V2S5B

GDPPR COVID-19  CCG - Pseudo — DARS-NIC-390198-L6W9C

Project 4 — DARS-NIC-147943-C4Q5L

Project 5 — DARS-NIC-120057-H3L3B

Project 6 — NIC-82404-V2S5B

Project 7 — NIC-120057-H3L3B

Project 8 — NIC-82404-V2S5B

Project 9 — NIC-47167-H3M4V

GDPPR COVID-19 CCG - Pseudo — DARS-NIC-390198-L6W9C