Determination of fasiglifam-induced liver toxicity: Insights from the data monitoring committee of the fasiglifam clinical trials program
Bibliographic record
Abstract
BACKGROUND: Different approaches to safety event collection influence the determination of liver toxicity within drug development programs. Herein, a description of how fasiglifam-induced liver injury was detected is provided. METHODS: This eight-trial drug development program was intended to evaluate fasiglifam (25 mg, 50 mg) against placebo or active comparators (glimepiride, sitagliptin) in approximately 11,000 suboptimally controlled patients with type 2 diabetes (terminated Dec 2013 due to liver toxicity). Liver safety had been pre-identified as a concern, and within the phase 3 trials, was measured through (1) adverse event reporting, (2) central predefined liver monitoring schedule with various thresholds for potential drug-induced liver injury, and (3) blinded adjudication of serious liver toxicity by a panel of experts in drug-induced liver injury. A single data monitoring committee provided safety oversight across all trials within the program. FINDINGS: Prior to program termination, 7595 of 7602 (99.9%) randomized participants across the eight trials received at least one dose of the study drug (fasiglifam, placebo, or active control). No concerning trends were noted in adverse or serious adverse event frequency, suspected unexpected serious adverse reaction, alanine or aspartate transaminase elevations, or hepatobiliary or gastrointestinal adverse events as reported by local site investigators. However, the predefined central liver safety measurements revealed a greater frequency of possible Hy's Law cases (5 vs 2) and a 3- to 7-fold greater relative risk in alanine or aspartate transaminase elevation (with respect to upper limit of normal) within fasiglifam recipients compared with placebo/active control: alanine or aspartate transaminase > 3×: relative risk 3.34 (95% confidence interval 2.29-4.90), alanine or aspartate transaminase > 5×: relative risk 6.60 (95% confidence interval 3.03-14.38), alanine or aspartate transaminase > 8×: relative risk 6.14 (95% confidence interval 2.18-17.27), and alanine or aspartate transaminase > 10×: relative risk 6.74 (95% confidence interval 2.05, 22.14). All elevations resolved on study drug discontinuation. Drug-induced liver injury was adjudicated as highly likely or probably related in 0.64% of fasiglifam-treated versus 0.06% placebo or active control-treated patients. CONCLUSION: In spite of clear liver toxicity detected with a systematic surveillance program, liver safety signals were not identified from investigator adverse event reporting alone. By integrating key safety monitoring processes within the randomized design of adequately sized clinical trials, the rare but serious liver toxicity signal became clear, leading to timely program termination.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.076 | 0.066 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.003 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; both teacher heads agree on what is shown here.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".