Displaying all 3 publications

Abstract:
Sort:
  1. Ahmad N, Javaid A, Syed Sulaiman SA, Afridi AK, Zainab, Khan AH
    Am J Ther, 2016 3 5;25(5):e533-e540.
    PMID: 26938643 DOI: 10.1097/MJT.0000000000000421
    Although Pakistan has a high burden of multidrug-resistant tuberculosis (MDR-TB), little is known about prevalence, management, and risk factors for adverse drug reactions (ADRs) in MDR-TB patients in Pakistan. To evaluate occurrence, management, and risk factors for ADRs in MDR-TB patients, and its impact on treatment outcomes, this observational cohort study was conducted at programmatic management unit for drug resistant TB of Lady Reading Hospital Peshawar, Pakistan. A total of 181 MDR-TB patients enrolled at the study site from January 1, 2012 to February 28, 2013 were included. Patients with drug resistant TB other than MDR-TB, transferred out patients and those who were still on treatment at the end of study duration (January 31, 2015) were excluded. Patients were followed until treatment outcomes were reported. ADRs were determined by laboratory data and/or clinical criteria. SPSS 16 was used for data analysis. A total of 131 patients (72.4%) experienced at least 1 ADR. Gastrointestinal disturbance was the most commonly observed adverse event (42%), followed by psychiatric disturbance (29.3%), arthralgia (24.3%), and ototoxicity (21%). Potentially life-threatening ADRs, such as nephrotoxicity (2.7%) and hypokalemia (2.8%) were relatively less prevalent. Owing to ADRs, treatment regimen was modified in 20 (11%) patients. On multivariate analysis, the only risk factor for ADRs was baseline body weight ≥ 40 kg (OR = 2.321, P-value = 0.013). ADRs neither led to permanent discontinuation of treatment nor adversely affected treatment outcomes. Adverse effects were prevalent in current cohort, but caused minimal modification of treatment regimen, and did not negatively impact treatment outcomes. Patient with baseline body weight ≥ 40 kg should be closely monitored.
  2. Serebruany V, Tanguay JF, Benavides MA, Cabrera-Fuentes H, Eisert W, Kim MH, et al.
    Am J Ther, 2020 10 29;27(6):e563-e572.
    PMID: 33109913 DOI: 10.1097/MJT.0000000000001286
    BACKGROUND: Excess vascular deaths in the PLATO trial comparing ticagrelor to clopidogrel have been repeatedly challenged by the Food and Drug Administration (FDA) reviewers and academia. Based on the Freedom of Information Act, BuzzFeed won a court order and shared with us the complete list of reported deaths for the ticagrelor FDA New Drug Application (NDA) 22-433. This dataset was matched against local patient-level records from PLATO sites monitored by the sponsor.

    STUDY QUESTION: Whether FDA death data in the PLATO trial matched the local site records.

    STUDY DESIGN: The NDA spreadsheet contains 938 precisely detailed PLATO deaths. We obtained and validated local evidence for 52 deaths among 861 PLATO patients from 14 enrolling sites in 8 countries and matched those with the official NDA dataset submitted to the FDA.

    MEASURES AND OUTCOMES: Existence, precise time, and primary cause of deaths in PLATO.

    RESULTS: Discrepant to the NDA document, sites confirmed 2 extra unreported deaths (Poland and Korea) and failed to confirm 4 deaths (Malaysia). Of the remaining 46 deaths, dates were reported correctly for 42 patients, earlier (2 clopidogrel), or later (2 ticagrelor) than the actual occurrence of death. In 12 clopidogrel patients, cause of death was changed to "vascular," whereas 6 NDA ticagrelor "nonvascular" or "unknown" deaths were site-reported as of "vascular" origin. Sudden death was incorrectly reported in 4 clopidogrel patients, but omitted in 4 ticagrelor patients directly affecting the primary efficacy PLATO endpoint.

    CONCLUSIONS: Many deaths were inaccurately reported in PLATO favoring ticagrelor. The full extent of mortality misreporting is currently unclear, while especially worrisome is a mismatch in identifying primary death cause. Because all PLATO events are kept in the cloud electronic Medidata Rave capture system, securing the database content, examining the dataset changes or/and repeated entries, identifying potential interference origin, and assessing full magnitude of the problem are warranted.

Related Terms
Filters
Contact Us

Please provide feedback to Administrator ([email protected])

External Links