Cancer Registration: Frequency of tumours diagnosed by route to diagnosis, per Government Office Region (GOR) for 38 cancer sites
Open data API in a single place
Provided by Government Digital Service
Get early access to Cancer Registration: Frequency of tumours diagnosed by route to diagnosis, per Government Office Region (GOR) for 38 cancer sites API!
National Cancer Registration and Analysis Service (NCRAS). (2018). Cancer Registration: Frequency of tumours diagnosed by route to diagnosis, per Government Office Region (GOR) for 38 cancer sites (2006-2013) [Data set]. Public Health England. https://doi.org/10.25503/3xn3-jp97
Total incident tumours (malignant and in situ) by Route to Diagnosis per Government Office Region. The data is restricted to the England resident population diagnosed between 01/01 2006 and 31/12/2013. 38 cancer sites are identified and the data is split by age at diagnosis (aggregated to 20 year age band)
-- TOTAL (total number of patients)
--FINAL_ROUTE (One of eight Routes to Diagnosis- methodology for the assignment of each route is described in Elliss-Brookes L, McPhail S, Greenslade M, Shelton J, Hiom S, Richards M (2012) Routes to diagnosis for cancer – determining the patient journey using multiple routine data sets. British Journal of Cancer 107: 1220–1226.)
-- DIAGDATEYEAR (Year of diagnosis)
-- RTD_GROUPS_BREAKDOWN_2013 (Description of site of tumour (topography))
-- GOR_CODE (in accordance with GOR classifications for April 1996-July 1998. See www.ons.gov.uk/methodology/geography/ukgeographies/administrativegeography/england)
-- GOR_NAME (Description of GOR_CODE for each Government Office Region)
-- AGE (aggregated in 4 categories: 0-39, 40-59, 60-79, 80+)
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.