Part of Central Transformation Principles
ASCOF 2A
The proportion of people who received short-term services during the year (who previously were not receiving services) where no further request was made for ongoing support.
Establish ST-Max events and sequels to each period of reablement
Run SALT code for STS002a through in its entirety
⇩
Denominator
Using the final STS002a table build, count out all ST-Max Events where Final Mapped Outcome (mapped to SALT) is in the following list:
- long term support (any setting)
- ongoing low level support
- short term support (other)
- no services provided – universal services / signposted to other services
- no services provided – other
Count based on count of events / rows in table
⇩
Numerator
Using the final STS002a table build, count out all ST-Max Events where Final Mapped Outcome (mapped to SALT) is in the following list:
- ongoing low level support
- short term support (other)
- no services provided – universal services / signposted to other services
- no services provided – other
Count based on count of events / rows in table
Known limitations
For 2023/24 ASCOF, to prioritise continuity, this uses existing SALT principles where people who received short-term services refers to ST-Max episodes only, not other Short Term Services, and classes someone as a new client if they were not in receipt of long term support at the time of the request for support which resulted in ST-Max.
As with all measures, the process is reliant on LAs accurately capturing fields as per the relevant specification defined lists. Any fields necessary for the derivation that are invalid as per the Client Level Data (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.
To consider ‘what happened next’ the methodology is dependent on Event Outcome field being complete, accurate and valid as per the specification Defined List, as there may be no further activity recorded. If events are left open, and the event end date not updated, the process will also 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.
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 key concepts for further information).
Last edited: 6 June 2024 12:48 pm