Part of Central transformation principles
LTS004
Accommodation and employment status of working age clients with a learning disability.
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 Service User
Service Type is one of Long Term Support: Nursing Care, Residential Care or Community Primary Support Reason is Learning Disability Support
Derive age at period of interest end date – see Summary – and only include those aged 18-64
⇩
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
⇩
To this, join the record with the latest event start date and pull through Employment Status and Accommodation Status. The SALT metric focuses on last known status
⇩
Using this subset, count distinct number of Clients by Employment Status, Accommodation Status, gender and age band, or other choice of breakdown
Count based on count of the new unique ID field
Known limitations
- Data quality issues have been identified in a handful of cases with conflicting accommodation status/employment status for seemingly duplicate records with same event start date. In these cases, any record where accommodation/employment status is known will be brought forward over a duplicate entry with an unknown status. If conflicting records are still present after this step, the latest submitted row will be brought forward. After this process any remaining duplicate events with conflicting accommodation/employment status will be recorded as having an Unknown status in the final table.
- Table is for 18-64 year olds only. Some clients have an unknown age and are therefore not considered for inclusion in the code process.
- 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. To quantify the difference between figures appearing in this table, and headline figures that could be derived from LTS001a, the number of individuals excluded because their record did not meet the specification on employment/accommodation data will be calculated as part of this process.
- 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: 5 June 2024 2:55 pm