Guide · Medical Devices

The U.S. medical device reimbursement pathway.

A senior advisor's view of how coding, coverage, and payment actually get built for medical devices in the United States — what sequences matter, where launches stall, and how to plan for a reimbursement environment that is fragmented by design.

By Wellguidant Advisors · Reimbursement, market access, and due diligence for pharmaceutical, medical device, and diagnostic companies.

01 · The reimbursement trifecta

For a U.S. medical device to generate durable revenue, three independent decisions have to line up: a code that identifies the procedure or product on a claim, coverage from payers who agree to pay for it under defined clinical criteria, and a payment rate that reflects real economics. Missing any one of the three collapses the commercial model.

Regulatory clearance is necessary but not sufficient. FDA answers whether a device can be sold. Reimbursement answers whether it can be paid for — and by whom, in which setting, on what terms. The teams that treat these as one workstream tend to arrive at commercialization unprepared for the second and third.

02 · Coding — CPT, HCPCS, and NTAP

Devices show up on claims in several ways. Physician services that use the device are billed with CPT codes maintained by the AMA. Supplies, DME, and many physician-administered products use HCPCS Level II codes maintained by CMS. Inpatient care is grouped into MS-DRGs, and hospital outpatient services are grouped into APCs under OPPS.

The strategic question is rarely "do we have a code" — it is "does the code that exists price our clinical value, and if not, what path changes that?" For a differentiated device that maps into a broad legacy code, the reimbursement can be structurally under-priced for years. Options include pursuing a new Category I CPT code (a multi-year, evidence-intensive process), establishing a Category III CPT code to track utilization during evidence build, or securing a product-specific HCPCS. Inpatient add-on payment through NTAP and outpatient pass-through status are time-limited bridges — they do not solve long-term rate strategy.

03 · Coverage — CMS and commercial payers

Coverage is the payer's decision to pay for a coded service in defined clinical circumstances. In the CMS world, that means National Coverage Determinations (NCDs) and, more commonly for devices, Local Coverage Determinations (LCDs) written by the Medicare Administrative Contractors. The Transitional Coverage for Emerging Technologies (TCET) pathway offers a narrow lane for select breakthrough devices to secure earlier, evidence-linked national coverage.

Commercial payers write their own medical policies, often drafted by the medical director's office and informed by professional-society guidelines, HTA bodies like ICER, and the published evidence base. In practice, commercial coverage is a portfolio game: dozens of policies at national and regional plans, each with distinct evidence thresholds, appeal mechanics, and update cycles. Winning coverage requires a coverage dossier written in the payers' language — clinical validity, clinical utility, comparative effectiveness, and economic impact — not the pitch deck version of the same claims.

04 · Payment — rate setting and durability

Payment rates are set by fee schedule and setting. Physician services follow the Medicare Physician Fee Schedule (MPFS), driven by RVUs and RUC recommendations. Hospital outpatient services follow OPPS via APC assignment. Inpatient care follows the IPPS MS-DRG system. Ambulatory Surgery Centers follow ASC payment rates. Commercial rates negotiate around these anchors.

Two questions drive strategy. First: does the initial rate cover the cost of the device plus the clinical work around it, or does it force the provider to absorb a loss on each case? Second: is the rate durable, or is it a temporary construct (NTAP, pass-through, high-cost outlier) that lapses in twenty-four to thirty-six months? The strongest launch plans model a base rate that persists after the bridges expire and design evidence generation to support the eventual full-rate case.

05 · Site of service and the buy-and-bill wall

A device's site of service — inpatient, hospital outpatient, ASC, physician office, home — determines which fee schedule, which coding pathway, and which purchasing pattern applies. The same device can pencil well inpatient and underwater in the office. Migration across settings (for example, from HOPD to ASC as CMS expands the ASC-payable list) is often the single biggest driver of a device's addressable market.

For physician-administered products, the buy-and-bill model puts working capital and denial risk on the practice. If the reimbursement is uncertain or lags the acquisition cost, adoption stalls regardless of clinical enthusiasm. Access programs — patient assistance, benefits investigation, prior-auth support, and, where appropriate, alternative distribution — are part of the reimbursement plan, not a post-launch afterthought.

06 · Sequencing a launch

Reimbursement work is calendar-driven. Coding cycles take twelve to twenty-four months. Payer medical policies update on quarterly or annual cadences. Society guidelines move slower still. The practical consequence: the reimbursement strategy has to be sequenced backward from launch, typically starting twelve to eighteen months before FDA action.

A workable sequence looks like this:

  • Reimbursement landscape assessment — code options, existing coverage baseline, comparator economics, payer segmentation.
  • Evidence-plan alignment — pressure-test the clinical and economic evidence against payer thresholds while the trial design still allows change.
  • Coding pathway decision — Category III vs Category I CPT, HCPCS, or leveraging existing codes; NTAP or pass-through where it fits.
  • Coverage dossier and payer engagement — MAC engagement, targeted commercial submissions, KOL and society outreach.
  • Rate strategy and site-of-service planning — pricing bands, gross-to-net logic, and setting expansion roadmap.
  • Field readiness — provider economics tools, access hub design, denial-management playbooks.

07 · Where device launches actually stall

The failure modes we see repeatedly are not exotic — they are the predictable result of treating reimbursement as a downstream problem.

  • Assuming an existing code prices the device fairly, then discovering the legacy rate cannot cover acquisition plus clinical time.
  • Building evidence for regulatory endpoints that do not match payer thresholds for clinical utility or economic value.
  • Winning early coverage at one large payer and treating it as a proxy for the market — while the rest of the panel writes divergent policy.
  • Relying on NTAP or pass-through as the base case, without a durable rate story once the add-on expires.
  • Under-resourcing access operations, so approved patients still cannot get the product on time.
  • Delaying commercial-payer engagement until after launch, then absorbing twelve to eighteen months of coverage development in the revenue ramp.

08 · What investors should diligence

For VC, growth equity, and PE teams evaluating a medical device asset, the reimbursement questions that move a valuation are usually the same handful:

  • Which codes carry today's revenue, and are they secure — or are they legacy codes at risk of revaluation or bundling?
  • What is the durable payment rate across settings, once time-limited add-ons expire?
  • How many covered lives sit under favorable medical policy today, and what is the realistic path to expand that base?
  • Is the evidence base aligned with payer expectations for clinical utility and economic value, or is a new study needed to unlock coverage?
  • How dependent is the model on a single site of service, MAC jurisdiction, or payer? What happens if any one moves?

These are the questions our reimbursement due diligence engagements are built to answer on transaction timelines — decision-grade, not exhaustive.

Related work
Working through this pathway?

Talk through your device's reimbursement plan.

Senior, partner-led engagements. Confidential by default.