Display Settings:

Format

Send to:

Choose Destination
    Arch Phys Med Rehabil. 2004 Jan;85(1):153-7.

    Fibrocartilaginous embolism--an uncommon cause of spinal cord infarction: a case report and review of the literature.

    Source

    Children's Hospital and Regional Medical Center and Department of Rehabilitation Medicine, University of Washington, Seattle, USA. jhan@u.washington.edu

    Abstract

    Fibrocartilaginous embolism is a rare cause of spinal cord infarction. It is postulated that an acute vertical disk herniation of the nucleus pulposus material can lead to spinal cord infarction by a retrograde embolization to the central artery. An increased intradiskal pressure resulting from axial loading of the vertebral column with a concomitant Valsalva maneuver is thought to be the initiating event for the embolus. We present a previously healthy 16-year-old boy with sudden onset of back pain and progressive paraparesis within 36 hours after lifting exercises in a squat position. His clinical presentation and neuroimaging studies were consistent with spinal cord infarction resulting from a central artery embolus at the T8 spinal cord level. Laboratory investigation showed no evidence of infectious, autoimmune, inflammatory, or neoplastic causes. Although no histologic confirmation was obtained, lack of evidence for other plausible diagnoses in the setting of his clinical presentation and in the magnetic resonance imaging findings made fibrocartilaginous embolism myelopathy the most likely diagnosis. We postulated that some cases of transverse myelitis might actually be fibrocartilaginous embolism, making it a more prevalent cause of an acute myelopathy than commonly recognized. Relevant literature and current theories regarding the pathogenesis of fibrocartilaginous embolism myelopathy are reviewed.

    PMID:
    14970983
    [PubMed - indexed for MEDLINE]

      Supplemental Content

      Icon for Elsevier Science

      Save items

      loading

      Recent activity

      Your browsing activity is empty.

      Activity recording is turned off.

      Turn recording back on

      See more...
      Write to the Help Desk