NHS Digital Data Release Register - reformatted

NHS Warwickshire North Ccg projects

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


🚩 NHS Warwickshire North Ccg was sent multiple files from the same dataset, in the same month, both with optouts respected and with optouts ignored. NHS Warwickshire North 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 Warwickshire North CCG; IV — DARS-NIC-82396-W4F5T

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, 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(7); 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:

  1. 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 Stratitification
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
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.

Outputs:

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.

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).

All access to data is auditable by NHS Digital.

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 (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. 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 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.



Project 2 — DARS-NIC-120064-Z5S8S

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:

  1. Acute-Local Provider Flows
  2. Ambulance-Local Provider Flows
  3. Children and Young People Health
  4. Community Services Data Set
  5. Community-Local Provider Flows
  6. Demand for Service-Local Provider Flows
  7. Diagnostic Imaging Dataset
  8. Diagnostic Services-Local Provider Flows
  9. Emergency Care-Local Provider Flows
  10. Experience, Quality and Outcomes-Local Provider Flows
  11. Improving Access to Psychological Therapies Data Set
  12. Maternity Services Data Set
  13. Mental Health and Learning Disabilities Data Set
  14. Mental Health Minimum Data Set
  15. Mental Health Services Data Set
  16. Mental Health-Local Provider Flows
  17. National Cancer Waiting Times Monitoring DataSet (CWT)
  18. Other Not Elsewhere Classified (NEC)-Local Provider Flows
  19. Population Data-Local Provider Flows
  20. Primary Care Services-Local Provider Flows
  21. Public Health and Screening Services-Local Provider Flows
  22. 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 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)
- Community Services Data Set (CSDS)
- 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 NHS Arden and GEM CSU and NHS Midlands and Lancashire 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.

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 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)
10. Community Services Data Set (CSDS)
11. National Cancer Waiting Times Monitoring Data Set (CWT)

Data quality management and pseudonymisation is completed within the DSCRO and is then disseminated as follows:

Data Processor 1 – Arden and GEM 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), Community Services Data Set (CSDS) and National Cancer Waiting Times Monitoring Data Set (CWT) only is securely transferred from the DSCRO to Arden and GEM CSU.
2. Arden and GEM 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. Arden and GEM 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 Arden and GEM 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.

Data Processor 2 – 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 3 — NIC-120064-Z5S8S

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.05.

Access method: Ongoing

Data-controller type:

Sublicensing allowed:

Datasets:

  1. SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  2. Improving Access to Psychological Therapies Data Set
  3. Mental Health Minimum Data Set
  4. Local Provider Data - Acute
  5. Local Provider Data - Ambulance
  6. Local Provider Data - Community
  7. Local Provider Data - Demand for Service
  8. Local Provider Data - Diagnostic Services
  9. Local Provider Data - Emergency Care
  10. Local Provider Data - Mental Health
  11. Local Provider Data - Other not elsewhere classified
  12. SUS for Commissioners
  13. Public Health and Screening Services-Local Provider Flows
  14. Primary Care Services-Local Provider Flows
  15. Population Data-Local Provider Flows
  16. Other Not Elsewhere Classified (NEC)-Local Provider Flows
  17. Mental Health-Local Provider Flows
  18. Mental Health Services Data Set
  19. Mental Health and Learning Disabilities Data Set
  20. Maternity Services Data Set
  21. Experience, Quality and Outcomes-Local Provider Flows
  22. Emergency Care-Local Provider Flows
  23. Diagnostic Services-Local Provider Flows
  24. Diagnostic Imaging Dataset
  25. Demand for Service-Local Provider Flows
  26. Community-Local Provider Flows
  27. Children and Young People Health
  28. Ambulance-Local Provider Flows
  29. Acute-Local Provider Flows

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 4 — NIC-82396-W4F5T

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:

  1. SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  2. Improving Access to Psychological Therapies Data Set
  3. Mental Health Minimum Data Set
  4. Local Provider Data - Acute
  5. Local Provider Data - Ambulance
  6. Local Provider Data - Community
  7. Local Provider Data - Demand for Service
  8. Local Provider Data - Diagnostic Services
  9. Local Provider Data - Emergency Care
  10. Local Provider Data - Mental Health
  11. 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 5 — NIC-47164-S6N7Z

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:

  1. Children and Young People's Health Services Data Set
  2. Improving Access to Psychological Therapies Data Set
  3. Local Provider Data - Acute
  4. Local Provider Data - Ambulance
  5. Local Provider Data - Community
  6. Local Provider Data - Demand for Service
  7. Local Provider Data - Diagnostic Services
  8. Local Provider Data - Emergency Care
  9. Local Provider Data - Experience Quality and Outcomes
  10. Local Provider Data - Public Health & Screening services
  11. Local Provider Data - Mental Health
  12. Local Provider Data - Other not elsewhere classified
  13. Local Provider Data - Population Data
  14. Mental Health and Learning Disabilities Data Set
  15. Mental Health Minimum Data Set
  16. Mental Health Services Data Set
  17. SUS Accident & Emergency data
  18. SUS Admitted Patient Care data
  19. SUS Outpatient data
  20. SUS (Accident & Emergency, Inpatient and Outpatient data)
  21. 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 reports.
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. 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:

Greater East Midlands (GEM) DSCRO will apply Type 2 objections (from 1st October 2016 onwards) before any identifiable data leaves the DSCRO.
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 & GEM CSU 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
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. Aggregation of required data for CCG management use can be completed by the CSU or the CCG
5. 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.

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, 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.
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.