NHS Digital Data Release Register - reformatted

NHS Enfield CCG

Project 1 — DARS-NIC-41640-G0C5N

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

Sensitive: Sensitive

When: 2018/10 — 2019/04.

Repeats: Frequent Adhoc Flow

Legal basis: Health and Social Care Act 2012 – s261(1) and s261(2)(b)(ii), National Health Service Act 2006 - s251 - 'Control of patient information'.

Categories: Anonymised - ICO code compliant, Identifiable

Datasets:

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

Objectives:

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. Invoice Validation with be conducted by North East London Commissioning Support Unit (NELCSU) The CCG are advised by North East London Commissioning Support Unit (NELCSU) whether payment for invoices can be made or not. 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) - Community Services Data Set (CSDS) - Diagnostic Imaging Data Set (DIDS) - National Cancer Waiting Times Monitoring Data Set (CWT) The pseudonymised data is required to for the following purposes:  Population health management: • Understanding the interdependency of care services • Targeting care more effectively • Using value as the redesign principle  Data Quality and Validation – allowing data quality checks on the submitted data  Thoroughly investigating the needs of the population, to ensure the right services are available for individuals when and where they need them  Understanding cohorts of residents who are at risk of becoming users of some of the more expensive services, to better understand and manage those needs  Monitoring population health and care interactions to understand where people may slip through the net, or where the provision of care may be being duplicated  Modelling activity across all data sets to understand how services interact with each other, and to understand how changes in one service may affect flows through another  Service redesign  Health Needs Assessment – identification of underlying disease prevalence within the local population  Patient stratification and predictive modelling - to identify specific patients at risk of requiring hospital admission and other avoidable factors such as risk of falls, computed using algorithms executed against linked de-identified data, and identification of future service delivery models The pseudonymised data is required to ensure that analysis of health care provision can be completed to support the needs of the health profile of the population within the CCG area based on the full analysis of multiple pseudonymised datasets. Processing for commissioning will be conducted by North East London Commissioning Support Unit (NELCSU)

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 Commissioning 1. Supporting Quality Innovation Productivity and Prevention (QIPP) to review demand management, integrated care and pathways. a. Analysis to support full business cases. b. Develop business models. c. Monitor In year projects. 2. Supporting Joint Strategic Needs Assessment (JSNA) for specific disease types. 3. Health economic modelling using: a. Analysis on provider performance against 18 weeks wait targets. b. Learning from and predicting likely patient pathways for certain conditions, in order to influence early interventions and other treatments for patients. c. Analysis of outcome measures for differential treatments, accounting for the full patient pathway. d. Analysis to understand emergency care and linking A&E and Emergency Urgent Care Flows (EUCC). 4. Commissioning cycle support for grouping and re-costing previous activity. 5. Enables monitoring of: a. CCG outcome indicators. b. Financial and Non-financial validation of activity. c. Successful delivery of integrated care within the CCG. d. Checking frequent or multiple attendances to improve early intervention and avoid admissions. e. Case management. f. Care service planning. g. Commissioning and performance management. h. List size verification by GP practices. i. Understanding the care of patients in nursing homes. 6. Feedback to NHS service providers on data quality at an aggregate and individual record level – only on data initially provided by the service providers. 7. Improved planning by better understanding patient flows through the healthcare system, thus allowing commissioners to design appropriate pathways to improve patient flow and allowing commissioners to identify priorities and identify plans to address these. 8. Improved quality of services through reduced emergency readmissions, especially avoidable emergency admissions. This is achieved through mapping of frequent users of emergency services and early intervention of appropriate care. 9. Improved access to services by identifying which services may be in demand but have poor access, and from this identify areas where improvement is required. 10. Potentially reduced premature mortality by more targeted intervention in primary care, which supports the commissioner to meets its requirement to reduce premature mortality in line with the CCG Outcome Framework. 11. Better understanding of the health of and the variations in health outcomes within the population to help understand local population characteristics. 12. Better understanding of contract requirements, contract execution, and required services for management of existing contracts, and to assist with identification and planning of future contracts 13. Insights into patient outcomes, and identification of the possible efficacy of outcomes-based contracting opportunities.

Outputs:

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 Commissioning 1. Commissioner reporting: a. Summary by provider view - plan & actuals year to date (YTD). b. Summary by Patient Outcome Data (POD) view - plan & actuals YTD. c. Summary by provider view - activity & finance variance by POD. d. Planned care by provider view - activity & finance plan & actuals YTD. e. Planned care by POD view - activity plan & actuals YTD. f. Provider reporting. g. Statutory returns. h. Statutory returns - monthly activity return. i. Statutory returns - quarterly activity return. j. Delayed discharges. k. Quality & performance referral to treatment reporting. 2. Readmissions analysis. 3. Production of aggregate reports for CCG Business Intelligence. 4. Production of project / programme level dashboards. 5. Monitoring of acute / community / mental health quality matrix. 6. Clinical coding reviews / audits. 7. Budget reporting down to individual GP Practice level. 8. GP Practice level dashboard reports include high flyers. 9. Comparators of CCG performance with similar CCGs as set out by a specific range of care quality and performance measures detailed activity and cost reports 10. Data Quality and Validation measures allowing data quality checks on the submitted data 11. Contract Management and Modelling 12. Patient Stratification, such as: o Patients at highest risk of admission o Most expensive patients (top 15%) o Frail and elderly o Patients that are currently in hospital o Patients with most referrals to secondary care o Patients with most emergency activity o Patients with most expensive prescriptions o Patients recently moving from one care setting to another i. Discharged from hospital ii. Discharged from community

Processing:

Data must only be used as stipulated within this Data Sharing Agreement. Data Processors must only act upon specific instructions from the Data Controller. Data can only be stored at the addresses listed under storage addresses. 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) 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. 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. 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. Data Minimisation • Patients treated by a provider where the commissioner is the host/co-ordinating commissioner and/or has the primary responsibility for the provider services in the local health economy – this is only for commissioning and relates to both national and local flows. and/or • Activity identified by the provider and recorded as such within national systems (such as SUS+) as for the attention of the commissioner - this is only for commissioning and relates to both national and local flows. For the purpose of Risk Stratification: • Patients who are normally registered and/or resident within the commissioner (including historical activity where the patient was previously registered or resident in another commissioner For the purpose of Invoice Validation: • CCG of residence and/or registration. The above relates to data requested only (Table 3B). Data currently held (Table 3A) will have the following Data Minimisation: • CCG of residence and/or registration. For clarity, any access by Interxion to data held under this agreement would be considered a breach of the agreement. This includes granting of access to the database[s] containing the data. 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 NEL CSU. 3. NEL 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 NEL 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. 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. Community Services Data Set (CSDS) 10. Diagnostic Imaging Data Set (DIDS) 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 –NEL 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), Community Services Data Set (CSDS). Diagnostic Imaging data (DIDS) and National Cancer Waiting Times Monitoring Data Set (CWT) only is securely transferred from the DSCRO to NEL CSU 2. NEL 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. NEL 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 NEL CSU or the CCG as instructed by the CCG. 6. Patient level data will not be shared outside of the CCG and will only be shared within the CCG on a need to know basis, as per the purposes stipulated within the Data Sharing Agreement. External aggregated reports only with small number suppression can be shared as set out within NHS Digital guidance applicable to each data set.


Project 2 — NIC-41640-G0C5N

Opt outs honoured: Y, N

Sensitive: Sensitive

When: 2016/12 — 2018/05.

Repeats: Ongoing

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

Categories: Identifiable, 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, Primary Care
  • 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 - Mental Health
  • Local Provider Data - Other not elsewhere classified
  • Local Provider Data - Population Data
  • Local Provider Data - Primary Care
  • SUS Accident & Emergency data
  • SUS Admitted Patient Care data
  • SUS Outpatient data
  • Local Provider Data - Public Health & Screening services
  • Maternity Services Dataset
  • SUS data (Accident & Emergency, Admitted Patient Care & Outpatient)
  • SUS for Commissioners
  • Public Health and Screening Services-Local Provider Flows
  • Primary Care Services-Local Provider Flows
  • Population Data-Local Provider Flows
  • Other Not Elsewhere Classified (NEC)-Local Provider Flows
  • Mental Health-Local Provider Flows
  • Maternity Services Data Set
  • Experience, Quality and Outcomes-Local Provider Flows
  • Emergency Care-Local Provider Flows
  • Diagnostic Services-Local Provider Flows
  • Diagnostic Imaging Dataset
  • Demand for Service-Local Provider Flows
  • Community-Local Provider Flows
  • Children and Young People Health
  • Ambulance-Local Provider Flows
  • Acute-Local Provider Flows

Objectives:

Invoice Validation As an approved Controlled Environment for Finance (CEfF), the data processor receives SUS data identifiable at the level of NHS number according to S.251 CAG 7-07(a) and (c)/2013, to undertake invoice validation on behalf of the CCG. NHS number is only used to confirm the accuracy of backing-data sets and will not be shared outside of the CEfF. The CCG are advised by the CSU whether payment for invoices can be made or not. Pseudonymised – SUS, Local Flows, Mental Health, IAPT, CYPHS and DIDs To use pseudonymised data for the following datasets to provide intelligence to support commissioning of health services : - SUS - Local Flows - Mental Health Minimum Data Set (MHMDS) - Mental Health Learning Disability Data Set (MHLDDS) - Mental Health Services Data Set (MHSDS) - Maternity Services Data Set (MSDS) - Improving Access to Psychological Therapy (IAPT) - Child and Young People Health Service (CYPHS) - Diagnostic Imaging Data Set (DIDS) The pseudonymised data is required to ensure that analysis of health care provision can be completed to support the needs of the health profile of the population within the CCG area based on the full analysis of multiple pseudonymised datasets. No record level data will be linked other than as specifically detailed within this application/agreement. Data will only be shared with those parties listed and will only be used for the purposes laid out in the application/agreement. The data to be released from NHS Digital will not be national data, but only that data relating to the specific locality of interest of the applicant.

Expected Benefits:

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

Outputs:

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

Processing:

North East London DSCRO will apply Type 2 objections before any identifiable data leaves the DSCRO. Invoice Validation 1. SUS Data is obtained from the SUS Repository to DSCRO North East London. 2. North East London DSCRO pushes a one-way data flow of SUS data into the Controlled Environment for Finance (CEfF) in the North East London CSU. 3. The CSU carry out the following processing activities within the CEfF for invoice validation purposes: a. Checking the individual is registered to a particular Clinical Commissioning Group (CCG) and associated with an invoice from the national SUS data flow to validate the corresponding record in the backing data flow b. Once the backing information is received, this will be checked against national NHS and local commissioning policies as well as being checked against system access and reports provided by NHS Digital to confirm the payments are: i. In line with Payment by Results tariffs ii. are in relation to a patient registered with a CCG GP or resident within the CCG area. iii. The health care provided should be paid by the CCG in line with CCG guidance.  4. The CCG are notified that the invoice has been validated and can be paid. Any discrepancies or non-validated invoices are investigated and resolved between the CSU CEfF team and the provider meaning that no identifiable data needs to be sent to the CCG. The CCG only receives notification to pay and management reporting detailing the total quantum of invoices received pending, processed etc. Pseudonymised – SUS, Local Flows, Mental Health, IAPT, CYPHS and DIDs 1. Data Services for Commissioners Regional Office (DSCRO) obtains a flow of data identifiable at the level of NHS number for SUS, Local Flows, Mental Health (MHSDS, MHMDS, MHLDDS), Maternity (MSDS), IAPT, CYPHS and DIDs for commissioning purposes. 2. Data quality management and pseudonymisation of data is completed by DSCRO North East London and the pseudonymised data is then passed securely to North East London CSU for the addition of derived fields, linkage and analysis. 3. North East London CSU then pass the processed, pseudonymised linked data to the CCG. 4. The CCG analyses the data to see patient journeys for pathway or service design, re-design and de-commissioning 5. Aggregation of required data for CCG management use will be completed by the CSU or the CCG as instructed by the CCG 6. Patient level data will not be shared outside of the CCG and will only be shared within the CCG on a need to know basis, as per the purposes stipulated within the Data Sharing Agreement. External aggregated reports only with small number suppression can be shared where contractual arrangements are in place.