Our complete vascular surgery guide

Lower extremity revascularization coding: the 2026 restructure.

2026 deleted the entire 3722037235 range and replaced sixteen codes with forty-six — 37254 through 37299 — organized by vascular territory and split by lesion type. If your charge master, superbill, or scrubber rule still points at the old codes, every affected claim is denying on code validity before a payer ever looks at medical necessity. This guide breaks the restructure down territory by territory: what changed, the hierarchy rule that decides which single code to bill, what's bundled into the base code, and the cleanup your revenue cycle team needs to run before the next batch of claims goes out.

Key takeaways

  • 37220–37235 no longer exist. Any charge path still pointing at them denies on invalid code, not medical necessity — and that denial isn't appealable, it's a corrected-claim problem.
  • Bill the single highest-ranking intervention per territory, not each component. Angioplasty is the base tier; stent and atherectomy each outrank it; a combined stent-and-atherectomy in the same territory outranks either alone.
  • Access, lesion crossing, imaging of the treated vessel, and closure are bundled into the base code — they are never separately billable add-ons to the same intervention.
  • The exact code-to-intervention crosswalk within each territory needs CPT 2026 Professional Edition verification — this build could not open the AMA's copyrighted text directly, and neither should your scrubber rule rely on an unverified secondary source. See the flag below before you build a rule on it.

The 2026 restructure, territory by territory

The old 3722037235 range covered three territories — iliac, femoral-popliteal, and tibial-peroneal — with sixteen codes total. The 2026 replacement adds a fourth territory that didn't exist as its own category before, and nearly triples the code count.

2026 lower extremity revascularization code ranges by territory. Range boundaries cross-checked against multiple industry coding sources (ACC Coding Corner, SIR coding guidance, MedAxiom); code counts below are simple arithmetic on those boundaries, not an independent claim about intervention structure.
TerritoryCode rangeCodes in rangeNotes
Iliac37254372629Common and external iliac artery interventions
Femoral/popliteal372633727917Largest single territory by code count
Tibial/peroneal372803729516Below-the-knee runoff vessels
Inframalleolar37296372994New territory for 2026 — did not exist as a separate category under the deleted codes; the narrow code count suggests a smaller intervention/lesion-type matrix than the other three territories, not the full grid

Two structural rules apply within every territory. First, straightforward (stenosis) and complex (occlusion) lesions are split into different codes — the same intervention performed on a stenosis and on an occlusion in the same territory is not billed the same code. Second, most territories carry the same primary-code logic that existed under the old code set: a code for the first vessel treated, and where the territory supports more than one treatable vessel in a single session, an add-on code for each additional vessel treated through the same access. That add-on structure was not uniform across all three territories in the deleted code set — iliac and tibial/peroneal had it, femoral/popliteal generally did not, because that territory is normally treated as a single vessel run — and nothing in the sourcing for this page confirms whether the 2026 set kept that same asymmetry or extended add-on coding to every territory including the new inframalleolar one. Confirm the add-on availability per territory in your codebook before assuming it mirrors the old pattern everywhere.

The hierarchy rule: what to bill when more than one intervention happens

This is the single rule that decides the most claims, and it hasn't changed in substance from the deleted code set — it's just been carried forward into more codes. For a given territory and lesion type, bill the one code that reflects the highest-ranking intervention actually performed, not each component separately.

The practical failure mode: a coder sees "atherectomy" and "stent" both documented in the operative note and bills two codes, or sees "angioplasty" mentioned as part of lesion preparation and adds a third line for it. All three findings in that note usually map to one combined code in the appropriate territory and lesion-type range — billing them separately is an unbundling error a payer's own edit logic is built to catch, not a legitimate way to capture extra work.

What's bundled into the base code

Consistent with how CPT has historically structured endovascular intervention codes, four things are included in every LER base code and are never separately billable against the same intervention:

What's not automatically bundled: a therapeutic intervention in a genuinely separate territory during the same session, a distinct diagnostic angiogram of a different vascular bed not used to guide the billed intervention, and access obtained at a separate site for a clinically distinct reason. Each of those can be separately reportable, but only with documentation that supports the distinction and, where an NCCI edit pair applies, only where the modifier indicator on that specific pair allows an override at all — see the NCCI note below before appending anything.

Worked coding scenarios

Worked scenarios applying the territory and hierarchy rules above. Specific code numbers within each range are intentionally not asserted here — see the verification flag below.
ScenarioWhat to bill
Femoropopliteal chronic total occlusion, treated with atherectomy followed by stent placement in the same sessionThe single combined stent-and-atherectomy, complex-lesion code in the femoral/popliteal range (3726337279) — not separate atherectomy and stent lines
Same session, same patient: a focal iliac stenosis also treated with angioplasty aloneA second code from the iliac range (3725437262) for angioplasty of a stenosis. Append XS (separate structure/territory) if the NCCI modifier indicator on that specific pair allows an override, and document each territory and lesion separately in the operative note
Tibial/peroneal territory, two distinct vessels (e.g. anterior and posterior tibial) each treated with angioplasty through the same accessThe primary tibial/peroneal angioplasty code for the first vessel, plus the territory's add-on code for the second vessel — if that territory's add-on structure has been confirmed against the current codebook
A charge master or scrubber rule maps "PTA, lower extremity" to a legacy code such as the old femoral-popliteal angioplasty codeNothing bills correctly. The claim denies on invalid code before medical necessity is ever evaluated — this is a systems fix, not a clinical one; see the cleanup checklist below

Charge master and scrubber cleanup

This is the single most preventable source of denied LER revenue through the rest of 2026, and it has nothing to do with clinical documentation. Any charge path — superbill line, EHR order set, charge master entry, or scrubber rule — still pointing at 3722037235 generates an invalid-code denial on every claim it touches.

Do
  • Audit every LER-adjacent charge path — EHR order sets, superbill lines, scrubber rules — against the 2026 code set before the next batch goes out, not after the first denial batch comes back.
  • Map each new charge line to territory and lesion type explicitly, not to a generic "PTA" or "stent" description that a coder has to interpret.
  • Confirm the individual code-to-intervention assignment within each territory against the CPT 2026 Professional Edition before finalizing a scrubber rule.
  • Re-train coders on the hierarchy rule specifically — the failure mode here is usually habit (billing three lines the way the old codes sometimes required), not unfamiliarity with the new ranges.
Don't
  • Don't leave a legacy code live anywhere in the charge path "just in case" — a deleted code doesn't fail gracefully, it denies outright.
  • Don't bill angioplasty separately when it was performed as vessel preparation for a stent or atherectomy in the same territory, same session.
  • Don't assume the complex-lesion code requires 100% occlusion — that specific threshold isn't confirmed against a primary AMA source; see the FAQ below.
  • Don't wait for a denial batch to discover the scrubber wasn't updated — audit proactively.

Medical necessity: ICD-10 specificity that supports intervention

LER is performed for symptomatic peripheral arterial disease, and the diagnosis on the claim has to reflect the severity that justified an invasive intervention rather than conservative management — an unspecified atherosclerosis code alone rarely supports it. All codes below were validated live against the FY2026 ICD-10-CM code set.

PAD severity coding that supports LER medical necessity, verified live against the FY2026 ICD-10-CM code set. All codes below confirmed billable for HIPAA transactions.
SeverityRight legLeft legBilateral
Intermittent claudicationI70.211I70.212I70.213
Rest painI70.221I70.222I70.223
Ulceration (ankle, as an example site)I70.233I70.243site-specific codes exist by laterality, not as a combined bilateral code — see the full I70.2 hierarchy
GangreneI70.261I70.262I70.263

A claudication-only diagnosis supports a conservative-management trial and, once documented as failing, a straightforward intervention; rest pain, ulceration, or gangrene — the clinical picture generally described as chronic limb-threatening ischemia — supports urgent or complex intervention more directly and is usually what closes the gap on a payer's medical necessity review for a complex-lesion code. Document the specific severity level in the office note and the operative note both, not just one or the other.

NCCI edits and MUE caps in LER

Two values decide whether a bundling denial in this code family can be appealed at all: the NCCI modifier indicator on the specific code pair, and the MUE Adjudication Indicator (MAI) on the specific code. An indicator of 0 on a pair means no modifier overrides it, full stop; an indicator of 1 means an NCCI-associated modifier can override it, but only with documentation that the second service was genuinely separate. An MAI of 2 is an absolute unit cap with no appeal path; an MAI of 3 can be appealed with documentation. Where this shows up most in LER: a primary territory code and that same territory's add-on code, and a primary intervention code paired against a separate diagnostic angiography code for the same vessel.

⚠️ On specificity: this build could not open CMS's primary NCCI PTP edit file or the NCCI Policy Manual directly to confirm the specific modifier indicator or MAI value for any individual LER code pair (CMS's site returned an access error to automated fetch attempts made while researching this page) — treat every pair discussed above as reported-but-unconfirmed and verify the current indicator and MAI in the CMS NCCI PTP Edits Lookup Tool before building any of it into a scrubber rule. These values change quarterly.

Still billing 37220–37235 anywhere in your workflow?

We'll audit your LER charge paths and scrubber rules against the 2026 code set, flag every legacy reference, and show what's been denying on code validity before it ever reached medical necessity review.

Book a free claims review

Frequently asked questions

What happened to CPT codes 37220 through 37235, and why are claims still denying?

They were deleted for 2026 and replaced with 46 new codes, 37254 through 37299, organized by vascular territory and lesion type. Claims still denying under the old codes are denying on code validity, not medical necessity, which means the fix is entirely upstream: the charge master, superbill, and claims scrubber all still have to be remapped to the new territory-and-lesion-type ranges before the next batch goes out. A denial for an invalid code is not appealable in the normal sense — it's a corrected claim, and every day the scrubber isn't fixed is another batch of denials from the same root cause.

How do I know whether to bill angioplasty, stent, atherectomy, or the combined code for a lower extremity intervention?

Bill the single code that reflects the highest-ranking intervention actually performed in that territory, not each component separately. The hierarchy runs angioplasty at the base, stent and atherectomy each above plain angioplasty, and a combined stent-and-atherectomy in the same territory above either alone. If atherectomy was performed to prepare the vessel and a stent was then placed in the same territory during the same session, that's the single combined code for that territory and lesion type — not an atherectomy code plus a stent code plus an angioplasty code for the balloon work that happened along the way.

Does the new complex LER code require 100% occlusion?

Not according to CPT's own framing, which distinguishes a stenosis (straightforward) from an occlusion (complex) without specifying a 100% threshold. Some industry material describes the complex code as applying "only to 100% total occlusion," but that specific numeric threshold could not be confirmed against a primary AMA source while building this page, so treat it as an oversimplification rather than a coding rule. Confirm the operative definition of occlusion your coders should apply against the CPT 2026 Professional Edition before writing it into a coding policy, and have the operative note document the lesion as occlusive or stenotic in the surgeon's own words rather than relying on a percentage alone.

Verify before billing. CPT is a registered trademark of the American Medical Association; codes here are paraphrased, not reproduced from the CPT Professional edition. CPT, HCPCS and ICD-10 codes, coverage policy, and bundling edits change, including annual code-set updates. This page reflects standard industry practice and is provided for general education — it is not a substitute for your own compliance review, your current payer contracts, or the current-year code sets. Confirm requirements against your specific payer mix before submitting claims.

Related resources