NHS Digital Data Release Register - reformatted

NHS Erewash Ccg

Project 1 — NIC-112258-C9G8J

Opt outs honoured: N

Sensitive: Sensitive

When: 2017/12 — 2018/05.

Repeats: Ongoing

Legal basis: Health and Social Care Act 2012

Categories: Anonymised - ICO code compliant

Datasets:

  • SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  • SUS for Commissioners
  • Public Health and Screening Services-Local Provider Flows
  • Primary Care Services-Local Provider Flows
  • Population Data-Local Provider Flows
  • Other Not Elsewhere Classified (NEC)-Local Provider Flows
  • Mental Health-Local Provider Flows
  • 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

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 reduction in duplication, reduction in misinterpretation, less analytical resource on an already complex area and most importantly one version of the truth with a level of granularity that is important for these activities. 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: 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) 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 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.

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 Erewash CCG - NHS Hardwick CCG - NHS North Derbyshire CCG - NHS Southern Derbyshire 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 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 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.


Project 2 — NIC-112265-G2X3M

Opt outs honoured: N, Y

Sensitive: Sensitive

When: 2017/12 — 2018/05.

Repeats: Ongoing

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

Categories: Anonymised - ICO code compliant, Identifiable

Datasets:

  • SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  • SUS for Commissioners

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 Pseudonymised – SUS and Local Flows (for Hardwick CCG and North Derbyshire CCG only) 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 agains 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. 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:

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 Pseudonymised – SUS and Local Flows (for Hardwick CCG and North Derbyshire CCG only) 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:

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 specified within the Data Minimisation Efforts within Annex A of the Data Sharing Agreement. 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. 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 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.  The CCG are notified that the invoice has been validated and can be paid. Any discrepancies or non-validated invoices are investigated and resolved between the CSU CEfF team and the provider meaning that no identifiable data needs to be sent to the CCG. The CCG only receives notification to pay and management reporting detailing the total quantum of invoices received pending, processed etc. Pseudonymised – SUS and Local Flows (for Hardwick CCG and North Derbyshire CCG only) 1. GEM Data Services for Commissioners Regional Office (DSCRO) obtains a flow of SUS identifiable data for the CCG from the SUS Repository. GEM DSCRO also obtains 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 Optum Health Solutions (UK) Ltd for the addition of derived fields, linkage of data sets and analysis. Allowed linkage is between SUS data sets and local flows. 3. Optum Health Solutions (UK) Ltd then pass the processed, pseudonymised and linked data to the CCG. The CCG 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 will be completed by the Optum Health Solutions (UK) Ltd or the CCG as instructed by 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 can be shared.

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. Pseudonymised – SUS and Local Flows (for Hardwick CCG and North Derbyshire CCG only) 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.


Project 3 — NIC-142633-S5G3Q

Opt outs honoured: N

Sensitive: Sensitive

When: 2017/12 — 2018/05.

Repeats: Ongoing

Legal basis: Health and Social Care Act 2012

Categories: Anonymised - ICO code compliant

Datasets:

  • SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  • Improving Access to Psychological Therapies Data Set
  • Maternity Services Dataset
  • Mental Health Services Data Set
  • Local Provider Data - Acute
  • Local Provider Data - Community
  • Local Provider Data - Demand for Service
  • Local Provider Data - Emergency Care
  • Local Provider Data - Mental Health
  • 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 Minimum Data Set
  • Mental Health and Learning Disabilities Data Set
  • Maternity Services Data Set
  • Experience, Quality and Outcomes-Local Provider Flows
  • Emergency Care-Local Provider Flows
  • Diagnostic Services-Local Provider Flows
  • Diagnostic Imaging Dataset
  • Demand for Service-Local Provider Flows
  • Community-Local Provider Flows
  • Children and Young People Health
  • Ambulance-Local Provider Flows
  • Acute-Local Provider Flows

Benefits:

Expected measurable benefits to health and/or social care including target date: 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 Insights into patient outcomes, and identification of the possible efficacy of outcomes-based contracting opportunities.Further expected benefits include reduction in duplication, reduction in misinterpretation, less analytical resource on an already complex area and most importantly one version of the truth with a level of granularity that is important for these activities. 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. 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:

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 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) 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 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 to: o See patient journeys for pathways or service design, re-design and de-commissioning (CSU or CCG). o Check recorded activity against contracts or invoices and facilitate discussions with providers (CSU or CCG). 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) 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. Data Processor 2 – North of England 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 North of England Commissioning Support Unit 7) North of England 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 (CSU or CCG). o Check recorded activity against contracts or invoices and facilitate discussions with providers (CSU or CCG). 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 8) Allowed linkage is between the data sets contained within point 1. 2) Allowed linkage is between the data sets contained within point 1. 3) North of England 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. 4) Aggregation of required data for CCG management use will be completed by North of England Commissioning Support Unit or the CCG as instructed by 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 can be shared.

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 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 services/interactions 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 Greater East Midlands (AGEM) Commissioning Support Unit and North of England 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 North of England CSU): - NHS Erewash CCG - NHS Hardwick CCG - NHS North Derbyshire CCG - NHS Southern Derbyshire 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 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 and North of England CSU: • SUS and Local Provider Flows (for commissioning) • Mental Health • Maternity Services • IAPT • CYPHS • DIDS The 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.


Project 4 — NIC-47086-Y2R7W

Opt outs honoured: N

Sensitive: Sensitive

When: 2016/12 — 2017/08.

Repeats: Ongoing

Legal basis: Health and Social Care Act 2012

Categories: Anonymised - ICO code compliant

Datasets:

  • 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
  • Mental Health Minimum Data Set
  • Mental Health and Learning Disabilities Data Set
  • Mental Health Services Data Set
  • Improving Access to Psychological Therapies Data Set
  • Children and Young People's Health Services 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
  • SUS Accident & Emergency data
  • SUS Admitted Patient Care data
  • SUS Outpatient data

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.

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.