NCCI edits and MUE limits in vascular surgery.
Most vascular surgery content stops at naming a bundled pair qualitatively — "duplex studies bundle together," "the fistulogram is included in the intervention" — without ever stating the actual value that decides whether a modifier can legally clear the edit, or whether a unit-cap denial can be appealed at all. Two CMS values answer both questions, and this guide walks through them against the specific pairs that generate the most denied and underpaid vascular claims: dialysis circuit stacking, same-day duplex conflicts, and LER territory bundling.
Key takeaways
- The NCCI modifier indicator (0, 1, or 9) decides whether an override is even legally possible — before documentation quality ever enters the conversation. A 0 means no modifier changes the outcome, full stop.
- The MUE Adjudication Indicator (1, 2, or 3) decides whether a unit-cap denial can be appealed at all. MAI 2 never can be, regardless of how well the excess units are documented.
- Dialysis circuit stacking — billing 36901 alongside 36902 or 36903, or 36904 alongside 36905 or 36906 — is the single most common vascular NCCI denial, because the family is additive by design, not a set of independent services.
- Every specific indicator and MAI value cited in this guide is flagged for primary-source verification — CMS's own NCCI and MUE files returned access errors to every automated retrieval attempt made researching this page, so confirm each pair yourself before it goes into a scrubber rule.
How the NCCI modifier indicator and MAI actually work
Two separate CMS mechanisms control vascular surgery's bundling and unit-cap denials, and they answer two different questions. The NCCI modifier indicator governs whether a Column 1/Column 2 code pair can ever be unbundled with a modifier. The MUE Adjudication Indicator governs whether exceeding a per-code, per-day unit cap can be appealed at all. Neither is a judgment call — both are specific values CMS publishes and updates quarterly.
The NCCI modifier indicator attached to a Column 1/Column 2 code pair:
- 0Never bypassable. No modifier, however well-documented, overrides it. If the pair carries a 0, the second code simply isn't separately payable, full stop — don't spend staff time drafting an appeal.
- 1Bypassable with documentation. An NCCI-associated modifier (59 or the specific X-modifier) can override the edit, but only where the record shows the second service was genuinely separate — separate territory, separate session, separate structure.
- 9Edit deleted. The pair no longer applies; the indicator itself is not meaningful going forward, though the code pair may still be re-added in a future quarterly update.
The MUE Adjudication Indicator (MAI) attached to a per-code, per-day unit cap:
- 1Claim-line edit. Units above the cap deny that line, but a genuinely repeated intervention or bilateral procedure can often be split across separate lines with the correct laterality modifier and documentation.
- 2Absolute, date-of-service edit. CMS treats exceeding it as clinically implausible for any single date of service, and adjudication sums units across all lines reporting the code that day, regardless of which modifier is attached to each line. There is no appeal path — confirm the MAI before staff spend time writing one.
- 3Appealable, date-of-service edit. A real path exists with documentation showing the excess units reflect genuinely distinct territories or sessions, not a duplicate order.
The MAI 2 date-of-service mechanism is worth calling out specifically for vascular surgery, because it's easy to assume a laterality modifier automatically protects a bilateral claim from a unit cap. It doesn't, for a code where CMS's adjudication sums units across the whole date of service rather than line by line — RT and LT on two separate lines can still trip a date-of-service MUE if the code's MAI is 2 or 3, because the cap looks at total units billed for that code on that date, not at how many lines it's split across. Confirm the specific code's MAI before assuming a bilateral claim is automatically safe.
Dialysis access circuit stacking
This is the most common and most avoidable NCCI denial pattern in the specialty, because the dialysis access family (36901–36909) is built as an additive hierarchy, not a menu of independent services.
| Code pair billed together | Why it bundles | Modifier indicator (reported industry value) |
|---|---|---|
36901 + 36902 | 36902 already includes the diagnostic fistulogram, needle/catheter introduction, and imaging guidance described by 36901 | ⚠️ Industry billing sources describe this pair as a routine Column 1/Column 2 bundle; this build could not confirm the specific indicator value against CMS's primary NCCI file |
36901 + 36903 | 36903 already includes everything in both 36901 and 36902 | ⚠️ Same status — reported as bundled, specific indicator unconfirmed against primary source |
36904 + 36905 | 36905 already includes the base thrombectomy work described by 36904 | ⚠️ Same status |
36904 + 36906 | 36906 already includes everything in both 36904 and 36905 | ⚠️ Same status |
The practical rule that holds regardless of the exact indicator value: bill the single highest code in the hierarchy that reflects what was actually performed for that access on that date, not the base code plus the therapeutic code. The one legitimate exception is a genuinely separate access site or a diagnostic-only encounter that didn't proceed to intervention — in that case 36901 stands alone, appropriately, because there's no higher-tier code to bundle it into. Where a modifier 52 (reduced services) situation applies — imaging interpreted through an existing catheter rather than a fresh percutaneous access — that's a separate billing decision from the stacking question above, not a way to unbundle the additive hierarchy.
Arterial and venous duplex same-day conflicts
The vascular lab's highest-volume same-day bundling question is whether an arterial study and a venous study of the same extremity, ordered together, are separately payable.
| Pair | Typical pattern | When it's defensible to bill both |
|---|---|---|
Lower extremity arterial (93925/93926) + lower extremity venous (93970/93971), same leg, same date | Routine Column 1/Column 2 pattern when ordered as one combined "vascular workup" without two distinct indications | Two independently documented indications — e.g. claudication workup plus a separate suspected-DVT presentation — with XS appended and each indication stated in the order |
Extracranial cerebrovascular (93880/93882) + upper extremity arterial (93930/93931), same date | Different vascular beds; generally more defensible as separately payable than same-extremity arterial/venous pairs, but still worth confirming the specific pair's indicator | Genuinely separate clinical indications for each territory, documented independently |
Complete bilateral duplex code (e.g. 93925) + the limited/unilateral code in the same family (93926) for the contralateral or a repeat limited look, same date | Rarely appropriate — billing both the complete and the limited code for overlapping scope on the same date is a common MUE and bundling trigger, not two legitimate services | Only when the limited study addresses a genuinely separate, later clinical question the complete study didn't answer, clearly documented |
⚠️ As with the dialysis access pairs above, this build could not confirm the specific modifier indicator values for these duplex pairs against CMS's primary NCCI PTP file (the CMS Coverage Database and NCCI files returned access errors to automated retrieval attempts made researching this page and the vascular surgery pillar guide). The bundling patterns described are consistent with standard industry billing guidance and CPT's own component structure, but treat every indicator value as reported-but-unconfirmed until checked in the CMS NCCI PTP Edits Lookup Tool.
LER primary-vs-add-on pairs
The 2026 lower extremity revascularization restructure (37254–37299) creates two distinct bundling questions that are easy to conflate but resolve differently.
- 1Same territory, same session — a CPT hierarchy rule, not an NCCI edit. When angioplasty is performed as vessel preparation for a stent or atherectomy in the same territory, that's not two separately billable services needing a modifier override; it's a single procedure reported with the one code that reflects the highest-intensity intervention actually performed. Billing the angioplasty code separately alongside the stent code in the same territory is an invalid-combination error, not a bundling denial to appeal.
- 2Same territory, base code plus a separate diagnostic angiogram of the same treated vessel. Percutaneous access, diagnostic angiography needed to guide the intervention, lesion crossing, and closure of the access site are bundled into the base LER code. Reporting a separate angiography code (e.g. from the
75710family) for the same vessel the same session is a routine Column 1/Column 2 bundle. ⚠️ Reported as a 0 (non-bypassable) indicator by standard industry coding guidance for access/diagnostic-imaging-inclusive intervention codes generally; this build could not confirm that specific value for the 2026 LER codes against CMS's primary file, since the codes are new for 2026 and this build could not open the current NCCI PTP file directly. - 3Different territory, same session (e.g. iliac plus femoropopliteal, same leg). These are separate codes for separate anatomic territories, and a genuine NCCI edit may or may not exist between specific territory-pair codes. Where one does, it's the kind of edit most likely to carry a 1 (bypassable) indicator, since the territories are anatomically distinct — XS is the right modifier, with each territory and lesion documented separately in the operative note.
- 4Same territory, contralateral leg, same session. Distinguished by RT/LT rather than by an X-modifier in most cases, since the laterality modifier itself establishes the services are on different anatomic sides. Confirm the specific code's MAI (not just the modifier indicator) before assuming a bilateral claim clears automatically — see the date-of-service MUE mechanism above.
The fallout for revenue cycle teams building scrubber rules against this family: don't write a single blanket rule that treats every same-session LER pairing the same way. A same-territory angioplasty-plus-stent pairing needs to collapse to one code before the claim goes out; a genuinely different-territory pairing needs the correct X-modifier and documentation; a bilateral same-territory pairing needs the correct laterality convention and, separately, a check against the code's MAI.
1) Confirm the exact two CPT codes actually billed together, not a paraphrased version of them. 2) Look up the NCCI modifier indicator for that specific pair in the CMS NCCI Procedure-to-Procedure Edits Lookup Tool — if it's 0, stop, there's no appeal to write. 3) If it's 1, confirm the operative note or study report independently documents the anatomic distinction (territory, structure, or side) that justifies the modifier. 4) Separately, look up the MUE and its MAI for any code that also hit a unit cap — if MAI 2, stop again, regardless of how the modifier question resolved. 5) Only draft the appeal once both checks clear, citing the specific indicator and MAI values by name, not "per CMS guidelines" generically.
Do and don't
- Check the modifier indicator for a pair before appending 59 or an X-modifier, every time, not just on claims that already denied.
- Bill the single highest code in an additive hierarchy (dialysis access, LER same-territory intervention) rather than the base code plus the therapeutic code.
- Check a code's MAI separately from its modifier indicator — they answer different questions and a bilateral modifier doesn't automatically clear a date-of-service unit cap.
- Document each territory, structure, or side independently in the operative note or study report before relying on it to support a modifier.
- Don't bill 36901 alongside 36902 or 36903, or 36904 alongside 36905 or 36906, for the same access on the same date.
- Don't write an appeal against a unit-cap denial before confirming the MAI — an MAI 2 denial has no appeal path regardless of documentation quality.
- Don't assume an X-modifier fixes every bundling denial — if the pair's indicator is 0, no modifier changes the outcome.
- Don't treat a same-territory angioplasty-plus-stent pairing as an NCCI bundling question — it's a code-selection hierarchy rule, and the fix is picking one code, not appending a modifier.
Losing vascular surgery revenue to bundling and unit-cap denials?
We'll audit a sample of your recent claims, confirm the actual NCCI and MUE values behind your denials, and show what's recoverable versus what isn't.
Frequently asked questions
Can 36901 ever be billed alongside 36902 or 36903 the same session?
No, not for the same access on the same date. The dialysis access family is additive: 36902 already includes the diagnostic fistulogram work described by 36901, and 36903 already includes everything in both 36901 and 36902. Billing 36901 on the same claim as 36902 or 36903 for the same access reports work that's already paid for inside the higher code, and it denies as bundled. The only scenario where a diagnostic study is separately reportable is a genuinely distinct access or a separate, later encounter that didn't lead to an intervention that same session.
Is an arterial and venous duplex of the same leg on the same day ever separately payable?
It can be, but it's the exception rather than the default, and it depends on two things: whether the code pair's NCCI modifier indicator allows an override at all, and whether the order documents two independently necessary clinical indications, not one combined vascular workup. A patient worked up for both claudication and suspected DVT in the same leg is a defensible case for XS; a routine "vascular survey" order covering both without two distinct reasons is not. Check the specific pair's indicator before billing both, and don't assume the override is automatic just because the clinical picture seems to justify it.
How do we know if a unit-cap denial on an LER code is even appealable?
Look up the MUE Adjudication Indicator, or MAI, for the specific code before doing anything else. MAI 1 is a claim-line edit and a genuinely repeated or bilateral intervention can often be split across separate lines with the correct laterality modifier. MAI 2 is an absolute date-of-service edit that CMS treats as clinically implausible — there is no appeal path, and writing one is wasted staff time. MAI 3 is a date-of-service edit that can be appealed with documentation showing the excess units reflect genuinely distinct territories or sessions. Confirm the MAI in the CMS MUE files before your team spends time on an appeal that MAI 2 makes impossible to win.
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.
Sources and verification
NCCI modifier-indicator and MUE Adjudication Indicator definitions are stated with confidence as CMS policy structure, consistent with how they're described in this site's cardiology and vascular surgery pillar content. Specific indicator and MAI values for the individual vascular code pairs named in this guide — the dialysis access family, the duplex same-day pairs, and the 2026 LER territory pairings — could not be confirmed against CMS's primary NCCI PTP and MUE files during this build; the CMS Coverage Database and NCCI file pages returned access errors to every automated retrieval attempt made researching this page. Every specific value above is flagged inline as reported-but-unconfirmed and should be checked in the CMS NCCI Procedure-to-Procedure Edits Lookup Tool and the current MUE files before being relied on operationally, since these values change quarterly. No Medicare Physician Fee Schedule dollar amounts are published in this guide.