Skip to main navigation Skip to search Skip to main content

Defining Spine Cancer Pain Syndromes: A Systematic Review and Proposed Terminology

  • On behalf of the AO Spine Knowledge Forum Tumor

Research output: Contribution to journal › Article › peer-review

Abstract

Study Design: Systematic Review. Objectives: Formalized terminology for pain experienced by spine cancer patients is lacking. The common descriptors of spine cancer pain as mechanical or non-mechanical is not exhaustive. Misdiagnosed spinal pain may lead to ineffective treatment recommendations for cancer patients. Methods: We conducted a systematic review of pain terminology that may be relevant to spinal oncology patients. We provide a comprehensive and unbiased summary of the existing evidence, not limited to the spine surgery literature, and subsequently consolidate these data into a practical, clinically relevant nomenclature for spine oncologists. Results: Our literature search identified 3515 unique citations. Through title and abstract screening, 3407 citations were excluded, resulting in 54 full-text citations for review. Pain in cancer patients is typically described as nociceptive pain (somatic vs visceral), neurologic pain and treatment related pain. Conclusions: We consolidate the terminology used in the literature and consolidated into clinically relevant nomenclature of biologic tumor pain, mechanical pain, radicular pain, neuropathic pain, and treatment related pain. This review helps standardize terminology for cancer-related pain which may help clinicians identify pain generators.

Original languageEnglish (US)
Pages (from-to)81S-92S
JournalGlobal Spine Journal
Volume15
Issue number1_suppl
DOIs
StatePublished - Jan 2025

Keywords

  • pain syndrome
  • spinal metastasis

ASJC Scopus subject areas

  • Surgery
  • Orthopedics and Sports Medicine
  • Clinical Neurology

Fingerprint

Dive into the research topics of 'Defining Spine Cancer Pain Syndromes: A Systematic Review and Proposed Terminology'. Together they form a unique fingerprint.

Cite this