This document is an event-by-event definition of the events captured
by the NDRS Cancer Pathway Dataset. Each event is labelled, numbered,
and its properties listed. The methodology used to define the event is
given, any data quality /completeness issues are described, and any
extra notes for interpretation are also provided.
Please contact ndrsenquiries@nhs.net with any
queries, or suggestions on how to improve this document.
|
Field or property
|
Description
|
|
Event name
|
CWT referral
|
|
Event number
|
501
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
As recorded by the Cancer Waiting Times (CWT) system, the event of the
patient being referred to secondary care, leading to this tumour
diagnosis.
|
|
Property 1 definition
|
The REF_SOURCE field from the CWT data table
|
|
Property 2 definition
|
The PRIORITY_TYPE field from the CWT data table.
|
|
Property 3 definition
|
The REF_TYPE field from the CWT data table.
|
|
Date definition
|
Where the CRTP_DATE from the CWT table is not missing this is used. If
it is missing and the DEC_TO_REF_DATE field is present then that date is
used.
|
|
Trust definition
|
The TRUST_FIRST_SEEN field in the CWT table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
Where both DEC_TO_REF_DATE and CRTP_DATE are missing the event is not
populated, even if a CWT record exists. This field holds tumour-linked
data, using the tumour linkage table specified in the data source.
|
|
DQ/Completeness Issues
|
Approximately 25% of cancer patients do not have a CWT record associated
with their tumour.
|
|
Notes for interpretation
|
Also see event 601, which is partially populated from this field
|
|
|
Field or property
|
Description
|
|
Event name
|
CWT First seen
|
|
Event number
|
502
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
As recorded by the Cancer Waiting Times (CWT) system, the event of the
patient being first seen in secondary care, leading to this tumour
diagnosis.
|
|
Property 1 definition
|
The REF_SOURCE field from the CWT data table
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
The DATE_FIRST_SEEN field as recorded in the CWT dataset.
|
|
Trust definition
|
The TRUST_FIRST_SEEN field in the CWT table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
Where the DATE_FIRST_SEEN is missing the event is not populated, even if
a CWT record exists. This field holds tumour-linked data, using the
tumour linkage table specified in the data source.
|
|
DQ/Completeness Issues
|
Approximately 25% of cancer patients do not have a CWT record associated
with their tumour.
|
|
Notes for interpretation
|
Also see event 602, which is partially populated from this field
|
|
|
Field or property
|
Description
|
|
Event name
|
Radiology
|
|
Event number
|
503
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
A radiology event, as recorded in the Diagnostic Imaging Dataset (DID).
|
|
Property 1 definition
|
Radiology type as recorded by National Interim Clinical Imaging
Procedure (NICIP) code.
|
|
Property 2 definition
|
Radiology type as recorded by Systematized Nomenclature of Medicine
(SNOMED) code.
|
|
Property 3 definition
|
The PATIENT_SOURCE_SETTINGS field from the DIDs table is used.
|
|
Date definition
|
PROCEDURE_DATE_CANCER_IMAGING in the DIDs data table is used.
|
|
Trust definition
|
The SITE_CODE_OF_IMAGING field in the DIDs table are used.
|
|
Data source
|
The DIDs data table is CASREF02.DIDS.DIDS_ANALYSIS
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Events prior to a
year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
The DIDs data is thought to be less complete for radiology with dates in
2012 and early 2013. There is known undercounting for patients diagnosed
in 2015 and imaging in 2016. The data is largely incomplete after 2017
|
|
Notes for interpretation
|
Trusts vary in their use of NICIP vs SNOMED coding - it is advisable to
use both to capture a particular class of radiology.
|
|
|
Field or property
|
Description
|
|
Event name
|
HES Admitted Patient Care episode
|
|
Event number
|
504
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
An episode of care as an inpatient, as recorded in the Hospital Episodes
Statistics (HES) Admitted Patient Care (APC) dataset
|
|
Property 1 definition
|
The ICD-10 code for the primary diagnosis of the patient in the episode.
|
|
Property 2 definition
|
Treatment speciality for the episode as recorded in the TRETSPEF field,
then a colon character, then the admimeth (admission method) value for
the episode
|
|
Property 3 definition
|
All ICD-10 diagnostic codes aggregated together in a list, separated by
“:”
|
|
Date definition
|
The EPISTART and EPIEND fields are used to identify the beginning and
end of the episode
|
|
Trust definition
|
The PROCODE3 field in the HESAPC field is used.
|
|
Data source
|
The HES table is HESLIVE.HESAPC, the diagnosis codes are stored in
HESLIVE.HESAPC_DIAG. Data is also drawn from HESLIVE.HESAPC_PROVISIONAL
with diagnosis codes in HESLIVE.HESAPC_DIAG_PROVISIONAL.
|
|
Further methodology
|
A linkage table HES_LINKAGE_AV_APC is used to link on PATIENTID from the
patient cohort table. Another linkage table
HESLIVE.HES_LINKAGE_AV_APC_PROVISIONAL is used to link to more recent
data. Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data is considered complete from April 2000.
|
|
Notes for interpretation
|
Procedure and operation coding are performed by the coding teams at each
trust and may vary in quality.
|
|
|
Field or property
|
Description
|
|
Event name
|
HES A&E attendance
|
|
Event number
|
505
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
An attendance at Accident and Emergency (A&E)
|
|
Property 1 definition
|
The diagnosis code for the attendence captured in the DIAG2 field.
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
The arrival date at A&E given by the ARRIVALDATE_RAW field.
|
|
Trust definition
|
The PROCODE3 field is used.
|
|
Data source
|
The HES table is HESLIVE.HESAE, the diagnosis codes are stored in
HESLIVE.HESAE_DIAG.
|
|
Further methodology
|
A linkage table HES_LINKAGE_AV_AE is used to link on PATIENTID from the
patient cohort table. Another linkage table
HESLIVE.HES_LINKAGE_AV_AE_PROVISIONAL is used to link to more recent
data. Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data is considered complete from April 2007. Data series ends in March
2020.
|
|
Notes for interpretation
|
Procedure and operation coding are performed by the coding teams at each
trust and vary substantially in quality and completeness.
|
|
|
Field or property
|
Description
|
|
Event name
|
ENCR Diagnosis
|
|
Event number
|
506
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
This event marks the diagnosis as registered by the NDRS cancer
registration system following international standard European Network of
Cancer Registration (ENCR) rules.
|
|
Property 1 definition
|
The basisofdiagnosis field held within the CAS AT_TUMOUR table is used
(see “Data source”).
|
|
Property 2 definition
|
The 3-character ICD-10 code assigned to the tumour by the NCRAS cancer
registration process.
|
|
Property 3 definition
|
The “STAGE_BEST” field held within the CAS AT_TUMOUR_ENGLAND table used
(see “Data source”) .
|
|
Date definition
|
DIAGNOSISDATEBEST from AT_TUMOUR_ENGLAND (see “Data source”) is used.
|
|
Trust definition
|
DIAG_TRUST from AT_TUMOUR_ENGLAND (see “Data source”) is used.
|
|
Data source
|
ANALYSISNCR.AT_TUMOUR_ENGLAND from the snapshot on which the AT_PATHWAY
table is built.
|
|
Further methodology
|
The patient cohort table is linked by TUMOURID to the Data source tables
listed and the fields listed are extracted.
|
|
DQ/Completeness Issues
|
This event is complete for all cancer patients. The ENCR rules privilege
pathological information over other sources of diagnostic information
(such as radiology). In a minority of cases (~10% depending on cancer
type) this may lead to the apparent diagnosisdate post-dating clinical
activity such as MDT, decision to treat, or even treatment.
|
|
Notes for interpretation
|
Also see event 600, which is derived based on this event, but with the
intention of marking the first point at which we can be reasonably
certain that a diagnosis has been made.
|
|
|
Field or property
|
Description
|
|
Event name
|
CWT Active Monitoring
|
|
Event number
|
507
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
The start of active monitoring as captured by the Cancer Waiting Times
(CWT) system.
|
|
Property 1 definition
|
CTE Type
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Treat Start date.
|
|
Trust definition
|
The ORG_TREAT_START code from the CWT treatments table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
CWT records with modality 08 (active monitoring) are identified. This
field holds tumour-linked data, using the tumour linkage table specified
in the data source.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Major Surgery
|
|
Event number
|
508
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Major surgery events from HES (restricted to within a year before the
diagnosis).
|
|
Property 1 definition
|
OPCS code of resection
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Surgery date from APC HES, using previously established major surgery
codes.
|
|
Trust definition
|
The provider code PROCODE3 from HES APC or OP is used.
|
|
Data source
|
The HES table is HESLIVE.HESAPC and HESLIVE.HESOP, the procedure codes
are stored in HESLIVE.HESAPC_OPERTN and HESLIVE.HESOP_OPERTN
|
|
Further methodology
|
Lookup table AV2021.opcs4resection_lookup_13_21 is used to implement
CASSOP 4.9 to identify specific OPCS codes for major surgery by cancer
site. Stage-specific major surgery is identified using AVP_TEST_HES_LUT
and AVP_TEST_STAGE_LUT. A linkage table HES_LINKAGE_AC_APC is used to
link on PATIENTID from the patient cohort table. Events prior to a year
before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
No surgery is reported where the cancer site has not had major surgery
codes associated with it, as defined in CASSOP 4.9.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS appointment (pre 201604)
|
|
Event number
|
509
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Radiotherapy fractions before April 2016.
|
|
Property 1 definition
|
PRESCRIBEDFRACTIONS field from RTDS prescriptions table
|
|
Property 2 definition
|
RTPRESCRIBEDDOSE field from RTDS prescriptions table
|
|
Property 3 definition
|
RTTREATMENTANATOMICALSITE field from RTDS prescriptions table
|
|
Date definition
|
Appointment date from RTDS OPCDS_PROCEDURE table.
|
|
Trust definition
|
The provider organisation code from the RTDS prescriptions table is
used.
|
|
Data source
|
The RTDS table (pre April 2016) is RTDS2016.RTDS_PRESCRIPTIONS.
|
|
Further methodology
|
A linkage table RTDS2016.OPCDS_CAS1712_LINKAGE is used to link on
PATIENTID from the patient cohort table. Events prior to a year before
diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data was curated by NatCanSAT, their methodology is unavailable, but
this data is belived to be a mixture of aggregated episode and
disaggregated fraction data.
|
|
Notes for interpretation
|
This is a single event which marks the delivery of one or multiple
fractions of radiotherapy (teletherapy only). It is based on RTDS data
originally collected by NatCanSAT up to March 31st 2016.
|
|
|
Field or property
|
Description
|
|
Event name
|
SACT regimen start
|
|
Event number
|
510
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Start of SACT regimen.
|
|
Property 1 definition
|
Benchmark regimen
|
|
Property 2 definition
|
Intent of treatment
|
|
Property 3 definition
|
ANALYSIS_GROUP field
|
|
Date definition
|
Regimen start date.
|
|
Trust definition
|
The provider organisation code from the SACT tumour table is used.
|
|
Data source
|
The SACT regimen table is SACT_LEGACY.REGIMEN, and
SACT.AT_REGIMEN_ENGLAND for more recent data.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Events prior to a
year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data collection was mandatory from April 2014 and known to be less
complete before that. Treatment for haemotology and paedeatric cancers
are known to be less complete. Some patients may have a regimen recorded
for each cycle.
|
|
Notes for interpretation
|
This is a single event which marks the start of the delivery of a series
of cycles of chemotherapy.
|
|
|
Field or property
|
Description
|
|
Event name
|
Vital Status
|
|
Event number
|
511
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Vital status
|
|
Property 1 definition
|
Vital status code (mostly A/D for Alive/Dead)
|
|
Property 2 definition
|
Underlying cause of death.
|
|
Property 3 definition
|
Death location
|
|
Date definition
|
Vital statusdate (where the patient has died this is the date of death
from ONS).
|
|
Trust definition
|
Not populated
|
|
Data source
|
AV_PATIENT in the latest CAS snapshot.
|
|
Further methodology
|
|
|
DQ/Completeness Issues
|
No known issues. A batch trace is carried out quarterly to pick up
deaths recorded in cases diagnosed up to that point. Deaths can be
considered complete to approximately six weeks prior to the time of last
trace. Where a coroner’s inquest is needed (e.g. suicide, or asbestos
related mesothelioma) reporting of deaths may be delayed and therefore
undercounted in the most recent data.
|
|
Notes for interpretation
|
Death data is as recorded by ONS.
|
|
|
Field or property
|
Description
|
|
Event name
|
Cancer Treatment Period Start
|
|
Event number
|
512
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Start of cancer treatment period from the Cancer Waiting Times (CWT)
system.
|
|
Property 1 definition
|
CTE_Type
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Treatment period start date from CWT.
|
|
Trust definition
|
ORG_DEC_TO_TREAT from the CWTPROC.TREATMENTS table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
The event is populated from the TREAT_PERIOD_START date. Events prior to
a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
This is a mandatory field in the CWT dataset, however only ~75% of
registered cancer cases are recorded in the CWT database.
|
|
Notes for interpretation
|
This marks the date that the patient and consultant agreed the course of
the treatment (also known as the ‘Decision to Treat’ date).
|
|
|
Field or property
|
Description
|
|
Event name
|
Cancer Treatment
|
|
Event number
|
513
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Treatment start date from Cancer Waiting Times (CWT) system.
|
|
Property 1 definition
|
Treatment modality
|
|
Property 2 definition
|
CTE_TYPE
|
|
Property 3 definition
|
METS_SITE
|
|
Date definition
|
Treatment start date from CWT.
|
|
Trust definition
|
ORG_TREAT_START from the CWTPROC.TREATMENTS table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
The event is populated from the TREAT_START date. Events prior to a year
before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
This is a mandatory field in the CWT dataset, however only ~75% of
registered cancer cases are recorded in the CWT database.
|
|
Notes for interpretation
|
The first cancer treatment marks the ‘clock stop’ for the 31-day and
62-day waiting time targets.
|
|
|
Field or property
|
Description
|
|
Event name
|
Outpatient attendence
|
|
Event number
|
514
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Outpatient attendance from HES.
|
|
Property 1 definition
|
Mainspef of clinician leading clinic
|
|
Property 2 definition
|
All opcs4 codes aggreagated together with a seperator of “:”
|
|
Property 3 definition
|
Code for whether the patient attended or not - ATTENDED field
|
|
Date definition
|
Attendance date from HES OP data.
|
|
Trust definition
|
PROCODET from the HESOP table is used.
|
|
Data source
|
The HES table is HESLIVE.HESOP. Data is also drawn from
HESLIVE.HESOP_PROVISIONAL.
|
|
Further methodology
|
A linkage table HES_LINKAGE_AV_OP is used to link on PATIENTID from the
patient cohort table. Another linkage table
HESLIVE.HES_LINKAGE_AV_OP_PROVISIONAL is used to link to more recent
data. Events prior to a year before diagnosis or before 2012 are
screened out.
|
|
DQ/Completeness Issues
|
Includes Did-Not-Attend apponitments, may occur after death if hospital
did not cancel appointments on patient mortality.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
MDT: COSD
|
|
Event number
|
515
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
MDT derived from COSD data.
|
|
Property 1 definition
|
MDT type (local/specialist) : MDTDISCUSSIONINDICATOR field
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
MDT date from COSD.
|
|
Trust definition
|
Provider code from the event table is used.
|
|
Data source
|
The table used is SPRINGMVC3.CANCERCAREPLAN from the snapshot the
pathway is built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Events prior to a
year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Around 80% of patients have a MDT date reported, it is not known whether
this is due to missing data or reflects a fact that some patients are
not going through MDT.
|
|
Notes for interpretation
|
Date of MDT as reported by trusts in their COSD submissions. Patients
may be discussed at multiple MDTs during period of diagnosis and initial
treatment, and after treatment in the followup period.
|
|
|
Field or property
|
Description
|
|
Event name
|
Other tumour diagnosis
|
|
Event number
|
516
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Other primary tumour events.
|
|
Property 1 definition
|
Basis of diagnosis
|
|
Property 2 definition
|
Tumour ICD-10 code
|
|
Property 3 definition
|
Stage Best field
|
|
Date definition
|
Diagnosis date of other tumour in same patient.
|
|
Trust definition
|
DIAGNOSISPROVIDER_CODE from the AV tumour experimental table is used.
|
|
Data source
|
ANALYSISNCR.AT_TUMOUR_ENGLAND from the snapshot on which the Pathway is
built.
|
|
Further methodology
|
The patient cohort table is linked by PATIENTID to the Data source
tables listed and TUMOURID is used to select other tumours and the
fields listed are extracted.
|
|
DQ/Completeness Issues
|
Based on cancer registry data, completeness likely to be ~>98%.
|
|
Notes for interpretation
|
Other primary tumours will be associated with their own tumour pathway,
or if close enough in time the two pathways may ‘merge’ as the patient
is treated concurrently (or consecutively) for multiple primaries,
|
|
|
Field or property
|
Description
|
|
Event name
|
CT from AV_TREATMENT
|
|
Event number
|
517
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Cancer treatment recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Chemotherapy is identified by choosing events where the EVENTCODE is one
of (‘02’,‘04’,‘15’,‘19’,‘21’,‘CTX’,‘02_03’,‘02_15’,‘02_21’,‘15_21’).
Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Date may align with the start of the regimen, first cycle, or other
significant date close to the commencement of chemotherapy.
|
|
Notes for interpretation
|
Typically a single event marking the start chemotherapy treatment.
|
|
|
Field or property
|
Description
|
|
Event name
|
RT from AV_TREATMENT
|
|
Event number
|
518
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Radiotherapy treatment recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Radiotherapy is identified by choosing events where the EVENTCODE is one
of (‘04’,‘05’,‘22’,‘RTX’). Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
Date may align with the start of the appointment or the first/an early
fraction delivered.
|
|
Notes for interpretation
|
Typically a single event marking the start radiotherapy treatment.
|
|
|
Field or property
|
Description
|
|
Event name
|
Surgery from AV_TREATMENT
|
|
Event number
|
519
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
All surgery events recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Surgery is identified by choosing events where the EVENTCODE is one of
(‘01a’,‘01b’,‘01c’,‘01z’). Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
No known issues
|
|
Notes for interpretation
|
All surgeries recorded by the cancer registry, which is limited to those
considered relevant to cancer treatment and includes paliative and
supportive surgery.
|
|
|
Field or property
|
Description
|
|
Event name
|
Major Surgery from AV_TREATMENT
|
|
Event number
|
520
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Major surgery events recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Surgery is identified by choosing events where the EVENTCODE is one of
(‘01a’,‘01b’,‘01c’,‘01z’). Lookup table
AV2021.opcs4resection_lookup_13_21 is used to implement CASSOP 4.9 to
identify specific OPCS codes for major surgery by cancer site.
Stage-specific major surgery is identified using AVP_TEST_AVT_LUT and
AVP_TEST_STAGE_LUT. Events prior to a year before diagnosis are screened
out.
|
|
DQ/Completeness Issues
|
No known issues
|
|
Notes for interpretation
|
All resective surgeries recorded by the cancer registry, defined
according to CASSOP 4.9.
|
|
|
Field or property
|
Description
|
|
Event name
|
SACT cycle event
|
|
Event number
|
521
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Start of SACT cycle.
|
|
Property 1 definition
|
Benchmark regimen
|
|
Property 2 definition
|
Cycle number
|
|
Property 3 definition
|
Performance status at start of cycle, concatenated with performance
status as start of regimen
|
|
Date definition
|
Cycle start date
|
|
Trust definition
|
ORGANISATION_CODE_OF_PROVIDER from the SACT tumour table is used.
|
|
Data source
|
The SACT cycle table is SACT_LEGACY.cycle up to 2017-06-30 and
SACT.AT_REGIMEN_ENGLAND from the latest snapshot after that.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Events prior to a
year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data collection was mandatory from April 2014 and known to be less
complete before that. Treatment for haemotology and paedeatric cancers
are known to be less complete. Data quality can vary strongly by trust -
e.g. some trusts may only submit the first cycle. Use caution in
interpreting.
|
|
Notes for interpretation
|
Events with a BENCHMARK_GROUP in (‘NOT CHEMO’,‘HORMONES’,‘ZOLEDRONIC
ACID’,‘PAMIDRONATE’,‘DENOSUMAB’) are filtered out.
|
|
|
Field or property
|
Description
|
|
Event name
|
SACT drug event
|
|
Event number
|
522
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
SACT drug given.
|
|
Property 1 definition
|
Benchmark regimen
|
|
Property 2 definition
|
Drug group
|
|
Property 3 definition
|
Administration route
|
|
Date definition
|
ADMINISTRATION_DATE
|
|
Trust definition
|
ORG_CODE_OF_DRUG_PROVIDER from the SACT drug detail table is used.
|
|
Data source
|
The SACT drug administration table is SACT_LEGACY.drug_detail up to
2017-06-30 and SACT.AT_DRUG_DETAIL_ENGLAND from the latest snapshot
after that..
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Events prior to a
year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data collection was mandatory from April 2014 and known to be less
complete before that. Treatment for haemotology and paedeatric cancers
are known to be less complete. Data quality can vary strongly by trust.
Use caution in interpreting.
|
|
Notes for interpretation
|
Events with a BENCHMARK_GROUP in (‘NOT CHEMO’,‘HORMONES’,‘ZOLEDRONIC
ACID’,‘PAMIDRONATE’,‘DENOSUMAB’) are filtered out.
|
|
|
Field or property
|
Description
|
|
Event name
|
Hormone from AV_TREATMENT
|
|
Event number
|
523
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Hormone treatment recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Hormone therapy is identified by choosing events where the EVENTCODE is
in (‘03’,‘03_15’,‘03_21’). Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
Known to be very incomplete, approximately 50%. Large regional variation
with much higher rates reported in the Yorkshire area for historic
reasons.
|
|
Notes for interpretation
|
We hope to supplement this with data from the prescriptions dataset, but
the timescale for this is not determined.
|
|
|
Field or property
|
Description
|
|
Event name
|
Brachy from AV_TREATMENT
|
|
Event number
|
524
|
|
Date updated
|
12/05/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Brachytherapy recorded in AV treatment table.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Brachytherapy is identified by choosing events where the EVENTCODE is
06. Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Biopsy
|
|
Event number
|
525
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Biopsy recorded in COSD.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
Provider code from the event table is used.
|
|
Data source
|
The table used is SPRINGMVC3.SURGERYETC from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
Lookup table OPCS4DIAGNOSTICCODES_V_1_5 with the BX flag set is used to
identify biopsy diagnostic events. Events are included when the date and
trust fields are complete.
|
|
DQ/Completeness Issues
|
Severely under-reports realistic numbers of biopsies that must be
occurring.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Endoscopy from COSD
|
|
Event number
|
526
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Endoscopy event recorded in COSD.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
Provider code from the event table is used.
|
|
Data source
|
The table used is SPRINGMVC3.SURGERYETC from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
Lookup table OPCS4DIAGNOSTICCODES_V_1_5 with the LD flag set is used to
identify endoscopy diagnostic events. Events are included when the date
and trust fields are complete.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
COSD Pathology
|
|
Event number
|
527
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Pathology event recorded in COSD.
|
|
Property 1 definition
|
Indication of date used: taken/receipt/ investigation
|
|
Property 2 definition
|
pathologyinvestigationtype
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
The first date available of SAMPLETAKENDATE, SAMPLERECEIPTDATE and
INVESTIGATIONRESULTDATE.
|
|
Trust definition
|
Provider code from the event table is used.
|
|
Data source
|
The table used is SPRINGMVC3.PATHOLOGY from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort, and presented where
the date is available. Events prior to 2012 are excluded.
|
|
DQ/Completeness Issues
|
No known issues, complete for ~85% of cancers.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTD start point
|
|
Event number
|
528
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Date first seen from routes to diagnosis.
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Date of HES record.
|
|
Trust definition
|
PROCODET from the HESLIVE table is used.
|
|
Data source
|
Data is drawn from RTD snapshots under RTD2020.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort, and presented where
the date in HES is available.
|
|
DQ/Completeness Issues
|
Defined for patients with a HES episode as the start point of the Route
to Diagnosis
|
|
Notes for interpretation
|
See http://www.ncin.org.uk/publications/routes_to_diagnosis
for more information
|
|
|
Field or property
|
Description
|
|
Event name
|
RTD referral date
|
|
Event number
|
529
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Referral date from routes to diagnosis (outpatient route).
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Referral date held in HES OP.
|
|
Trust definition
|
PROCODET from the HESLIVE table is used.
|
|
Data source
|
Data is drawn from RTD snapshots under RTD2020.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort, and presented where
the date in HES is available. TODO: Route-code caveat I don’t quite
follow.
|
|
DQ/Completeness Issues
|
Defined for patients with a outpatient HES episode as the start point of
the route.
|
|
Notes for interpretation
|
See http://www.ncin.org.uk/publications/routes_to_diagnosis
for more information
|
|
|
Field or property
|
Description
|
|
Event name
|
MDT: CWT
|
|
Event number
|
530
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
MDT derived from Cancer Waiting Times (CWT) system.
|
|
Property 1 definition
|
MDT type (local/specialist)
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
MDT date from CWT.
|
|
Trust definition
|
ORG_DEC_TO_TREAT from the CWTPROC treatments table is used.
|
|
Data source
|
The CWT data table is CASREF02.CWTPROC.TREATMENTS. The linkage table is
lnk_tums_cwttrts.
|
|
Further methodology
|
The event is populated from the MDT_DATE date. Events prior to a year
before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Only 70-80% of registered cancer cases are recorded in the CWT database.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Biopsy from APC HES
|
|
Event number
|
531
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Biopsy recorded in HES APC data.
|
|
Property 1 definition
|
OPCS code
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
HESAPC OPDATE
|
|
Trust definition
|
PROCODE3 from the HESLIVE APC table is used.
|
|
Data source
|
The HES table is HESLIVE.HESAP. Data is also drawn from
HESLIVE.HESAPC_PROVISIONAL.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Lookup table
OPCS4DIAGNOSTICCODES_V_1_5 with the BX flag set is used to identify
biopsy diagnostic events. Events are included when the date and trust
fields are complete. Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
Severely under-reports realistic numbers of biopsies that must be
occurring.
|
|
Notes for interpretation
|
This field is under review, usage not currently recommended
|
|
|
Field or property
|
Description
|
|
Event name
|
Endoscopy from HES
|
|
Event number
|
532
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Endoscopy event recorded in HES.
|
|
Property 1 definition
|
OPCS4 code
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
HESAPC OPDATE
|
|
Trust definition
|
PROCODE3 from the HESLIVE APC table is used.
|
|
Data source
|
The HES table is HESLIVE.HESAP. Data is also drawn from
HESLIVE.HESAPC_PROVISIONAL.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort. Lookup table
OPCS4DIAGNOSTICCODES_V_1_5 with the LD flag set is used to identify
endoscopy diagnostic events. Events are included when the date and trust
fields are complete. Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
This has been closely examined for colorectal and lung cancers, other
cancers may have less complete endocopy code lists.
|
|
|
Field or property
|
Description
|
|
Event name
|
Active monitoring from COSD
|
|
Event number
|
533
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Active monitoring recorded in COSD.
|
|
Property 1 definition
|
Monitoring intent (1: future curative, 2: future palliative, 3: future
unknown/uncertain)
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
STARTORADMISSIONDATE1
|
|
Trust definition
|
Provider code from the SPRINGMVC3.EVENT table is used.
|
|
Data source
|
The table used is SPRINGMVC3.ACTIVEMONITORING from the snapshot the
pathway is built against. Trust codes are drawn from SPRINGMVC3.EVENT,
SPRINGMVC3.TUMOUREVENTS is used for tumour-level linkage and
SPRINGMVC3.TREATMENT is used for the date.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort, and presented where
the date is available. Events prior to 2012 are excluded.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Path sample taken
|
|
Event number
|
534
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Date the pathology sample was taken as recorded in COSD.
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
SAMPLETAKENDATE
|
|
Trust definition
|
Provider code from the SPRINGMVC3.EVENT table is used.
|
|
Data source
|
The table used is SPRINGMVC3.PATHOLOGY from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort, and presented where
the date is available.
|
|
DQ/Completeness Issues
|
Complete for ~55% of tumours
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Path sample received
|
|
Event number
|
535
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Receipt of the pathology sample as recorded in COSD.
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
SAMPLERECEIPTDATE
|
|
Trust definition
|
Provider code from the SPRINGMVC3.EVENT table is used.
|
|
Data source
|
The table used is SPRINGMVC3.PATHOLOGY from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort, and presented where
the date is available.
|
|
DQ/Completeness Issues
|
Complete for ~75% if tumours
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Path investigation result
|
|
Event number
|
536
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Result of the pathology sample as recorded in COSD.
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
INVESTIGATIONRESULTDATE
|
|
Trust definition
|
Provider code from the SPRINGMVC3.EVENT table is used.
|
|
Data source
|
The table used is SPRINGMVC3.PATHOLOGY from the snapshot the pathway is
built against. Trust codes are drawn from SPRINGMVC3.EVENT.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort, and presented where
the date is available.
|
|
DQ/Completeness Issues
|
Complete for ~65% if tumours
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS episode (post 201604)
|
|
Event number
|
537
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Beginning of radiotherapy episode from April 2016.
|
|
Property 1 definition
|
Radiotherapy intent
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
TREATMENTSTARTDATE
|
|
Trust definition
|
ORGPROVIDER from the RTDS episodes table is used.
|
|
Data source
|
The RTDS table (from April 2016) is RTDS.AT_EPISODES and
RTDS.AT_PRESCRIPTIONS from the snapshot the pathway is built against.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort, and presented where
the date is available. Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
There is intermittant under-reporting by trust in the last few months of
recorded data as the RTDS team actively follow up trust by trust.
|
|
Notes for interpretation
|
Marks the beginning of the delivery of a series of teletherapy
fractions. It is based on RTDS data originally collected by NCRAS from
April 1st 2016. Welsh providers are excluded.
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS appointment (post 201604)
|
|
Event number
|
538
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Radiotherapy fractions from April 2016.
|
|
Property 1 definition
|
Prescribed fractions
|
|
Property 2 definition
|
Prescribed dose
|
|
Property 3 definition
|
Treatment anatomicalsite
|
|
Date definition
|
APPTDATE
|
|
Trust definition
|
ORGPROVIDER from the RTDS episodes table is used.
|
|
Data source
|
The RTDS table (from 201604) is RTDS.AT_EPISODES and
RTDS.AT_PRESCRIPTIONS from the snapshot the pathway is built against.
|
|
Further methodology
|
The events are patient-linked to the tumour cohort, and presented where
the date is available. Events prior to a year before diagnosis are
screened out.
|
|
DQ/Completeness Issues
|
There is intermittant under-reporting by trust in the last few months of
recorded data as the RTDS team actively follow up trust by trust.
|
|
Notes for interpretation
|
This is a single event which marks the delivery of a fraction of
radiotherapy (teletherapy only). It is based on RTDS data originally
collected by NCRAS from April 1st 2016. Welsh providers are excluded.
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS episode (pre 201604)
|
|
Event number
|
539
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Beginning of radiotherapy episode before April 2016.
|
|
Property 1 definition
|
Radiotherapy intent
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
APPTDATE
|
|
Trust definition
|
ORGPROVIDER from the RTDS episodes table is used.
|
|
Data source
|
The RTDS table (pre 201604) is RTDS2016.RTDS_EPISODES.
|
|
Further methodology
|
A linkage table RTDS2016.OPCDS_AV_TUMOUR_LINKAGE is used to link on
PATIENTID from the patient cohort table to RTDS2016.RTDS_PRESCRIPTIONS,
unique episodes corresponding to those prescriptions are the identified.
Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
No known issues, but DQ not well investigated.
|
|
Notes for interpretation
|
Marks the beginning of the delivery of a series of teletherapy
fractions. It is based on RTDS data originally collected by NatCanSAT up
to March 31st 2016.
|
|
|
Field or property
|
Description
|
|
Event name
|
HESAPC procedures
|
|
Event number
|
540
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
HESAPC procedures
|
|
Property 1 definition
|
List of procedure codes aggregated together in a list, separated by “:”
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Operation date (one event is generated per unique operation date in the
episode)
|
|
Trust definition
|
Provider code for the episode
|
|
Data source
|
The HES table is HESLIVE.HESAPC, the diagnosis codes are stored in
HESLIVE.HESAPC_DIAG. Data is also drawn from HESLIVE.HESAPC_PROVISIONAL
with diagnosis codes in HESLIVE.HESAPC_DIAG_PROVISIONAL.
|
|
Further methodology
|
A linkage table HES_LINKAGE_AV_APC is used to link on PATIENTID from the
patient cohort table. Another linkage table
HESLIVE.HES_LINKAGE_AV_APC_PROVISIONAL is used to link to more recent
data. Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
Data is considered complete from April 2000.
|
|
Notes for interpretation
|
Procedure and operation coding are performed by the coding teams at each
trust and may vary in quality.
|
|
|
Field or property
|
Description
|
|
Event name
|
AV_TREATMENT imaging
|
|
Event number
|
549
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Imaging recorded in AV treatment table.
|
|
Property 1 definition
|
IMAGINGCODE from AV_Treatment
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Imaging is identified by choosing events where the EVENTCODE is ‘IM’.
Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
AV_TREATMENT Other event
|
|
Event number
|
550
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Other treatment recorded in AV treatment table.
|
|
Property 1 definition
|
N/A
|
|
Property 2 definition
|
EVENT CODE from AV_Treatment
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Event date
|
|
Trust definition
|
TRUST_CODE from the AV treatment table is used.
|
|
Data source
|
ANALYSISNCR.AT_TREATMENT_ENGLAND from the snapshot on which the Pathway
is built.
|
|
Further methodology
|
Imaging is identified by choosing events where the EVENTCODE is in
(‘07’,‘08’,‘09’,‘10’,‘11’,‘12’,‘13’,‘14’,‘16’,‘20’,‘2000’,‘21’,‘97’,‘98’,‘99’).
Events prior to a year before diagnosis are screened out.
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS brachytherapy fractions up to April 2016
|
|
Event number
|
551
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
One event for each brachytherapy fraction recorded
|
|
Property 1 definition
|
PRESCRIBEDFRACTIONS
|
|
Property 2 definition
|
RTPRESCRIBEDDOSE
|
|
Property 3 definition
|
RTTREATMENTANATOMICALSITE
|
|
Date definition
|
APPTDATE
|
|
Trust definition
|
ORGCODEPROVIDER
|
|
Data source
|
RTDS2016.RTDS_PRESCRIPTIONS
|
|
Further methodology
|
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS brachytherapy fractions from April 2016
|
|
Event number
|
552
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
One event for each brachytherapy episode recorded
|
|
Property 1 definition
|
RADIOTHERAPYINTENT
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
TREATMENTSTARTDATE
|
|
Trust definition
|
ORGCODEPROVIDER
|
|
Data source
|
RTDS.AT_EPISODES_ENGLAND from the snapshot on which the Pathway is
built.
|
|
Further methodology
|
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS brachytherapy appointments from April 2016
|
|
Event number
|
553
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
One event for each brachytherapy appointment recorded
|
|
Property 1 definition
|
PRESCRIBEDFRACTIONS
|
|
Property 2 definition
|
RTPRESCRIBEDDOSE
|
|
Property 3 definition
|
RTTREATMENTANATOMICALSITE
|
|
Date definition
|
APPTDATE
|
|
Trust definition
|
ORGCODEPROVIDER
|
|
Data source
|
RTDS.AT_PRESCRIPTIONS_ENGLAND from the snapshot on which the Pathway is
built.
|
|
Further methodology
|
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
RTDS brachytherapy episodes up to April 2016
|
|
Event number
|
554
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
One event for each brachytherapy episode recorded
|
|
Property 1 definition
|
RADIOTHERAPYINTENT
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
TREATMENTSTARTDATE
|
|
Trust definition
|
ORGCODEPROVIDER
|
|
Data source
|
RTDS2016.RTDS_EPISODES
|
|
Further methodology
|
|
|
DQ/Completeness Issues
|
DQ has not been closely investigated
|
|
Notes for interpretation
|
|
|
|
Field or property
|
Description
|
|
Event name
|
Derived Diagnosis date
|
|
Event number
|
600
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Derived diagnosis date. Must satisfy the following rules: 1. The derived
diagnosis date must be before or on the same date as the Cancer
treatment period start date; 2. The derived diagnosis date must be
before or on the same date as the MDT date; 3. The derived diagnosis
date must be before or on the same date as first treatment of any kind;
4. It must not be more than han 90 days prior to current diagnosisdate.
|
|
Property 1 definition
|
PROPERTY_1 of event used.
|
|
Property 2 definition
|
PROPERTY_2 of event used
|
|
Property 3 definition
|
Event_TYPE of EVENT used
|
|
Date definition
|
First of diagnosis, treatment, MDT, CTPSD
|
|
Trust definition
|
The trust definition is derived from that of the event used.
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types
6,7,8,9,10,12,13,15,17,18,20,21,22,23,24,30,33,37,38,39 are used for
this derived event.
|
|
DQ/Completeness Issues
|
Complete for all tumours
|
|
Notes for interpretation
|
About 10% of tumours (with strong variation by cancer type) differ in
their derived and ENCR diagnosis date (i.e., event 6). The median
variation is about a week.
|
|
|
Field or property
|
Description
|
|
Event name
|
Referral date
|
|
Event number
|
601
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Derived referral date - takes the first date between CWT referral and
RTD referral.
|
|
Property 1 definition
|
PROPERTY_1 of event used.
|
|
Property 2 definition
|
PROPERTY_2 of event used
|
|
Property 3 definition
|
PROPERTY_3 of event used
|
|
Date definition
|
First of CWT referral and RTD startpoint. Ties for date are broken with
AVPID.
|
|
Trust definition
|
The trust definition is derived from that of the event used.
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types 1,29 are
used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
Experimental field under active development
|
|
|
Field or property
|
Description
|
|
Event name
|
First Seen
|
|
Event number
|
602
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Derived first seen date - takes the first date between CWT first seen
date and RTD start point.
|
|
Property 1 definition
|
PROPERTY_1 of event used.
|
|
Property 2 definition
|
PROPERTY_2 of event used
|
|
Property 3 definition
|
PROPERTY_3 of event used
|
|
Date definition
|
First of CWT first seen and RTD start point. Ties for date are broken
with AVPID.
|
|
Trust definition
|
The trust definition is derived from that of the event used.
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types 2,28 are
used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
Experimental field under active development
|
|
|
Field or property
|
Description
|
|
Event name
|
Derived MDTs
|
|
Event number
|
603
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Tumour
|
|
Event definition
|
Derived MDT date - takes the first date between MDT from COSD and MDT
from CWT.
|
|
Property 1 definition
|
PROPERTY_1 of event used.
|
|
Property 2 definition
|
PROPERTY_2 of event used
|
|
Property 3 definition
|
PROPERTY_3 of event used
|
|
Date definition
|
Date of first MDT, from COSD and CWT.
|
|
Trust definition
|
The trust definition is derived from that of the event used.
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types 15,30 are
used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
First MDT date. This may pre- or post date treatment. Occasionally there
is no recorded MDT in the initial diagnosis or treatment period and the
‘first’ MDT will be months later during the followup/recurrence period
|
|
|
Field or property
|
Description
|
|
Event name
|
Derived first treatment
|
|
Event number
|
604
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Derived first treatment - must have minimum of SACT, major surgery,
RTDS, CWT-TSD, hormone treatment, active monitoring, brachytherapy.
|
|
Property 1 definition
|
Modality code
|
|
Property 2 definition
|
EVENT_TYPE of event used
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
First treatment date.
|
|
Trust definition
|
Trust of event used
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types
7,8,9,10,13,17,18,20,21,22,23,24 are used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
This event is generated by scanning the pathway from the point of
daignosis looking for a ‘treatment’ type event.
|
|
|
Field or property
|
Description
|
|
Event name
|
Derived end of initial treatment
|
|
Event number
|
605
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Derived end of initial treatment - looks for first gap in treatment of
more than 182 days.
|
|
Property 1 definition
|
Modality code
|
|
Property 2 definition
|
EVENT_TYPE of event used
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
Last treatment date before gap of >182 days.
|
|
Trust definition
|
Trust of event used
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types
7,8,9,10,13,17,18,20,21,22,23,24 are used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
This event is generated by scanning the pathway from the start of
treatment until a gap of 182 days is found. At that point the previous
treatment is used as the end of treatment. For single point event
treatments (e.g. surgery) the start and end of treatment will co-incide.
Death is not taken into account in this event definition, so if
treatment is interrupt by death the algorithm will naively take the last
recorded treatment in the data as the end of treatment.
|
|
|
Field or property
|
Description
|
|
Event name
|
Treatment for recurrence
|
|
Event number
|
606
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Treatment for recurrence - must satisfy the following rules: 1. Start
with derived end of initial treatment; 2. Look for any active treatment
following it, define this to be a recurrence event; 3. No exclusions for
second primaries; 4. Do not take hormone or WW/AS as evidence for
recurrence.
|
|
Property 1 definition
|
Modality code
|
|
Property 2 definition
|
N/A
|
|
Property 3 definition
|
N/A
|
|
Date definition
|
First treatment date after gap.
|
|
Trust definition
|
The trust definition is derived from that of the event used.
|
|
Data source
|
Derived events are based on existing events in the current AV_PATHWAY
build.
|
|
Further methodology
|
The events are tumour-linked to the tumour cohort. Event types
7,8,9,10,13,17,18,20,21,22,23,24 are used for this derived event.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
Experimental field under active development. This scans the pathway from
the end of treatment looking for a treatment (after the 182 day gap that
event 105 seeks) or other recurrence-signifying event.
|
|
|
Field or property
|
Description
|
|
Event name
|
HES Recurrence
|
|
Event number
|
607
|
|
Date updated
|
18/06/2025
|
|
Linkage
|
Patient
|
|
Event definition
|
Recurrence as recorded by HES.
|
|
Property 1 definition
|
The ICD-10 code for the primary diagnosis of the patient in the episode.
|
|
Property 2 definition
|
Treatment speciality for the episode as recorded in the TRETSPEF field.
|
|
Property 3 definition
|
All ICD-10 diagnostic codes aggregated together in a list, separated by
“:”
|
|
Date definition
|
The EPISTART field is used to identify the beginning and end of the
episode
|
|
Trust definition
|
The first three digits of the PROCODE3 field are in the HESAPC field are
used.
|
|
Data source
|
The HES table is HESLIVE.HESAPC, the diagnosis codes are stored in
HESLIVE.HESAPC_DIAG. Data is also drawn from HESLIVE.HESAPC_PROVISIONAL
with diagnosis codes in HESLIVE.HESAPC_DIAG_PROVISIONAL.
|
|
Further methodology
|
The first episode with a HESAPC diagnositic field (i.e. EVENT_TYPE=4)
that includes (‘C77’,‘C78’,‘C79’) is counted as a recurrence. All
tumours with a second primary (excluding those in (‘C44’, ‘D40’, ‘D01’,
‘D07’, ‘D03’, ‘D04’, ‘D06’)) are excluded.
|
|
DQ/Completeness Issues
|
|
|
Notes for interpretation
|
|
|