216
Views
14
CrossRef citations to date
0
Altmetric
Reviews

Say “no” to spinal cord injury: is nitric oxide an option for therapeutic strategies?

, , , , , , , , , , , , , & show all
Pages 81-90 | Received 07 Jan 2014, Accepted 24 Mar 2014, Published online: 27 May 2014
 

Abstract

Purpose: a literature review was made to investigate the role of nitric oxide (NO) in spinal cord injury, a pathological condition that leads to motor, sensory, and autonomic deficit. Besides, we were interested in potential therapeutic strategies interfering with NO mechanism of secondary damage. Materials: A literature search using PubMed Medline database has been performed. Results: excessive NO production after spinal cord injury promotes oxidative damage perpetuating the injury causing neuronal loss at the injured site and in the surrounding area. Conclusion: different therapeutic approaches for contrasting or avoiding NO secondary damage have been studied, these include nitric oxide synthase inhibitors, compounds that interfere with inducible NO synthase expression, and molecules working as antioxidant. Further studies are needed to explain the neuroprotective or cytotoxic role of the different isoforms of NO synthase and the other mediators that take part or influence the NO cascade. In this way, it would be possible to find new therapeutic targets and furthermore to extend the experimentation to humans.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.