Spine Surgery Prior Authorization: The Documentation Payers Actually Check

By the SpineOS team · Updated July 7, 2026 · 9 min read

Most spine surgery prior authorization denials aren't arguments about the surgical indication — they're documentation failures. Medicare contractor guidance (CMS article A53975, "Spinal Fusion Services: Documentation Requirements") and MAC guidance identify inadequate documentation of conservative treatment as the most common denial driver, and they're explicit that the bare phrase "failed conservative treatment" is not sufficient. This guide walks through what reviewers actually check — dated conservative-care records, imaging that correlates with the clinical picture, functional evidence, neuro exam findings, nicotine status, and shared decision-making — and how to build the packet prospectively instead of reconstructing it after a denial.

Why spine prior auths get denied — the specific documentation gaps

When a fusion request is denied, the denial letter usually cites "medical necessity not established." In practice that phrase almost always maps to one of a handful of concrete, fixable documentation gaps. The reviewer isn't at the bedside; the file is the patient. If the file doesn't tell a dated, internally consistent story, the request fails — even when the underlying case is sound.

Payer policies differ — commercial plans, Medicare Advantage, and traditional Medicare contractors each publish their own criteria, and the specific policy for the specific plan should always be pulled before submission. But the gaps above recur across nearly all of them, and conservative-care documentation is consistently the biggest one.

What "adequate conservative care documentation" means

Medicare contractor guidance is unusually direct on this point: a summary assertion that conservative treatment failed does not establish that it happened. What establishes it is a dated record of what was tried, for how long, and what happened. The elements reviewers commonly look for:

The hardest part is usually not the surgeon's own records — it's outside records. PT often happens at an unaffiliated clinic; the medication trial happened under the PCP; the injections were done at a pain practice. If those records aren't requested and attached, the reviewer sees a gap where care actually occurred. Requesting outside conservative-care records at the first surgical consult, not at submission time, is one of the highest-yield process changes a practice can make.

Imaging–symptom concordance: the story has to match

The second most common weakness is imaging that doesn't correlate with the clinical picture. Degenerative findings are near-universal in the age groups being considered for fusion, and reviewers know it. A report listing multilevel disc degeneration doesn't support surgery at any particular level; what supports it is a specific finding at the symptomatic level and side that explains the symptoms and exam.

Concretely, that means the packet should let a reviewer draw a straight line: left L5 radicular pain and a left L5 sensory deficit on exam, matched to a left L4–L5 foraminal or subarticular finding on MRI — level and side both concordant. Incidental findings at other levels don't substitute, and if the operative plan includes levels the imaging narrative doesn't support, expect a partial denial or a request for more information. Where sagittal alignment is part of the indication, objective measurements help — see our reference on spinopelvic parameters and normal values for the commonly cited thresholds.

A practical habit: at the time imaging is reviewed, record which findings the surgeon actually endorses as clinically relevant, at which level and side, and why. That adjudicated list — not the raw radiology report — is what the medical-necessity narrative should be built from.

PROMs as functional evidence

"Documented functional limitation" is a criterion in most fusion policies, and it's the one that benefits most from validated patient-reported outcome measures. A dated Oswestry Disability Index score quantifies what "significant disability" means for this patient; a series of scores across the conservative-care period documents that structured treatment did not produce meaningful improvement — which is precisely the claim the packet needs to substantiate. (See our guide to ODI scoring and interpretation for the bands and the commonly used MCID.)

Two cautions. First, a single score collected the week of submission is weaker than a baseline collected at intake plus follow-ups — the trend is the evidence, so start collecting early. Second, PROMs are patient-generated data. They're legitimate and widely used, but they should be labeled as patient-reported in the packet and reviewed by a clinician rather than presented as if they were objective exam findings.

Build the packet prospectively, not after the denial

Most denied packets weren't built — they were reconstructed. After a denial, someone goes hunting for PT records from a clinic the practice doesn't control, tries to reconstruct a medication history from memory, and drafts a conservative-care summary months after the care happened. Reconstruction is slow, incomplete, and it shows.

The alternative is to treat every surgical candidate's episode as a packet in progress from the first visit:

• Request outside conservative-care records at the initial consult, while the trail is fresh.
• Collect a baseline PROM at intake and repeat it at follow-ups, so the functional trend exists by decision time.
• Document the neuro exam, with laterality, at each visit where it's performed.
• Record nicotine status early for any fusion candidate, and document counseling.
• When imaging is reviewed, note which findings are endorsed as symptomatic, at which level and side.
• Document the shared decision-making conversation when it happens, not retrospectively.

Practices already running remote therapeutic monitoring have a head start here: RTM programs generate dated, structured records of prescribed conservative care and patient response as a byproduct of the billing documentation — see our guide to RTM CPT codes for spine practices.

How SpineOS assembles this

SpineOS builds a medical-necessity evidence crosswalk from the episode record: imaging findings the clinician has explicitly accepted (never unreviewed candidates), documented symptoms, exam and note text, PROM scores, conservative-care history, and alignment measurements. Each criterion row is marked supported, partial, or missing, so gaps are visible before submission rather than after a denial. Patient-reported items are labeled with their provenance, and a packet containing patient-generated data requires clinician attestation before it's finalized. The output is documentation support for the clinician's own submission — it is not a coverage determination, and no software can promise approval.

Frequently asked questions