Surgical exploration of a previously performed spinal fusion to assess the integrity of the bone graft, instrumentation, and fusion site.
Verified May 8, 2026 · 5 sources ↓
- Medicare
- $791.60
- Total RVUs
- 23.7
- Global, days
- 90
- Region
- Spine
Documentation requirements
What must appear in the operative or office note to support the claim.
Source · Editorial brief grounded in 5 cited references ↓
- Operative note must identify the specific spinal level(s) explored by name and anatomic location
- Findings at the fusion site must be documented — bone graft incorporation status, hardware integrity, evidence of pseudarthrosis or hardware failure
- If billed same-day with another spinal procedure, the note must establish that the exploration occurred at a distinct anatomic level to support modifier 59
- Anesthesia type and intraoperative imaging use (e.g., fluoroscopy) should be recorded
- Clearly state that no new fusion, arthrodesis, or full hardware revision was performed — or bill the appropriate revision codes instead
- Preoperative indication must document why stand-alone exploration was medically necessary (e.g., suspected pseudarthrosis, persistent pain, hardware concern)
Applicable modifiers
Modifiers commonly billed with this code.
Source · AMA CPT modifier descriptors · CMS NCCI Policy Manual
What this code covers
Source · Editorial summary grounded in 5 cited references ↓
CPT 22830 covers a stand-alone surgical exploration of a prior spinal fusion — the surgeon reopens the fusion site, inspects hardware (screws, rods, plates), evaluates bone graft incorporation, and documents findings. The procedure is performed under general anesthesia, typically with intraoperative fluoroscopy, and is distinct from incidental inspection done as part of another spine procedure at the same level.
The single most important billing rule for 22830: NCCI policy prohibits reporting it with another spinal procedure performed in the same anatomic area. If the exploration occurs at a different spinal level than the concurrent procedure, modifier 59 supports separate reporting — but you need the operative note to clearly identify distinct anatomic regions. If the exploration leads to hardware removal, bone graft revision, and a new fusion, the procedure is no longer exploratory; bill the definitive revision codes instead.
The 90-day global period means any post-op visits, wound checks, and routine follow-up related to the exploration are bundled through day 90. An E/M visit the day before surgery is included; the day-of pre-op evaluation is included. Unrelated problems seen during the global window require modifier 24.
RVU & reimbursement
Component RVUs and Medicare national rate. Actual payment varies by GPCI locality.
Source · CMS Physician Fee Schedule, RVU26A · January 2026
| Work RVU | 10.94 |
| Practice expense RVU | 9.42 |
| Malpractice RVU | 3.34 |
| Total RVU | 23.7 |
| Medicare national rate | $791.60 |
| Global period | 90 days |
Payment by site of service
Medicare pays different rates by setting. HOPD typically pays substantially more than ASC for the same procedure.
Source · CMS OPPS Addendum B·ASC HCPCS payment rates·2026
| Setting | Medicare rate (national) |
|---|---|
Office (PFS non-facility) Procedure performed in physician's office | $791.60 |
HOPD (APC 5114) Hospital outpatient department | $7,413.38 |
ASC (PI J8) Ambulatory surgical center (freestanding) | $5,013.96 |
Common denial reasons
The recurring reasons claims for CPT 22830 get rejected.
Source · Editorial brief grounded in CMS NCCI edits, AAOS coding appeals, and cited references ↓
- NCCI bundling — 22830 denied when billed with another spinal procedure at the same anatomic level without modifier 59 and supporting documentation of distinct levels
- Downcoded or denied when the operative note describes findings that evolved into hardware removal and new fusion, making the procedure a revision rather than exploration
- Medical necessity denial when preoperative documentation doesn't establish a specific clinical reason for stand-alone exploration separate from a planned adjacent-level procedure
- Global period conflict — 22830 billed during the post-op global of a prior spinal procedure without modifier 79 (unrelated) or 78 (related return to OR)
- Missing modifier 59 when billed same-day with adjacent-level spinal surgery, resulting in automatic bundling by the payer
Frequently asked questions
Source · Generated from the editorial pipeline, verified against 5 cited references ↓
01Can 22830 be billed with another spinal fusion code on the same day?
02What happens if the exploration turns into hardware removal and a new fusion?
03What modifier do I use if 22830 is performed during the global period of a prior spinal surgery?
04Is 22830 typically performed in a hospital or ASC setting?
05Does 22830 have a global period, and what does that include?
06Can a PA or NP bill as assistant-at-surgery on 22830?
Sources & references
Editorial content was developed using the following public sources. Last verified May 8, 2026.
- 01CMS Physician Fee Schedule 2026
- 02selecthealth.orghttps://selecthealth.org/content/dam/selecthealth/Provider/PDFs/policies/medical-coding-reimbursement/cr-21-exploration-of-spinal-fusion-with-other-surgery.pdf
- 03findacode.comhttps://www.findacode.com/newsletters/ama-cpt-assistant/musculoskeletal-system-22612-22830-qa-9.html
- 04aapc.comhttps://www.aapc.com/codes/cpt-codes/22830
- 05cms.govhttp://cms.gov
Mira AI Scribe
Mira's AI scribe captures the explored spinal level by name, hardware inspection findings (screw loosening, rod fracture, graft incorporation status), intraoperative imaging used, and the surgeon's conclusion — specifically whether the procedure remained exploratory or converted to revision. This prevents the most common audit flag: an operative note that says 'fusion site was inspected' without documenting distinct level, findings, and decision-making that justify a stand-alone 22830 versus bundling into an adjacent procedure.
See how Mira captures CPT 22830 documentation