| Literature DB >> 31922953 |
Jonathon R Campbell, Dennis Falzon, Fuad Mirzayev, Ernesto Jaramillo, Giovanni Battista Migliori, Carole D Mitnick, Norbert Ndjeka, Dick Menzies.
Abstract
International policy for treatment of multidrug- and rifampin-resistant tuberculosis (MDR/RR TB) relies largely on individual patient data (IPD) from observational studies of patients treated under routine conditions. We prepared guidance on which data to collect and what measures could improve consistency and utility for future evidence-based recommendations. We highlight critical stages in data collection at which improvements to uniformity, accuracy, and completeness could add value to IPD quality. Through a repetitive development process, we suggest essential patient- and treatment-related characteristics that should be collected by prospective contributors of observational IPD in MDR/RR TB.Entities:
Keywords: MDR TB; RR-TB; TB; antimicrobial resistance; bacteria; data collection standards; evidence-based medicine; meta-analysis; multidrug resistance; practice guideline; statistics and numerical data; therapy data collection; tuberculosis
Mesh:
Substances:
Year: 2020 PMID: 31922953 PMCID: PMC7045826 DOI: 10.3201/eid2603.190997
Source DB: PubMed Journal: Emerg Infect Dis ISSN: 1080-6040 Impact factor: 6.883
Data-sharing principles for contributors of individual patient data for multidrug-/rifampin-resistant tuberculosis
| Principle | Additional notes |
|---|---|
| Data contributed to the IPD should be coded to remove identifying information. | • All names, the date of birth, address, telephone number, and other easily identifying personal information must be removed (e.g., national identification or health insurance numbers).
• Each participant contributed should be re-coded with a new IPD identification number that is mapped to the original identification number retained by the contributing investigator, group, and/or program.
• Dates of events (e.g., treatment start, cultures, medication changes) should be retained in the sent participant data file.
• Other local rules for encoding and other data protection measures should be followed. |
| The contributing investigator, group, and/or program retains ownership of the data and should have permission to share them. | • The transfer of data for use in guideline development or other projects does not constitute transfer of ownership.
• Data contributors are free to withdraw their data at any time.
• Data must be contributed only if they are permitted by programs or donor agencies.
• A data sharing agreement will specify the details of the transfer of data (an example of a “starting point” for these data sharing agreements is contained in the Appendix). |
| All transfers of data must clear ethics review | • The institutional review board responsible for the bioethics of each contributed dataset should approve that the data can be shared.
• All anticipated uses of the data should be reviewed and approved by the institutional review board. |
| All uses of data are subject to oversight by the collaborative group. | • Ideally 1 individual is designated to liaise with the rest of the contributors of IPD to approve or deny use of their data for current or future analyses and be part of the oversight committee.
• The oversight committee reviews proposals for data use and sharing of data. |
| All data are held centrally in a secure data repository. | • The IPD used for the development of MDR/RR-TB treatment guidelines for the WHO and other entities has been held securely by the McGill University Health Centre (MUHC) under Dick Menzies since 2010. • The MUHC (now a WHO collaborating center) is expected to retain these responsibilities, pending approval of the oversight committee. • Use of data held in this repository follows these principles, with bioethics approval and conforming to the current data sharing agreements signed. |
Suggested steps to improve the accuracy and completeness of observational IPD
| Suggested steps | Additional notes |
|---|---|
| Persons responsible for capture and entry of data into electronic databases should be appropriately trained. | • This includes obtaining a certificate in good clinical practice and training around the importance of confidentiality.
• This also includes training on the basics of MDR/RR-TB, relevant national guidelines, what to collect, how to collect it, and the importance of accuracy in the capture of data.
• These principles can be reinforced with detailed guidance for data capture and the definitions of the variables collected at the point of capture (e.g., within the electronic system or within a document kept where data are captured). |
| Quality control measures (e.g., data safeguards) should be implemented to prevent implausible or “out-of-range” entries. | • A warning can be implemented for continuous variables falling outside plausible ranges (e.g., age outside 0–99 y).
• Drop-down lists can be created to reduce/remove need for free form data entry (e.g., including the most common extrapulmonary TB sites within the dropdown or limiting responses for HIV-coinfection status to positive, negative, or not tested).
• Safeguards can be logical, which prevent certain data from being entered without a specific response in another section (e.g., CD4 and viral load cannot be filled in unless HIV-coinfection status is positive). |
| Supervisors should have a standard quality assurance routine (e.g., perform routine follow-up for data accuracy of collected information). | • Supervisors should have simple algorithms developed to detect implausible information that defy inbuilt measures (e.g., patients reported to be receiving a medicine to which their DST shows resistance).
• Complete checks should be run on at least 10% of records independently via dual extraction. These checks should be performed regularly and assessed by a supervisor with the goal of 95% accuracy.
• Corrective steps should be taken (e.g., further training, more comprehensive or routine checks of variables) when accuracy of data collection is an issue. |
| Concurrent checks for data completeness should be performed with assessments of accuracy. | • Reminders can be developed that automatically signal that certain variables are not completed each time a patient record is updated. • In addition, preventing the “finalization” of a patient file until all variables are entered can be implemented—however, files should still be permitted to be saved, and other files opened and populated while patient files await finalization. • Completeness of data is of utmost importance—high frequency of absence of certain information may necessitate exclusion of entire datasets from particular analyses for which these data are required. |