ASC Billing Services / Case Study

The device money was on the claim. It just was not on the check.

A multispecialty ASC was billing device-intensive procedures cleanly and still leaving the protected implant portion behind, because its rates never reflected the CMS CY2026 device offset.

CY2026 OPPS/ASC Final Rule Device-Intensive Methodology 30% Offset Threshold ASCQR Program

Audit our device-intensive lines → ASC billing services

One device-intensive procedure

Illustrative worked example built from the CMS device-offset method. Dollar figures shown for illustration only.

Full OPPS payment (reference)$10,000

device 62%

service 38%

Billed as ordinary ASC line$8,500

everything scaled ×0.85

short

Billed device-intensive (correct)$9,430

device paid in full

service ×0.85

Device portion (offset) Service portion Silent under-collection

30%Device-cost share that flips a procedure into "device-intensive" under CMS methodologyOffset threshold

100%Of the device offset amount paid to the ASC unscaled, not reduced by the ASC-to-OPPS ratioPayment protection

31%Default device offset CMS applies to a device-intensive code that has no claims data yetNew-code default

2.0Percentage-point payment cut for ASCs that miss ASCQR reporting, on top of any device leakASCQR penalty

The short answer

Device-intensive procedures pay differently. If your rate table does not know that, you under-collect quietly.

For a device-intensive procedure, CMS does not scale the whole payment down by the usual ASC-to-OPPS ratio. It pays the device offset portion in full and scales only the remaining service portion. Miss the device-intensive designation, or let a stale charge master treat the line as ordinary, and the unscaled implant dollars never land, even when the claim itself is clean. The fix is not appeals. It is rebuilding the device-intensive rate logic against the CMS Calendar Year 2026 OPPS/ASC Payment System Final Rule and its device-offset file, then reconciling every implant line to it.

What counts as device-intensive

A procedure whose device cost is at least 30% of its mean cost. CMS assigns each one a procedure-specific device offset percentage, published in the CY2026 device-intensive list.

Why the payment is higher

The device offset amount is paid at the full OPPS device value. Only the non-device service portion is scaled by the ASC ratio, so device-intensive lines sit far closer to full OPPS than ordinary ASC lines.

Where credits belong

Modifiers FB (no-cost device) and FC (partial credit), with value code FD, reduce the offset when a device arrives free or credited. Applied when they should not be, they hand back money the ASC earned.

The methodology, step by step

How CMS actually builds a device-intensive ASC payment

Four moves. The leak almost always hides between step 2 and step 3, where a rate table decides whether the device portion gets protected or scaled away.

Confirm the flag

Check the code against the CY2026 device-intensive list. If it carries a device offset percentage, standard ASC scaling does not apply the same way.

Split the payment

Separate the payment into the device offset portion and the service portion using the code's offset percentage.

device% + service% = 100%

Protect the device

Pay the device offset amount in full. Scale only the service portion by the ASC-to-OPPS ratio.

pay = dev + (svc × ratio)

Adjust for credits

Only if the device was free or credited, apply FB / FC and value code FD. No credit, no reduction.

FB/FC only when true

Ordinary line vs device-intensive line

Same claim. Same implant. Two very different checks.

A single illustrative device-intensive procedure with a 62% device offset, shown two ways. The math is CMS methodology; the dollar values are for illustration only.

Line item	Treated as ordinary ASC	Treated as device-intensive
Full OPPS reference	$10,000	$10,000
Device offset portion (62%)	Scaled down with everything else	$6,200 paid in full
Service portion (38%)	Scaled × 0.85	$3,800 × 0.85 = $3,230
ASC payment	$8,500	$9,430
Difference per case	$930 under-collected on every case the rate table treated as ordinary

Illustrative example only. Actual amounts follow each code's published device offset percentage, the CY2026 ASC conversion factor, and the ASC-to-OPPS scaling ratio in the final rule.

Where the ASC was losing it

The leak was upstream of the claim, not in it

The billing team was clean. The clearinghouse was clean. The money was leaving before either of them ever touched the account.

Stale rate table

The charge master carried device-intensive codes at ordinary ASC rates. Nothing in the workflow told it a procedure had a protected device portion, so every line got the same across-the-board scaling.

New codes defaulted low

Recently added device-intensive codes with no claims history should carry the CMS default 31% offset. Instead they were mapped with no offset at all, so the newest, highest-implant procedures leaked the most.

Reflex FB / FC

Device credit modifiers were being appended out of habit on cases where the ASC actually purchased the device at full cost, quietly reducing payments that should have been paid whole.

No reconciliation loop

Remits were posted without ever comparing the paid device portion back to the expected offset. A short payment looked identical to a correct one, so no one flagged it.

The rebuild

A cost-offset rebuild, not a denial project

No new staff, no new clearinghouse. We rebuilt the device-intensive logic so the correct payment was expected, billed, and reconciled from the first pass.

Re-map every device-intensive code

Reconciled the charge master to the CY2026 device-intensive list and its per-code offset percentages, with the 31% default assigned to new codes lacking claims data.

Split-rate expected value

Built an expected-payment calculation that protects the device portion and scales only the service portion, so every device-intensive line has a target to reconcile against.

Gate FB / FC to real credits

Tied device credit modifiers and value code FD to actual invoice and credit evidence, so they fire only when a device was genuinely free or credited.

Post with a variance check

Every remit on a device-intensive line now compares paid device value to expected offset; shortfalls route to rework instead of posting silently.

The ASCQR line no one connects to device money

Under the Ambulatory Surgical Center Quality Reporting (ASCQR) Program, an ASC that misses its reporting requirements takes a 2.0 percentage-point cut to its annual payment update. That reduction lands on the same conversion factor that drives your device-intensive rates, so a compliance miss and a device-offset miss compound. Recovering implant dollars and protecting ASCQR standing are one workstream, not two.

Guidelines referenced

CMS Calendar Year 2026 Hospital Outpatient Prospective Payment System and Ambulatory Surgical Center Payment System Final Rule , annual ASC rate setting and the ASC conversion factor.
Device-intensive procedure methodology and device offset percentages , the 30% device-cost threshold, per-code offset file, and 31% default for codes without claims data.
ASC Covered Procedures List (Addenda AA and BB) and device credit reporting via modifiers FB and FC with value code FD.
Ambulatory Surgical Center Quality Reporting (ASCQR) Program , 2.0 percentage-point reduction to the annual payment update for non-compliant ASCs.

If you do implants, you have a device-offset question worth answering.

We will pull your device-intensive lines against the CY2026 offset file, model the split-rate expected value, and show you exactly where the protected device portion is landing short. No leak, we tell you so. That is the honest version of an audit.

Start a device-intensive review →

ASP-RCM Solutions · ASC Billing Services · Senior Partner, Frisco