Part of Central transformation principles
LTS002b
Those clients receiving long term support for more than 12 months at the year-end (LTS001c), for whom an unplanned or planned review of care needs took place during the year and the sequel to that review - approach only (no accompanying code)
Create Cohort:
Run process to create LTS001c and pull all Client IDs included in this measure
Client Type is Service User
Event Type is Review
Method of Review is ‘Service User Only’ or ‘Service User and Carer’
Derive age at period of interest end date – see Summary
⇩
Set period of interest:
Events ending between 01/04/2023 and 31/03/2024
⇩
Unplanned reviews:
Filter Events where Review Reason field begins ‘Unplanned - ’
Where Support Setting denotes living in the Community, stage into Community Unplanned table
Where Support Setting denotes Residential/Nursing stage into Res/Nursing Unplanned table
⇩
Sequel to Unplanned Reviews in both Community Unplanned and Res/Nursing Unplanned:
Group by Review Reason to ascertain Significant Event:
- ‘Unplanned - Hospital (Planned and unplanned episodes)’
- ‘Unplanned - Carer related’
- ‘Unplanned - Safeguarding concern’
- ‘Unplanned - Other Reason’
- ‘Unplanned - Provider Failure’
- ‘Unplanned - Change in Commissioning arrangements’)
Count distinct events by sequel to unplanned review
⇩
Planned Reviews:
Filter Events from original LTS001c cohort where Review Reason field is ‘Planned’
Where Support Setting denotes living in the Community (as per existing SALT definitions – link to guidance)
Where Event Outcome is either ‘Progress to Reablement/ST-Max’, ‘Progress to Re- assessment / Unplanned Review’, ‘Progress to Assessment’ or ‘Progress to Support Planning / Services’ to identify that something happened next
Known limitations
- The over-arching approach is captured here should users want to recreate LTS002a however code has not been developed for this measure and so is not available on github. There are no fields in CLD to capture ‘Level of Long Term Support Increased’ and ‘Level of Long Term Support Decreased’: scenarios such as these will need to be inferred from the CLD chronology.
- For the LTS001c cohort, interrupted services may be recorded differently across the country so for this small proportion of cases, more may need to be understood to develop the methodology further.
- There is no currently Event Outcome in the CLD defined list that denotes a Service being temporarily suspended, to satisfy the ‘All Long Term Support Temporarily Suspended’ category in LTS002b. It may be possible to infer this from the Client’s chronology, this is still to be investigated fully as part of finalising the mappings for this table.
- 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.
- For the purpose of this table, which is 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).
Last edited: 6 June 2024 9:46 am