https://github.com/nhsdigital/asc-client-level-data-salt-ascof-transformations
https://github.com/nhsdigital/asc-client-level-data-salt-ascof-transformations
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/nhsdigital/asc-client-level-data-salt-ascof-transformations
- Owner: NHSDigital
- Created: 2024-04-12T08:41:55.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-05-22T07:48:35.000Z (about 2 years ago)
- Last Synced: 2025-04-09T09:44:24.928Z (about 1 year ago)
- Size: 1000 KB
- Stars: 3
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Adult Social Care Client Level Data
## What is Client Level Data?
#### Adult Social Care CLient Level Data (CLD) is a data product is created from data submitted to NHS England by Arden & GEM (AGEM) who collect the data from local authorities on a quarterly basis. This is then transferred to NHS England where data is pseudonymised centrally and made available to request through the Data Access Request Service (DARS). It contains data relating to adults over 18 who are receiving social care services, informal carers and events where the care is provided or arranged by the local authority.
#### Following a 12-month period of dual running in 2023/24, CLD will replace the Short and Long Term (SALT) collection in 2024/25. CLD is seen as an evolution of the SALT return, containing more granular detail and timeliness to allow for more flexible and broader analytical use.
## What is the purpose of these SQL codes?
#### The codes are intended to replicate (wherever possible) the metrics previously captured in the Short and Long Term Support (SALT) collection, using the Client Level Data, where there is an ongoing need for this insight. The code processes have been written to be as true to the original principles of SALT as possible and filter, process, de-duplicate and aggregate the data in a way that closest matches SALT and provides transparency on how these figures will be calculated centrally, or how users accessing data through the Data Access Request Service could recreate these locally. Please refer to the Transformation Documentation linked above for more of an over-arching step-by-step guide on how the order and logic of the various coding processes created.
#### Methods were developed in collaboration with local authority and DHSC analysts on our CLD SALT metrics reference group, and made available to all local authorities for feedback which has been reviewed and incorporated where applicable. This document now reflects the approaches that will be used when comparing SALT with CLD equivalents for 2023/24. 2023/24 is the last year of SALT data collection and so the content of this code is now fixed and will not be subject to any further rounds of feedback or changes.
## Prerequisites
#### Codes are stored as txt files, which can be pasted into an instance of SQL Server Management Studio. The codes were developed by NHS England using the access to the AGEM CLD Repository and as such the labels used reflect this (Database names, table names, field names). These labels will need to be changed according to local naming conventions and an existing connection to to Client Level Data is required. The principles of the base code should, however, be transferable once adjustments to these labels are made.
## Known Limitations
#### As a new data collection, with a change in the underlying source, metrics derived from CLD are not expected to perfectly match those from SALT (and a small number of fields collected and used in SALT were not carried over to the CLD specification). However, the approach outlined is intended to stay in line with principles adopted by SALT. See the individual Notes and Limitations associated with each measure for more specific information.