Part of Central Transformation Principles
ASCOF 3D
The proportion of people who use services who receive direct payments.
Set period of interest using data from the latest local authority 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 1/04/2023 or no date of death
⇩
Part 1a and 2a client-based measures
Set cohort of interest:
- client type is a service user
- service type is one of 'long term support: nursing care', 'long term support: residential care', 'long term support: Community' or 'long term support: 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.
⇩
De-duplicate clients based on SALT hierarchy (such as where one individual has multiple support settings).
⇩
Denominator
Count distinct number of clients in the cohort where final de-duplicated setting is ‘long term support: community’
Count based on count of the new unique ID field
⇩
Numerator 1a
Of those in the denominator, count distinct number of clients in the cohort where Delivery Mechanism field or Service Component field = ‘Direct Payment’ or Delivery Mechanism field = ‘CASSR managed personal budget’. Count based on count of the new unique ID field.
Numerator 2a
Of those in the denominator, count distinct number of clients in the cohort where delivery mechanism field or service component field = ‘Direct Payment’. Count based on count of the new unique ID field.
⇩
Part 1b and 2b – Carer-based measures
Set cohort of interest:
Client Type is a Carer or Carer known by association
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 and advice / Signposting only'
or
Event Type is 'Assessment' or Event Type is 'Review' AND Service Type is blank
Derive age at period of interest end date see summary.
⇩
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 carer 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 SALT hierarchy (for example where one individual has multiple type of support provided)
⇩
Denominator
Count distinct number of Carers in the cohort where final de-duplicated ‘Support Provided’ field is 'Direct Payment only', 'CASSR Managed Personal Budget' or 'CASSR Commissioned Support only'
Numerator
Numerator 1b: Of those in the denominator, count distinct number of carers in the cohort where Support Provided (see Appendix) = ‘Direct Payment only’ or ‘CASSR Managed Personal Budget’. Count based on count of the new unique ID field.
Numerator 2b: Of those in the denominator, count distinct number of carers in the cohort where Support provided (see Appendix) = ‘Direct Payment’. Count based on count of the new unique ID field.
Known limitations
As delivery mechanism is not mandatory, it may not be 100% populated. Query uses events where either Service Component of ‘Direct Payment’ or Delivery Mechanism of ‘Direct Payment’ but some events may still not be captured if fields are not complete.
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 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 local authorities to highlight areas to be corrected in future submissions.
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).
Carers: there are some instances where the delivery mechanism is unknown or invalid in the service type – support to direct to carer. As it is not possible to categorise this support at the appropriate level of detail, these records are out of scope for ASCOF.
Carers: there are some instances where Event Outcome may be invalid or may not accurately reflect the outcome reached. This may lead to under-reporting of the ‘Information and Advice’ cohort and ‘No Direct Support Provided to Carer’ cohort.
To establish the support setting a client is recorded against, should they be receiving support in different settings at the same time, a hierarchy is used. This uses the same approach as SALT. If an individual were receiving long term support in a residential home as well as some long term support in the community on the date in question, they would be recorded against the residential support setting in SALT rather than the community, and likewise in client level data, therefore out of scope for this indicator.
Last edited: 5 June 2024 4:33 pm