BACKGROUND: In patients with supraclavicular injuries of the brachial plexus, the suprascapular nerve (SSN) is frequently reconstructed with a sural nerve graft coapted to C5. As the C5 cross-sectional diameter exceeds the graft diameter, inadequate positioning of the graft is possible.
OBJECTIVE: To identify a specific area within the C5 proximal stump that contains the SSN axons and to determine how this area could be localized by the nerve surgeon, we conducted a microanatomic study of the intraplexal topography of the SSN.
METHODS: The right-sided C5 and C6 roots, the upper trunk with its divisions, and the SSN of 20 adult nonfixed cadavers were removed and fixed. The position and area occupied by the SSN fibers inside C5 were assessed and registered under magnification.
RESULTS: The SSN was monofascicular in all specimens and derived its fibers mainly from C5. Small contributions from C6 were found in 12 specimens (60%). The mean transverse area of C5 occupied by SSN fibers was 28.23%. In 16 specimens (80%), the SSN fibers were localized in the ventral (mainly the rostroventral) quadrants of C5, a cross-sectional area between 9 o'clock and 3 o'clock from the surgeon's intraoperative perspective.
CONCLUSION: In reconstruction of the SSN with a sural nerve graft, coaptation should be performed in the rostroventral quadrant of C5 cross-sectional area (between 9 and 12 o'clock from the nerve surgeon's point of view in a right-sided brachial plexus exploration). This will minimize axonal misrouting and may improve outcome.
1Peripheral Nerve Surgery Unit, Department of Neurosurgery and Neuroregeneration Center, University of São Paulo Medical School, São Paulo, Brazil
2Neuroregeneration Center, University of São Paulo Medical School, São Paulo, Brazil
3Department of Neurosurgery, Leiden University Medical Center, Leiden, The Netherlands
Received, January 24, 2010.
Accepted, July 6, 2010.
Reprint requests: Mario G. Siqueira, MD, PhD, R. Maestro Cardim 592, cj 1101, CEP01323-001, São Paulo, SP, Brazil. E-mail: email@example.com