Harvard Pilgrim Health Care Lumbar Spinal Fusion prior authorization requirements (2026)
What Harvard Pilgrim Health Care generally requires to approve Lumbar Spinal Fusion (CPT 22612), for Commercial plans. Yes. Harvard Pilgrim Health Care generally requires prior authorization for Lumbar Spinal Fusion (CPT 22612).
Medical-necessity criteria Harvard Pilgrim Health Care generally applies
Prior authorization required; delegated to Evolent (formerly NIA) via RadMD. Per Evolent guideline NIA_CG_304 (Lumbar Spine Surgery), single-level lumbar fusion is medically necessary when ALL of: (1) lumbar back pain, neurogenic claudication, and/or radicular leg pain impairing daily activities for at least 6 months (6 months for isolated low back pain); (2) failure of at least 6 consecutive weeks of physician-directed conservative therapy within the last 6 months, including at least two of: analgesics/NSAIDs/steroids, structured physical therapy, structured home exercise program, or epidural steroid/facet/selective nerve root injections; (3) imaging correlating with clinical findings; AND (4) at least one qualifying condition: spondylolisthesis, segmental instability, pseudarthrosis revision, recurrent disc herniation, spinal tumor/infection, or chronic low back pain/degenerative disc disease (the latter additionally requires completion of a comprehensive cognitive-behavioral rehabilitation program and is reviewed case-by-case). Conservative care is waived for progressive acute motor deficit or cauda equina syndrome with a qualifying condition.
Diagnoses that commonly support medical necessity
ICD-10-CM diagnoses frequently associated with medical necessity for Lumbar Spinal Fusion. Confirm the covered diagnosis list against the current Harvard Pilgrim Health Care policy.
Related procedure codes
Codes often billed alongside Lumbar Spinal Fusion: 22612, 22630, 22633. Verify the correct codes for your documentation.
Commonly required documentation
- Office notes, imaging, and documented conservative-care records (including home-exercise prescription and follow-up)
- for revisions, rationale plus signed patient acknowledgment of elevated failure/complication risk.
Situations to verify before submitting
Harvard Pilgrim Health Care may not cover Lumbar Spinal Fusion in these situations. Verify against the current policy rather than assuming a denial:
- Percutaneous lumbar discectomy
- Laser discectomy
- Percutaneous radiofrequency disc decompression
- Intradiscal electrothermal therapy (IDET/IDEA)
- Nucleus pulposus replacement
- Pre-sacral (axial) lumbar fusion
How to submit
- Method: Evolent / RadMD (www.radmd.com or 800-642-7543)
- Portal: RadMD (Evolent/NIA)
Source
Source: Evolent/NIA Musculoskeletal Surgery Guideline NIA_CG_304 (lumbar spine surgery), implementation Jan 2024, delegated by Harvard Pilgrim (Point32Health). Same criteria apply to Tufts. Last verified 2026-06-17.
Frequently asked questions
Does Harvard Pilgrim Health Care require prior authorization for Lumbar Spinal Fusion?
Yes. Harvard Pilgrim Health Care generally requires prior authorization for Lumbar Spinal Fusion (CPT 22612).
What does Harvard Pilgrim Health Care require to approve Lumbar Spinal Fusion?
Prior authorization required; delegated to Evolent (formerly NIA) via RadMD. Per Evolent guideline NIA_CG_304 (Lumbar Spine Surgery), single-level lumbar fusion is medically necessary when ALL of: (1) lumbar back pain, neurogenic claudication, and/or radicular leg pain impairing daily activities for at least 6 months (6 months for isolated low back pain); (2) failure of at least 6 consecutive week… Always confirm against the current Harvard Pilgrim Health Care policy.
How long does a Harvard Pilgrim Health Care prior authorization take?
Turnaround varies by plan and submission method. Check the Harvard Pilgrim Health Care portal for current timeframes.
Submitting Lumbar Spinal Fusion to Harvard Pilgrim Health Care?
Praxigen checks your clinical note against these criteria before you submit and drafts a policy-cited appeal if it is denied. You review and submit; nothing is sent automatically.