MétaCan
Menu
Back to cohort
Record W1968682431 · doi:10.1007/s40264-014-0185-4

Causality Assessment for Suspected DILI During Clinical Phases of Drug Development

2014· review· en· W1968682431 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueDrug Safety · 2014
Typereview
Languageen
FieldPharmacology, Toxicology and Pharmaceutics
TopicDrug-Induced Hepatotoxicity and Protection
Canadian institutionsHealth Canada
FundersInnovative Medicines Initiative
KeywordsMedicineClinical trialCausality (physics)DrugExpert opinionDrug developmentIntensive care medicinePathologyPharmacology

Abstract

fetched live from OpenAlex

Causality assessment is a critical step in establishing the diagnosis of drug induced liver injury (DILI) during drug development. DILI may resemble almost any type of liver disease, and often presents a serious challenge to clinical investigators and drug makers. The diagnosis of DILI is largely based upon a combination of a compatible clinical course, exclusion of all other reasonable causes, resemblance of clinical and pathological features to known features of liver injury due to the drug (i.e., "drug's signature"), and incidence of liver injury among patients treated with the drug compared to placebo or comparator. Causality assessment for suspected DILI is currently performed using either evaluation by physicians with expertise in liver disorders (i.e., expert opinion) or standardized scoring instruments such as the Roussel Uclaf Causality Assessment Method (RUCAM). Both approaches are widely used in the post marketing setting. Causality assessment based on expert opinion is considered superior to standardized instruments such as RUCAM, in the setting of drug development, and is currently the preferred approach during clinical trials. There is a need for a systematic revision of RUCAM that will render it more suitable for the setting of clinical trials and drug development. Careful monitoring and meticulous data collection during clinical trials are essential in all cases with established liver injury to allow for a proper causality assessment. A workshop was convened to discuss best practices for the assessment of drug-induced liver injury (DILI) in clinical trials. This publication is based on the conclusions of this workshop.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.991
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0030.001
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.268
GPT teacher head0.554
Teacher spread0.286 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it