Facet, MBB, and RFA coding

This code family pays or denies on a sequence, not a single claim: a diagnostic medial branch block has to happen twice, on separate dates, with documented relief, before radiofrequency ablation is medically necessary at all — and every code in between is billed per joint, not per side or per nerve. Our pain management billing and coding guide covers this family at a summary level; this page works the level-by-level billing, the diagnosis codes that actually clear a payer's coverage check, the unit traps that cost money silently, and the appeal language a two-block denial actually needs.

The code family, by level and region

Facet joint injections, medial branch blocks, and RFA share one billing structure across the family: a primary code for the first level or joint, and an add-on code for each additional one in the same session. The service, not the anatomy, decides which pair applies — injection versus ablation — and the spinal region decides which of the two code pairs within that service.

Two counting rules govern the whole table, and both are easy to get wrong in a way that pays instead of denying. First, "level" for the injection codes and "joint" for the RFA codes both mean one unit per spinal level or joint pair addressed, using the primary code once and the add-on code for each additional one — not one unit per side. Second, and the more expensive mistake: an RFA unit tracks the joint, not the nerve. Every facet joint is innervated by two medial branch nerves, so a complete ablation at one joint denervates two nerves but is still one unit of 64633 or 64635 for that joint. A coder who bills two units of 64636 because two nerves were treated at one level is overbilling, and it's the kind of pattern an MUE audit finds after the fact rather than a scrubber catching it before submission. ⚠️ The current MUE value and its MAI (whether the edit is appealable with documentation) for each code in this family are quarterly CMS figures this build could not open the CMS MUE table directly to confirm — check the Medicare NCCI MUE table by name before building a scrubber rule around a specific unit count.

Non-thermal or pulsed radiofrequency is a distinct modality from the conventional thermal RFA this table describes, and it's a code-selection error to report 64633-64636 for it. Pulsed RF doesn't have a dedicated CPT code in most current fee schedules and, where reportable at all, typically falls to an unlisted procedure code with supporting documentation attached — check current payer policy before performing it, since coverage varies and some payers treat it as investigational regardless of how it's coded.

The two-block requirement, in documentation terms

RFA's medical necessity in this family isn't judged on the ablation note alone — it's judged on two prior, separately dated diagnostic medial branch block sessions at the target level, each with a documented pain reduction and a relief duration consistent with the anesthetic used. A short-acting anesthetic should show relief resolving in hours; a mismatch between the anesthetic used and the relief duration reported is itself a documentation red flag reviewers look for. Medicare's facet joint intervention LCD is published separately by each MAC under its own document ID — Novitas Solutions (LCD L34892, Article A56670, effective 01/05/2026), Palmetto GBA (LCD L38765, Article A58350), CGS Administrators (LCD L38773, Article A58364), WPS (LCD L38841, Article A58477), Noridian (LCD L38801, Article A58403), First Coast Service Options (LCD L33930, Article A57787), and Wellpoint Federal (LCD L35936, Article A57826) — and the structure is consistent across all seven even though the exact relief-percentage threshold is not. ⚠️ Industry and clinical-literature sources describe thresholds ranging from 50% to as strict as 80% depending on the policy version; this build could not open the LCD article text directly to confirm the exact figure your jurisdiction currently requires, so pull your own MAC's current article by the ID above rather than assuming a single percentage applies everywhere.

What doesn't vary by MAC is the shape of the record RFA needs behind it:

• 1Two diagnostic MBB sessions on separate dates, each independently documented — not a single note stating "prior positive blocks" without dates attached.
• 2Relief percentage and duration recorded for each block, matching the anesthetic used at that session.
• 3Level and side named explicitly in both block notes and the ablation note, matching the primary-plus-add-on code structure on the claim.
• 4A region-specific diagnosis code tying the finding to the level treated, not an unspecified or mismatched one (see below).
• 5Thermal approach stated explicitly, since pulsed/non-thermal RF isn't billed under these codes at all.

When an RFA claim denies for lack of medical necessity, the fix is rarely a generic reconsideration letter. The appeal has to attach both diagnostic MBB notes with their dated relief percentages as exhibits, not a sentence in the appeal letter referencing that blocks were "previously performed and documented" — reviewers request the underlying notes independently of what the ablation note claims, and a denial that cites missing medical necessity is almost always actually citing missing documentation of the two blocks, not a real clinical gap.

Diagnosis coding: the specificity payers actually check

Coverage articles for this family gate on a region-specific diagnosis, and "facet syndrome" isn't itself a billable ICD-10-CM code — the coding convention routes through spondylosis without myelopathy or radiculopathy, coded to the region treated. That last part matters clinically as much as administratively: MBB and RFA target the facet joint, not a compressed nerve root, so a code that specifies radiculopathy actually argues against the procedure being performed, not for it.

The trap isn't obscure: an EHR problem list defaults to a generic "spondylosis" or "back pain" entry, the coder bills whatever's on the list, and a claim that would have cleared coverage with the correct region-specific code denies instead. Pull the diagnosis from the exam and imaging findings for the level actually treated, not the EHR's default problem-list entry, every time.

Bilateral and setting: what the claim actually looks like

A same-level bilateral facet procedure is one clinical event described two different ways depending on where the claim originates. On the physician's professional claim, bilateral work at one level is reported as a single line with modifier 50 appended — one unit, not two. On the facility side, an ambulatory surgery center reports the same bilateral procedure as two separate lines using RT and LT instead, because the facility fee schedule prices each side independently. Billing bilateral work as two lines with 50 attached on the professional claim, instead of one line, is a common cause of a claim paying at roughly half the expected rate rather than denying outright — which means it's the kind of error that survives in a fee schedule unnoticed until someone runs a per-procedure revenue reconciliation.

Site of service compounds this: RFA and facet injections performed in an ASC generate two genuinely separate claims — the physician's professional component and the facility's own claim for the procedure suite, equipment, and staff — priced under two different Medicare fee schedules entirely. A physician's office billing a facility-level charge for a procedure actually performed in-office, or an ASC failing to submit its own separate facility claim, both surface as reconciliation problems rather than a straightforward denial, and both are easy to miss without someone actively watching for the second claim that should exist.

Do and don't

Frequently asked questions

Related resources

• Pain management billing and coding guide
• Epidural steroid injection coding
• Spinal cord stimulator billing