Efeito Cardioprotetor da Suplementação Materna com Resveratrol sobre a Toxicidade Induzida por Doxorrubicina em Cardiomiócitos de Neonatos
Bibliographic record
Abstract
BACKGROUND: Doxorubicin (DOX) is frequently used to treat many types of cancers, despite its dose-dependent cardiotoxicity. Alternatively, resveratrol is a polyphenol that has shown useful cardioprotective effects in many heart dysfunction models. OBJECTIVE: This study investigated whether resveratrol treatment in pregnant rats protects against doxorubicin-induced toxicity in offspring cardiomyocytes. METHODS: Wistar rats (n=8) were supplemented with dietary resveratrol during pregnancy. Upon the offspring's birth, hearts (9-11) were used to obtain the primary culture of cardiomyocytes. DOX-induced cardiotoxicity and the effects of resveratrol supplementation were evaluated by oxidative stress markers, such as dichlorofluorescein diacetate oxidation, decrease in the activity of antioxidant enzymes, and oxidation of total sulfhydryl content, in addition to cell viability evaluation, DNA damage generation, and DNA damage repair response. A value of p<0.05 was considered statistically significant. RESULTS: Neonatal cardiomyocytes from resveratrol supplemented rats exhibiting an increase (p<0.01) in cell viability and lower (p<0.0001) apoptotic/necrotic cells after DOX treatment, which correlates with the activities of antioxidant enzymes and dichlorofluorescein production. Moreover, resveratrol protected cardiomyocytes from DOX-induced DNA damage, showing a decrease (p<0.05) in DNA breaks induced by oxidative stress, evaluated by the activity of DNA-repair enzymes endonuclease III and formamidopyrimidine glycosylase. Supplementation with resveratrol increased (p<0.05) the expression of the repair protein Sirt6 in the cardiomyocytes of the pups. CONCLUSION: This research indicates that supplementation with resveratrol during the gestational period has a notable cardioprotective effect on the offspring's heart against DOX-induced toxicity, which may well be due to its antioxidant function, and the increase in the DNA damage repair response.
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.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.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".