Abstract:
BACKGROUND : In the United Kingdom National Health Service (NHS), digital transformation
programmes have resulted in the creation of pseudonymised linked datasets of patient-level medical
records across all NHS and social care services. In the Southeast England counties of East andWest
Sussex, public health intelligence analysts based in local authorities (LAs) aimed to use the newly
created “Sussex Integrated Dataset” (SID) for identifying cohorts of patients who are at risk of early
onset multiple long-term conditions (MLTCs). Analysts from the LAs were among the first to have
access to this new dataset. METHODS : Data access was assured as the analysts were employed within
joint data controller organisations and logged into the data via virtual machines following approval
of a data access request. Analysts examined the demographics and medical history of patients against
multiple external sources, identifying data quality issues and developing methods to establish true
values for cases with multiple conflicting entries. Service use was plotted over timelines for individual
patients. RESULTS : Early evaluation of the data revealed multiple conflicting within-patient values
for age, sex, ethnicity and date of death. This was partially resolved by creating a “demographic
milestones” table, capturing demographic details for each patient for each year of the data available
in the SID. Older data ( 5 y) was found to be sparse in events and diagnoses. Open-source code
lists for defining long-term conditions were poor at identifying the expected number of patients,
and bespoke code lists were developed by hand and validated against other sources of data. At the
start, the age and sex distributions of patients submitted by GP practices were substantially different
from those published by NHS Digital, and errors in data processing were identified and rectified.
CONCLUSIONS : While new NHS linked datasets appear a promising resource for tracking multi-service
use, MLTCs and health inequalities, substantial investment in data analysis and data architect time is
necessary to ensure high enough quality data for meaningful analysis. Our team made conceptual
progress in identifying the skills needed for programming analyses and understanding the types of
questions which can be asked and answered reliably in these datasets.