z-logo
Premium
31 P NMR studies of the diabetic lens
Author(s) -
Gonzalez R. Gilberto,
Miglior Stefano,
Von Saltza Ingrid,
Buckley Lisa,
Neuringer J.,
Cheng HongMing
Publication year - 1988
Publication title -
magnetic resonance in medicine
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.696
H-Index - 225
eISSN - 1522-2594
pISSN - 0740-3194
DOI - 10.1002/mrm.1910060409
Subject(s) - aldose reductase , phosphorylcholine , aldose reductase inhibitor , aldehyde reductase , chemistry , lens (geology) , nuclear magnetic resonance spectroscopy , diabetes mellitus , endocrinology , enzyme , medicine , biochemistry , nuclear magnetic resonance , stereochemistry , biology , paleontology , physics
Phosphorus‐31 ( 31 P) nuclear magnetic resonance (NMR) spectroscopic analyses of the crystalline lens from the experimental diabetic rat were performed. Qualitative and quantitative alterations in the phosphorus‐31 NMR metabolic profile were observed over the course of 3 weeks after the induction of diabetes mellitus. Most striking was the appearance of two new, as yet unidentified, metabolites. These metabolites which resonate at 6.6 and 5.8 ppm were not detected in the normal lens. Compared to the normal lens, glycerol‐3‐phosphate (G3P) underwent an eightfold increase in concentration and phosphorylcholine decreased to one‐third its initial level. The phosphodiesters, glycerophosphorylcholine (GPC) and glycerophosphorylethanolamine (GPE), decreased to barely detectable levels. Oral treatment of the diabetic animal with an aldose reductase inhibitor resulted in the preservation of an essentially normal lens 31 P NMR spectrum. Except for the changes observed in glycerol‐3‐phosphate, these alterations have not been previously reported and raise new questions about the metabolic consequences of diabetes mellitus and the dependence of these alterations on the action of a single enzyme, aldose reductase. © 1988 Academic Press, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here