z-logo
Premium
Mannitol But Not Dantrolene Prevents Myocardial Dysfunction Following Intra‐cranial Hypertension in Rats
Author(s) -
Hall S.R.R.,
Wang L.,
Milne B.,
Hong M.
Publication year - 2005
Publication title -
american journal of transplantation
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.89
H-Index - 188
eISSN - 1600-6143
pISSN - 1600-6135
DOI - 10.1111/j.1600-6143.2005.01127.x
Subject(s) - dantrolene , medicine , mannitol , anesthesia , pharmacology , chemistry , biochemistry , calcium
Cardiac complications stemming from intra‐cranial hypertension may result from impaired intra‐cellular Ca 2+ homeostasis. The aim of this study was to examine the effects of dantrolene, a blocker of sarcoplasmic reticulum (SR) Ca 2+ release, on myocardial dysfunction associated with intra‐cranial hypertension in rats. Dantrolene (10 mg) with and without 15% mannitol was administered to halothane‐anesthetized rats prior to induction of intra‐cranial hypertension by subdural balloon inflation. Its effects were compared to 3% and 15% mannitol and 5% Pentaspan ® . Dantrolene with mannitol or 15% mannitol alone prevented the transient intra‐cranial hypertension‐induced hyperdynamic response and ensuing circulatory collapse that was found in animals pre‐treated with 3% mannitol solution or pentaspan. Moreover, hemodynamic function was preserved irrespective of TnI cleavage. However, only animals treated with high dose 15% mannitol exhibited lower lipid peroxidation content in the heart. In contrast, pre‐treatment with dantrolene alone did not prevent the cardiac complications associated with intra‐cranial hypertension. In conclusion, 15% mannitol attenuated the cardiopulmonary complications associated with intra‐cranial hypertension. Dantrolene without mannitol was without effect. Since mannitol exhibits free radical scavenging properties, protection could be the result of a decrease in oxidative stress after intra‐cranial hypertension.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here