How Does Medical Device Reimbursement Work? The Coding–Coverage–Payment Primer

2026-07-15 · Caduvo Team

Medical device reimbursement rests on three pieces: coding, coverage, and payment. This primer explains how that framework works, who decides each part, and why reimbursement strategy must begin before design freeze.

Your device delivers clear clinical gains in a controlled study. Yet the hospital’s value analysis committee kills the pilot because nobody can tell them how—or if—it gets paid. That failure happens when reimbursement strategy gets pushed to the pre-launch checklist instead of shaping the product design from the start.

Medical device reimbursement in the US rests on three pieces: coding, coverage, and payment. If one is missing, the device won’t generate revenue. This guide explains that framework, who decides each part, and why the first reimbursement conversation should happen before the first design freeze.

The three-legged stool: coding, coverage, payment

You can’t get paid without a code. You won’t get paid unless the payer covers the service or item. And coverage alone is worthless if the payment rate is too low to justify adoption. The pieces are sequential in logic but not in time—work on all three must begin early and overlap.

Medicare sets the pace for much of this. Commercial insurers often follow Medicare’s coding and coverage signals, so starting with Medicare medical device reimbursement is practical for most device makers.

Step 1: Assign the right code

A new device usually needs either a CPT code (for procedures) or an HCPCS Level II code (for products, supplies, and durable medical equipment). Understanding the difference matters because the code type determines the claims infrastructure. HCPCS vs CPT codes explains when each applies.

CPT Category I codes describe established procedures. If your device enables a new surgical approach, you’ll likely need a Category III code first—a temporary tracking code that allows data collection but rarely triggers coverage or payment. Transitioning from Category III to Category I requires volume and published evidence, a multi-year effort.

HCPCS Level II codes cover DME, supplies, and some diagnostic products. The process runs through the Pricing, Data Analysis, and Coding (PDAC) contractor for DME, or through a national HCPCS workgroup. Without a code, you cannot submit a claim. Early code mapping should be part of the device’s feasibility phase, not the commercial launch plan.

Step 2: Secure coverage

A code opens the door; coverage decides whether the payer will walk through it. Medicare coverage comes in three layers:

Searching the Medicare Coverage Database for NCDs and LCDs that affect your target procedure reveals evidence gaps and coverage restrictions before you design a clinical trial. Commercial payers maintain their own medical policies but routinely mirror Medicare’s logic.

Non-coverage is often the default for new technology. Payers want proof that the device improves outcomes in the intended population, not just that it’s safe. Generating that proof starts with endpoints that matter to payers—cost avoidance, hospital days saved, reduced readmissions—not just technical performance.

Step 3: Understand payment

Once a code is covered, a payment rate is assigned. The setting determines how the money flows:

A DRG-packaged surgical implant that adds $1,200 in supply cost without reducing length of stay or complications will face headwinds in the value analysis committee. If your device is DME, a low fee-schedule rate can kill a business case. The payment model must be factored into design choices—disposable versus reusable, in-clinic versus in-home use, procedure versus device-only code.

Why medical device reimbursement strategy starts before design freeze

Waiting until after FDA clearance to ask “how do we get paid” is a predictable path to a no from hospital buyers. Reimbursement requirements should shape the development plan.

In short, how does medical device reimbursement work? It works only when you treat coding, coverage, and payment as design inputs, not launch tasks.

A reimbursement checklist for early-stage device teams

Key takeaways

Related reading