CMS’s RAPID Coverage Pathway Leaves Coding and Billing Behind

On August 11, 2026, CMS published a procedural notice (CMS-3487-NC) formally standing up the Regulatory Alignment for Predictable and Immediate Device (RAPID) coverage pathway, a program CMS and FDA first announced jointly on April 23, 2026. The pitch is straightforward: for a defined set of breakthrough medical devices, Medicare can post a proposed national coverage determination (NCD) the same day the FDA grants market authorization. For device makers and patients, that is a genuine acceleration. For coding and revenue cycle teams, it opens a gap that deserves attention now, before the first devices start moving through the pathway.

What the RAPID Pathway Actually Does

RAPID is narrow by design. To qualify, a device must carry FDA Breakthrough designation and sit in the IDE pre-submission stage, with plans to enroll Medicare beneficiaries in the supporting clinical study. Class II devices must be pursuing the De Novo pathway; Class III devices must be pursuing full PMA approval. The device cannot already be governed by an existing controlling NCD, must be billable as a separately payable item, and in vitro diagnostics and laboratory tests are excluded outright.

Full eligibility detail is laid out in CMS’s fact sheet on the notice. For devices that clear those bars, CMS will post a proposed NCD the same day FDA grants authorization, run a 30-day public comment period, and finalize coverage within roughly 60 days for Class II devices or 90 days for Class III devices post-authorization — a fraction of the 9- to 12-month timeline a typical NCD takes today. The procedural notice itself is open for public comment for 60 days from publication, putting that window at roughly October 10, 2026.

Why Coverage Speed Doesn’t Translate to Coding Speed

An NCD is a coverage decision, not a payment mechanism. Nothing in the RAPID notice creates, assigns, or accelerates a HCPCS or CPT code, and nothing in it sets a payment rate. Those processes run on their own separate clocks inside CMS: HCPCS Level II code applications go through their own biannual cycle, and payment rate-setting for new technology add-on payments or device-intensive procedures follows its own rulemaking calendar. A device can clear FDA authorization and receive same-day Medicare coverage under RAPID and still have no billable code, and therefore no clean claim path, for months afterward.

The Two Timelines Don’t Line Up

That mismatch is the operational risk. A hospital or physician practice that starts using a RAPID-covered device as soon as coverage posts may find itself billing with an unlisted or miscellaneous code, appending modifiers to approximate the service, or holding claims until a permanent code exists — each of which carries its own denial and audit exposure. Coding teams that treat an NCD posting as a signal to start normal billing, without separately confirming code and payment status, are the ones most likely to get caught in that gap.

Where This Intersects With an Already-Strained Pathway

RAPID is also arriving as CMS scales back a related program: the Transitional Coverage for Emerging Technologies (TCET) pathway, aimed at a similar breakthrough-device population, has been paused as CMS shifts toward RAPID. Coding and RCM staff who built processes around TCET’s coverage-with-evidence-development structure will need to unlearn some of that and rebuild around RAPID’s same-day NCD model instead — the two pathways are not interchangeable, and provider billing teams should not assume TCET-era workarounds apply.

A Practical Checklist for Coding and RCM Teams

For any RAPID-covered device a provider organization plans to use, coding and revenue cycle staff should confirm the following before the first claim goes out:

• Whether a permanent HCPCS or CPT code exists yet, or whether the claim will need an unlisted/miscellaneous code with supporting documentation
• Whether a payment rate or new technology add-on payment has been established, or whether reimbursement is still pending a separate CMS action
• Whether the NCD is still in its 30-day proposed-comment stage or has been finalized, since coverage terms can shift between the two
• Whether the device falls under a National Coverage Analysis tracking number that should be referenced in documentation for future audit defense
• Whether local MAC guidance has been issued that adds coding or documentation requirements on top of the national NCD

What to Do Before the First RAPID-Covered Claims Arrive

Provider organizations don’t need to wait for a specific device to work through RAPID before preparing. Coding leadership can flag RAPID-eligible technologies now, build a standing process for confirming code and payment status separately from coverage status, and brief clinical documentation and denials-management staff that “covered” does not mean “codeable” under this pathway. Given that the procedural notice is still in its comment period through roughly October 10, 2026, the exact operational details CMS ultimately adopts may still shift — worth tracking directly rather than assuming the current notice is final.

This is the kind of gap that autonomous, rules-aware coding systems are built to catch — flagging when a covered service lacks a finalized code or payment path rather than defaulting to a miscellaneous code and hoping it clears. That’s the layer Medikode’s automated medical coding platform is designed to sit at: catching coverage-to-code mismatches before they become denials.