Part of Central transformation principles
LTS003
Carer support provided during the year, broken down by the age of the carer and the type of support provided. (High level total only.)
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 01/04/2023 (or still open)
Import Date is equal to the Import Date found in the Latest Submission – see Summary
Date of Death on or after 01/04/2023 or no Date of Death
⇩
Set cohort of interest:
Client Type is a Carer
Service Type is 'Carer Support: Direct to Carer' or Service Type is 'Carer Support: Support involving the person cared-for'
or
Service Type is blank AND Event Outcome is 'NFA - Information & Advice / Signposting only'
or
Event Type is 'Assessment' or Event Type is 'Review' AND Service Type is blank
⇩
Give all Carers 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 Carers in the cohort. See Summary for further details
⇩
Map all Carers into SALT ‘Support Provided’ categories using combination of Service Type, Event Type and Event Outcome
⇩
De-duplicate Carers based on a hierarchy (for example. where one individual has multiple type of Support Provided)
⇩
Using this subset, count distinct number of Carers
Count based on count of the new unique ID field
Known limitations
- As carer services are often outsourced to a third party, record level data may not be available for all carers in the way aggregate counts were previously. As such, the metadata needs to be checked to see if LAs have advised of any limitations of their submission which may impact their data, especially in comparison with SALT numbers previously reported.
- 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.
- 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 LTS003 may not be possible.
- 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).
- The accompanying code calculates the high-level numbers (to provide broad comparison with the SALT tables) however due to the limitations above, does not attempt to recreate the breakdown further.
Last edited: 6 June 2024 1:33 pm