Outcome Definition Influences the Relationship between Genetic Polymorphisms of ERCC1, ERCC2, SLC22A2 and Cisplatin Nephrotoxicity in Adult Testicular Cancer Patients
Bibliographic record
Abstract
Although previous research identified candidate genetic polymorphisms associated with cisplatin nephrotoxicity, varying outcome definitions potentially contributed to the variability in the effect size and direction of this relationship. We selected genetic variants that have been significantly associated with cisplatin-induced nephrotoxicity in more than one published study (SLC22A2 rs316019; ERCC1 rs11615 and rs3212986; ERCC2 rs1799793 and rs13181) and performed a replication analysis to confirm associations between these genetic polymorphisms and cisplatin nephrotoxicity using various outcome definitions. We included 282 germ cell testicular cancer patients treated with cisplatin from 2009–2014, aged >17 years recruited by the Canadian Pharmacogenomics Network for Drug Safety. Nephrotoxicity was defined using four grading tools: (1) Common Terminology Criteria for Adverse Events (CTCAE) v4.03 for acute kidney injury (AKI) or CTCAE-AKI; (2) adjusted cisplatin-induced AKI; (3) elevation of serum creatinine; and (4) reduction in the estimated glomerular filtration rate (eGFR). Significant associations were only found when using the CTCAE v4.03 definition: genotype CA of the ERCC1 rs3212986 was associated with decreased risk of cisplatin nephrotoxicity (ORadj = 0.24; 95% CI: 0.08–0.70; p = 0.009) compared to genotype CC. In contrast, addition of allele A at SLC22A2 rs316019 was associated with increased risk (ORadj = 4.41; 95% CI: 1.96–9.88; p < 0.001) while genotype AC was associated with a higher risk of cisplatin nephrotoxicity (ORadj = 5.06; 95% CI: 1.69–15.16; p = 0.004) compared to genotype CC. Our study showed that different case definitions led to variability in the genetic risk ascertainment of cisplatin nephrotoxicity. Therefore, consensus on a set of clinically relevant outcome definitions that all such studies should follow is needed.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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; a candidate call from one teacher head, not a consensus.
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".