| Literature DB >> 31961959 |
Kevin Rademakers1, Andrew Gammie2, Habiba Yasmin3, Linda Cardozo4, Tamsin Greenwell3, Christopher Harding5, Ruth Kirschner-Hermanns6,7, Tom Marcelissen1, Enrico Finazzi-Agro8.
Abstract
AIMS: Lower urinary tract (LUT) function can be investigated by urodynamic studies (UDS) to establish underlying functional abnormalities in the LUT. A multicentre registry could present an opportunity to improve the scientific evidence base for UDS. During the International Consultation on Incontinence Research Society (ICI-RS) meeting in Bristol, United Kingdom 2019, an expert panel discussed the potential of a multicentre urodynamic registry to improve the quality of urodynamic output.Entities:
Keywords: ICI-RS 2019; LUTS; big data; multicentre urodynamics
Mesh:
Year: 2020 PMID: 31961959 PMCID: PMC7497217 DOI: 10.1002/nau.24280
Source DB: PubMed Journal: Neurourol Urodyn ISSN: 0733-2467 Impact factor: 2.696
Challenges in the design of a multinational and multicentre urodynamic data collection
| Data agreements | Considerations on which existing registries to include (how to approach them) (obtain contracts and permissions) |
|---|---|
| Patient consent | This may have been given for the registry to hold the data; consent should also be checked if the data can be used for research by third parties. |
| Data anonymisation | Minimize risk of reidentification. |
| IT infrastructure and data procurement | Defining storage location of the registry data and secure safe transport of the data. |
| Data access and storage | There are generally two types of data access; (a) a centralized model where the registries provide the data and which can be stored on individual servers, or (b) a federated model where there is access to data in the server and which can only extract aggregated statistics. The servers would need to be multi node cpu, with large memory capacity, and dedicated data management software such as Hadoop, and statistical software, such as R. Depending on where the data are coming from, there may be restrictions on where it can be stored (for example, EU data will have an EU storage range). |
| Common data model | Securing the data to enter the registry in a similar format and unit with identical variable names/labels. This will also allow programmers to navigate between datasets with efficiency. |
| Data protection | The need for support on GDPR EU ruling on data privacy and protection, to ensure data are handled compliantly and legally. |