Part of Central transformation principles
STS002b
Of existing clients who have received ‘Short term Support to Maximise Independence’ a breakdown of what followed the period of short term support – full approach (code covers high level numbers only).
Set period of interest:
Events beginning on or before 31/03/2024 and ending on or after 01/04/2023 (or still open)
⇩
Set cohort of interest:
Client Type is a Service User
Service Type is ‘Short Term Support: ST-Max’
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
⇩
Create ‘Current Open’ table:
For all events showing in the ST-Max table, check if the client had an open/ongoing Long Term Service event when ST-Max event commenced
Long Term Support event starting before start of ST-Max event and event not ending before start of ST-Max event
⇩
Clustering of ST-Max episodes:
Where there are multiple ST-Max event rows relating to the same reablement episode, group these together into one ST-Max episode
This is where there are ST-Max event rows for the same client running concurrently or sequentially where reablement has been recorded in CLD in an itemised way (allowing for a one day gap)
⇩
Select ST-Max episodes (clusters or discrete events) from ST-Max cohort table where Clients are present in the ‘Current Open’ table. These are the Existing Clients to be taken forward into STS002b
Known limitations:
- The STS002b tables cannot be replicated exactly from CLD as route of access is not available for STS002b as it is only associated in the specification with a request for support. The accompanying code calculates the high-level numbers (to provide broad comparison with the SALT tables) however due to these limitations, does not attempt to recreate the breakdown further.
- To consider ‘what happened next’ the methodology is dependent on Event Outcome field being complete, accurate and valid as per the specification Defined List.
- Early cessation of service is not possible to derive from CLD (as per the guidance). This means that headline figures may be broadly comparable with SALT but the proportion allocated to each sequel will vary.
- For any methodology that needs to consider ‘what happened next’, if Events are left open, and the event end date not updated, the process will not work accurately.
- 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.
- Where records cannot be included (in the overall headline numbers), the impact of records being excluded because they do not meet the specification will be quantified. Records not meeting the specification will be fed back to local authorities through the usual data validation route.
Last edited: 5 June 2024 2:28 pm