ArticleCureus2023
Transregional Study Highlighting the Increasing Burden of Urology Cancer Multidisciplinary Team Meetings Around the UK.
Article in Cureus, 2023. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
8 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Introduction The urology multidisciplinary team meeting (MDT) is the key weekly meeting that allows the opportunity to review results and discuss management plans for all urological cancers within a department. As populations age and cancer detection and management improve, the demand for the MDT will increase. We conducted a collaborative transregional study within the UK to evaluate the current workload on the urology MDT. Methods The study was divided into two parts: a multicenter retrospective audit and a snapshot survey. Three UK hospitals in Birmingham, Liverpool, and Cardiff were recruited into the multicenter study. Each hospital provided full MDT lists for all weekly meetings between August 2017 and 2022. Retrospective data gathered included the number of patients discussed per week, the average age of patients per week, the time allocated to their weekly MDT, and the total number of consultants in the department. The second part of the study involved the distribution of an online questionnaire to urologists across the UK to obtain a snapshot picture with the above parameters. Results Snapshot data from 34 different UK hospitals showed MDT length ranged from 1-6 hours, patients discussed ranged from 10-90 per week, and the maximum average discussion time was 3.8 minutes per case. Furthermore, 76% (N = 28/37) of respondents said unnecessary cases were discussed. Varied suggestions were provided on how the MDT could be improved. Multicenter five-year data showed a rise in mean total numbers of patients discussed per week in all centers: a 34.8% increase in Birmingham (from 34.5 patients to 46.5 patients), a 23.5% increase in Liverpool (27.2 patients to 33.6 patients), and a 38.8% increase in Cardiff (22.7 patients to 31.5 patients). Hours per meeting were Birmingham (2), Liverpool (3), and Cardiff (4), which meant the average minutes per patient discussion were Birmingham (2.6), Liverpool (5.4), and Cardiff (7.6). Conclusion There is a rapidly rising trend across UK regions for the number of patients being discussed in the urology MDT meeting. The MDT structure and function across the country are highly variable. There is consensus that the MDT discusses cases that are unnecessary, and this has been recognized for many years. Widespread implementation of the latest MDT management guidelines is urgently required to ensure MDT meetings are able to function effectively and efficiently into the future.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.