Inhibition of histone deacetylation with vorinostat does not prevent tunicamycin-mediated acute kidney injury
Bibliographic record
Abstract
Endoplasmic reticulum (ER) stress is associated with acute kidney injury (AKI) caused by various mechanisms, including antibiotics, non-steroidal anti-inflammatory drugs, cisplatin, and radiocontrast. Tunicamycin (TM) is a nucleoside antibiotic that induces ER stress and is a commonly used model of AKI. 4-phenylbutyrate (4-PBA) is a chemical chaperone and histone deacetylase (HDAC) inhibitor and has been shown to protect the kidney from ER stress, apoptosis, and structural damage in a tunicamycin model of AKI. The renal protection provided by 4-PBA is attributed to its ability to prevent misfolded protein aggregation and inhibit ER stress; however, the HDAC inhibitor effects of 4-PBA have not been examined in the TM-induced model of AKI. As such, the main objective of this study was to determine if histone hyperacetylation provides any protective effects against TM-mediated AKI. The FDA-approved HDAC inhibitor vorinostat was used, as it has no ER stress inhibitory effects and therefore the histone hyperacetylation properties alone could be investigated. In vitro work demonstrated that vorinostat inhibited histone deacetylation in cultured proximal tubular cells but did not prevent ER stress or protein aggregation induced by TM. Vorinostat induced a significant increase in cell death, and exacerbated TM-mediated total cell death and apoptotic cell death. Wild type male mice were treated with TM (0.5 mg/kg, intraperitoneal injection), with or without vorinostat (50 mg/kg/day) or 4-PBA (1 g/kg/day). Mice treated with 4-PBA or vorinostat exhibited similar levels of histone hyperacetylation. Expression of the pro-apoptotic protein CHOP was induced with TM, and not inhibited by vorinostat. Further, vorinostat did not prevent any renal damage or decline in renal function caused by tunicamycin. These data suggest that the protective mechanisms found by 4-PBA are primarily due to its molecular chaperone properties, and the HDAC inhibitors used did not provide any protection against renal injury caused by ER stress.
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 machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 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.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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 source (direct Gemma or distilled Codex), 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".