Unofficial. This site is an experimental reformatting of data published by NHS England. It is not endorsed by NHS England. Always check the official Data Uses Register before relying on anything here.

DSfC - NHS Hambleton, Richmondshire and Whitby CCG - Comm

NHS Humber and North Yorkshire ICB · Sub ICB Location

Listed under NHS Humber and North Yorkshire Integrated Care Board.

Expired The latest version ended on 13 December 2021. The September 2026 register still lists the agreement, but its term has passed.

Reference
DARS-NIC-134558-G9L9K
Latest version
v1.2
Term of latest version
14 December 2018 to 13 December 2021
Start date
Before 14 December 2018
Data controller
Sole Data Controller
Commercial purposes
No
Sublicensing
No
Files released to date
0

Why the data was released

Objective for processing

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 NHS North of England Commissioning Support Unit

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.

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.

Data Minimisation

Data Minimisation in relation to the data sets listed within section 3 are listed below. This also includes the purpose on which they would be applied -

For the purpose of Commissioning:

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

and/or

• 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 clarity, any access by Pulsant 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.

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. 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 – North of England Commissioning Support Unit (CSU)

1. Data quality management and pseudonymisation of data is completed by the DSCRO and the pseudonymised data is then held until completion of points 2 – 7.

2. North of England Commissioning Support Unit also receive GP Data. It is received as follows:

o Identifiable GP data is submitted to the CSU.

o The data lands in a ring-fenced area for GP data only.

o There is a Data Processing Agreement in place between the GP and the CSU. A specific named individual within the CSU acts on behalf on the GP. This person has been issued with a black box.

o The individual requests a pseudonymisation key from the DSCRO to the black box. The key can only be used once. The key is specific to that GP and the pseudonymisation request. The individual does not have access to the data once it has been passed on to the CSU.

o The GP data is then pseudonymised using the black box and DSCRO issued key – the clear data is then deleted from the ring-fenced area.

o The CSU are then sent the pseudo GP data with the pseudo key specific to them.

3. North of England Commissioning Support Unit receive a flow of social care data. Social Care data is received in one of the following 2 ways:

o Pseudonymised:

 The social care organisation is issued with their own black box solution.

 The social care organisation requests a pseudonymisation key from the DSCRO to the black box. The key can only be used once and is specific to that date.

 The social care organisation submits the pseudonymised social care data to the CSU with the pseudo algorithm specific to them

o Identifiable:

 Identifiable Social Care data is submitted to North of England Commissioning Support Unit

 The data lands in a ring-fenced area for GP data only.

 There is a Data Processing Agreement in place between the Local Authority and North of England Commissioning Support Unit A specific named individual within North of England Commissioning Support Unit on behalf on the Local Authority. This person has been issued with a black box.

 The individual requests a pseudonymisation key from the DSCRO to the black box. The key can only be used once. The key is specific to the Local Authority and to that specific date.

 Before North of England Commissioning Support Unit will receive the data from the ring-fenced area, they require confirmation that the identifiable data has been deleted.

 North of England Commissioning Support Unit are then sent the pseudonymised GP data with the pseudo algorithm specific to them.

4. North of England Commissioning Support Unit receive a flow of consented data. It is received as follows:

o Identifiable consented data is submitted to the CSU.

o The data lands in a ring-fenced area for consented data only.

o There is a Data Processing Agreement in place between the CCG and the CSU. A specific named individual within the CSU acts on behalf on the CCG. This person has been issued with a black box.

o The individual requests a pseudonymisation key from the DSCRO to the black box. The key can only be used once. The key is specific to the CCG and the pseudonymisation request. The individual does not have access to the data once it has been passed on to the CSU.

o The consented data is then pseudonymised using the black box and DSCRO issued key – the clear data is then deleted from the ring-fenced area.

o The CSU are then sent the pseudo consented data with the pseudo key specific to them.

5. Once the pseudonymised GP data, social care data and consented data is received, the CSU make a request to the DSCRO.

6. The DSCRO then send a mapping table to the CSU

7. The CSU then overwrite the organisation specific keys with the DSCRO key.

8. The mapping table is then deleted.

9. The DSCRO then pass the pseudonymised SUS, local provider data, Mental Health (MHSDS, MHMDS, MHLDDS), Maternity (MSDS), Improving Access to Psychological Therapies (IAPT), Child and Young People’s Health (CYPHS) and Diagnostic Imaging (DIDS) Community Services Data Set (CSDS) and National Cancer Waiting Times Monitoring Data Set (CWT) securely to North of England CSU for the addition of derived fields, linkage of data sets and analysis.

10. Social care, GP and Consented data is then linked to the data sets listed within point 9 in the CSU. utilising algorithms and analysis

11. North of England Commissioning Support 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

12. North of England Commissioning Support also apply an risk stratification algorithm to the pseudonymised SUS+, Local Provider flows and GP data.

13. Aggregation of required data for CCG management use will be completed by the CSU as instructed by the CCG.

14. Patient level data will not be shared outside of the Data Processor/Controller and will only be shared within the Data Processors 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.

Expected output

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

Discharged from community

Expected measurable 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.

Benefits reported so far

Not stated in the register.

Datasets on the latest version

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

Datasets approved under DARS-NIC-134558-G9L9K-v1.2
DatasetType of dataSensitivity FrequencyConfidential data
Acute-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Ambulance-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Children and Young People Health Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Community-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Demand for Service-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Diagnostic Imaging Data Set (DID) Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Diagnostic Services-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Emergency Care-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Experience, Quality and Outcomes-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Improving Access to Psychological Therapies (IAPT) v1.5 Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Maternity Services Data Set Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Mental Health and Learning Disabilities Data Set (MHLDDS) Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Mental Health Minimum Data Set (MHMDS) Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Mental Health Services Data Set (MHSDS) Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Mental Health-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
National Cancer Waiting Times Monitoring DataSet (NCWTMDS) Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Other Not Elsewhere Classified (NEC)-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Population Data-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Primary Care Services-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
Public Health and Screening Services-Local Provider Flows Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data
SUS for Commissioners Anonymised - ICO Code Compliant Sensitive Frequent Adhoc Flow Does not include the flow of confidential data

Files released

Files released counts only files released externally by DARS. Access granted in NHS England's own systems, such as its Secure Data Environment, is not included.

No files recorded as released under this agreement.

Version history

The register lists each renewal of this agreement as a separate row. This site has 1 version — earlier versions existed before this site's records begin.

DARS-NIC-134558-G9L9K-v1.2 14 December 2018 to 13 December 2021
Title
DSfC - NHS Hambleton, Richmondshire and Whitby CCG - Comm
Commercial
No
Sublicensing
No
Datasets
21
Files released
0

Datasets: Acute-Local Provider Flows; Ambulance-Local Provider Flows; Children and Young People Health; Community-Local Provider Flows; Demand for Service-Local Provider Flows; Diagnostic Imaging Data Set (DID); Diagnostic Services-Local Provider Flows; Emergency Care-Local Provider Flows; Experience, Quality and Outcomes-Local Provider Flows; Improving Access to Psychological Therapies (IAPT) v1.5; Maternity Services Data Set; Mental Health and Learning Disabilities Data Set (MHLDDS); Mental Health Minimum Data Set (MHMDS); Mental Health Services Data Set (MHSDS); Mental Health-Local Provider Flows; National Cancer Waiting Times Monitoring DataSet (NCWTMDS); 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

Register history

When this agreement appeared in, or was edited in, each monthly edition of the register. Built by comparing every edition this site holds, the earliest of which is July 2021.

Cite this page

NHS England (2026) Data Uses Register, September 2026 edition, agreement DARS-NIC-134558-G9L9K, “DSfC - NHS Hambleton, Richmondshire and Whitby CCG - Comm”. Read via NHS Data Access Explorer (unofficial), https://healthdatauses.uk/agreements/dars-nic-134558-g9l9k/ (accessed [date]).

This address stays the same, but the page is rebuilt with each monthly edition, so the citation names the edition it shows. Every edition's data is kept in the facts store.

Source: datausesregister_september2026.xlsx, September 2026 edition of the NHS England Data Uses Register. Search that workbook for DARS-NIC-134558-G9L9K to see the original rows.