Part of Central transformation principles
LTS001b
Of the clients in LTS001a, the number of people accessing long term support at the year-end (31 March) by Primary Support Reason, Age Band, Support from Carer, Gender, Ethnicity, Support Setting and Mechanism of Service Delivery.
Set period of interest using data from the latest submission for that reporting period:
Events beginning on or before 31/03/2024 and ending on or after 31/03/2024 (or still open)
Import Date is equal to the Import Date found in the Latest Submission – see Summary
Date of Death on or after 31/03/2024 or no Date of Death
⇩
Set cohort of interest:
Client Type is a Service User
Service Type is one of Long Term Support: Nursing Care, Residential Care, Community or Prison
Derive age at period of interest end date – see Summary
⇩
Give all Clients a new Identifier – using firstly the NHS Number when available, followed by the Local Authority Identifier to fill any gaps wherever possible – to allocate a unique ID to each Client in the cohort. See Summary for further details
⇩
Select which fields are of interest (for example, support setting, PSR, ethnicity) noting that some records need de-duplicating based on a hierarchy (for example, where one individual has multiple Support Settings)
⇩
Using this subset, count distinct number of Clients by PSR and age band, or other choice of breakdown
Count based on count of the new unique ID field
Known limitations
- As with all measures, the process is reliant on LAs accurately capturing fields as per the relevant specification defined lists. Any fields that are invalid as per the CLD specification are removed from the analysis – source data will not be corrected and invalid field entries cannot be mapped to the specification. All invalid field entries are flagged and captured in the Data Quality Reports received by LAs to highlight areas to be corrected in future submissions.
- There are instances arising in CLD where Clients have conflicting PSR entries for otherwise identical records. In these cases, any record where PSR is known will be brought forward over a duplicate entry with an Unknown PSR. If conflicting records are still present after this step, the latest submitted row will be brought forward. After this process any remaining duplicate events with conflicting PSRs will be recorded as Unknown PSR in the final table. Similar sequences are run for Carer Support and Ethnicity for Tables 2 and 3a/b respectively.
- As delivery mechanism is not mandatory, some delivery mechanisms previously captured in SALT (for example, Councils with Adult Social Services Responsibilities (CASSR) commissioned support, CASSR managed personal budget) may not aways be populated in CLD. As such, full completeness across columns previously in LTS001b may not be possible.
- For the purposes of replicating SALT tables, which are typically disaggregated into 18-64 and 65 and over age bands, where a client has missing age information, they would not be included in these tables as they cannot be mapped to an age band.
- NHS Number is used as a unique identifier for each Client wherever possible. Where NHS number is not populated the Local Authority unique ID is used instead, if this can be done without compromising accuracy. In instances where no ID can be attributed to an event row without introducing the risk of either double-counting or incorrect allocation of identifiers to individuals, these event rows will be removed from the headcount (see Summary of main concepts for further information).
- DHSC now publish Monthly statistics for adult social care (England) - GOV.UK (www.gov.uk) using Client Level Data. It should be noted that in the DHSC publication, individuals will be counted under multiple categories if they receive long-term support in multiple settings at the end of the month. As such, the totals (but not the data by setting) are comparable with LTS001b, whereby a person is counted in only one support setting based on a hierarchy.
Last edited: 6 June 2024 9:32 am