Our product is a device, not a drug. Does this apply?

The mechanism names differ. Devices have their own transitional pass-through pathway, new technology add-on payments in the inpatient setting, and category codes. The planning problem is the same: approval, coding, coverage, and payment are separate events with separate clocks, and each one reopens commercial decisions.

We have no pass-through or add-on payment path. Is reimbursement still a launch dependency?

Yes. ReSure Sealant is the example inside this article. A product paid inside a bundled procedure payment sells on a clinical and operational case made to a committee, and the site-selection, pricing, and contracting questions all still apply. They are harder, not absent.

Who should own reimbursement on a small team?

One named person, even if it is a fraction of their job. The register of codes, coverage policies, payment status, effective dates, and expiry dates cannot live in a consultant's report. The owner does not need to do the policy work. They need to keep the facts current and trip the reopen triggers.

How early should payment work start?

Ocular filed its pass-through application on the day of FDA approval. The practical rule is that the payment application timeline belongs in the launch plan beside the regulatory timeline, not after it.

One Reimbursement Change, Seven Commercial Decisions

Short answer

A change in coverage or payment does not update one slide in the launch plan. It reopens site selection, price, contracting, hiring, the sales story, evidence, and launch scope, and each of those decisions needs an owner before the change takes effect.

The Dextenza record

On November 30, 2018, the FDA approved Ocular Therapeutix's application for Dextenza, a dexamethasone ophthalmic insert for the treatment of ocular pain following ophthalmic surgery. The same day, the company applied to the Centers for Medicare and Medicaid Services for transitional pass-through payment status.

That sequence is the story. The regulatory event and the payment event were planned as two different milestones on two different clocks.

Dextenza is placed in the canaliculus during or after cataract surgery and releases steroid over about a month. It competes against post-surgical eye drops, which cost little and are familiar to every site. Without separate payment, an ambulatory surgical center would absorb the cost of the insert inside its packaged payment for the cataract procedure. The clinical argument alone would have to carry the full price difference against drops.

In May 2019, CMS approved transitional pass-through payment status for Dextenza and established a temporary billing code, C9048, effective July 1, 2019. Ocular commercially launched Dextenza in July 2019. A permanent J-code, J1096, followed, effective October 1, 2019, and the temporary code retired. The company's 2020 annual report said it expected pricing during pass-through of approximately $538 per insert, paid separately from the surgery.

The commercial plan tracked the payment structure. The company built what it described as a highly targeted, key account sales force focused on the ambulatory surgical centers responsible for the largest cataract surgery volumes, with an initial emphasis on the roughly two million cataract procedures performed annually under Medicare Part B. Product moved through a network of specialty distributors that resold to surgical centers and hospital outpatient departments. In December 2020, the company reported in-market unit sales of 4,198 billable inserts for October 2020 and 4,327 for November 2020.

Net revenue from Dextenza grew from $2.2 million in 2019 to $15.7 million in 2020, $42.0 million in 2021, and $50.5 million in 2022.

The payment was never a settled fact. Pass-through status is temporary by statute, no more than three years. The company's 2020 annual report stated plainly that Dextenza was scheduled to lose pass-through status in July 2022, and that if it lapsed without replacement, the product would no longer be reimbursed separately from the surgery and revenue would be adversely affected. In November 2021, CMS rulemaking indicated Dextenza would be paid separately in surgical centers and hospital outpatient departments through 2022 despite the scheduled loss. After pass-through ended, Dextenza kept separate payment in the surgical center setting for 2023 under a provision for non-opioid pain management drugs, but CMS did not require separate payment in hospital outpatient departments.

The same company shows the counterfactual. Ocular's second product, ReSure Sealant, has no separate reimbursement and is paid only as part of the bundled surgery payment. The 2022 annual report describes its revenues as limited.

This is what a reimbursement change looks like from inside a launch. It is not a market access update. It is a reordering of the commercial plan.

Codes, coverage, and payment are three different assumptions

Launch teams often treat reimbursement as one milestone: the product is reimbursed, or it is not.

The Dextenza record shows at least three separate assumptions maturing at different times. A temporary C-code made billing possible in hospital outpatient and surgical center settings in July 2019. A permanent J-code made the product legible to billing staffs and payers from October 2019. Pass-through status made the product separately payable, for up to three years. Each of those is a different fact with a different effective date, a different owner, and a different expiry.

Coverage is a fourth assumption. A payer's decision to cover a product does not set the rate it will pay, and a code does not make any payer cover anything.

A launch plan that records "reimbursement: done" after the first of these events has stopped watching the other three.

The seven decisions a payment change reopens

When coverage or payment changes, the effect is not confined to the market access workstream. Seven commercial decisions reopen, whether the team schedules the reviews or not.

#	Decision	What a payment change forces	Typical owner
1	Which sites can move now	Which accounts can bill separately today, under which codes, in which settings	Market access + sales
2	Which sites should wait	Sites whose setting or payer mix does not support the economics yet	Sales leadership
3	Price	Whether the current price survives the payment structure, and what happens when it changes	Commercial + finance
4	Contracting	Distributor terms, rebates, volume discounts, and how much of list price the company keeps	Commercial ops
5	Financing and hiring	Whether field and support spend should accelerate, hold, or wait on the payment event	CEO/CFO
6	The sales story	Whether reps lead with the clinical case or the economic case	Marketing
7	Launch scope	Whether the launch narrows to the settings where payment works, or expands when it arrives	Launch lead

None of these reviews is optional in practice. They happen on the team's schedule or on the payer's.

Sell where the payment works

The first site-selection question after a payment change is not which accounts want the product. It is which accounts can be paid for using it.

Ocular aimed its initial sales force at high-volume surgical centers and Medicare Part B cataract volume, the setting and payer where separate payment applied. That is a commercial decision built on a reimbursement fact, and it belongs to the launch team, not to market access alone.

The same logic runs in reverse. After pass-through ended, separate payment continued in surgical centers but was not required in hospital outpatient departments. A site list built in 2021 on "hospital outpatient departments can bill separately" had an expiry date.

A smaller team should keep its target list annotated with the payment fact that qualifies each account: the code, the setting, the payer policy, and the date the fact was last checked. When the payment rule changes, the list re-sorts itself.

Price against the payment clock

During pass-through, Ocular disclosed expected pricing of approximately $538 per insert, separately payable. That number existed because of the payment mechanism, and the company disclosed the mechanism's expiry date in the same filings.

Pricing decisions have to answer for three moments: the price while transitional payment applies, the price when it ends, and the price the site can defend if the product is ever absorbed into a packaged payment. A team that sets one number and treats the payment structure as stable has made an unrecorded bet on CMS rulemaking.

The practical artifact is a pricing memo with a reopen trigger: the rule, the effective date, and the decision that follows if the rule changes.

Contract for the payment you actually have

Reimbursement shows up in the P&L as what the company keeps, not what the site is paid.

Ocular sold through specialty distributors and ran rebate and volume-discount programs. Its gross-to-net deductions were 22.4% of gross Dextenza sales in 2020 and 25.5% in 2021, after the company introduced a rebate program under a purchase volume-discount program in 2020. As volume grew, the contracting structure consumed a larger share of each dollar.

A payment change reopens these terms. A distributor discount negotiated when the product is separately payable may not fit a world of packaged payment. Rebate and volume programs built for one payment structure need review when the structure moves. The contracting question is not "did we get the product listed." It is "does the commercial plumbing still work at the payment rate the site actually receives."

Hire against the payment clock

Commercial hiring is a bet on payment timing.

Ocular increased selling and marketing spending to build its field team for the Dextenza launch, and said it expected those expenses to keep increasing in support of commercialization. That spend began while pass-through was new and its expiry was already on the calendar.

The same decision faces a smaller company with less room for error. If separate payment is expected in October, hiring ten reps in March buys six months of readiness and six months of burn. Waiting until October buys a half-year of missed selling. There is no safe default. There is only a recorded decision, tied to the payment event, with a trigger that reopens the hiring plan if the event moves.

Change the sales story when the payer changes

Before separate payment, the rep's argument is clinical: the product manages post-surgical pain and inflammation without depending on a patient's drop schedule. After separate payment, the argument gains an economic leg: the site is paid for the insert separately from the procedure. If separate payment ends, the story has to survive on clinical and operational value inside the site's existing procedure payment.

These are different conversations with different stakeholders. The first is a surgeon discussion. The second includes the administrator and the billing staff. The third is a value-analysis committee.

Marketing should version the story against payment states, not against the calendar. The question in the launch review is which state each account is in, and whether the rep walking in knows it.

A reimbursement change-impact map

Use a single page when a payment event lands. Fill it in before the next launch review.

Payment event	Site selection	Price	Contracting	Financing	Sales story	Launch scope
Separate payment granted	Prioritize accounts that can bill today	Confirm price against the payment rate	Review distributor and rebate terms	Decide whether spend pulls forward	Add the economic leg to the story	Hold or expand deliberately
Payment delayed	Shift to pilot and evidence sites	Revisit discounting	Avoid long lock-ins	Extend runway; hold hires	Lead with clinical value, not ROI	Narrow
Payment scheduled to end	Re-qualify every account by setting	Model packaged-payment price	Renegotiate terms built on separate payment	Decide what the cliff costs	Rebuild the story for committee review	Narrow to defensible settings
Permanent code created	Add billing-ready accounts	Confirm unit economics	Standardize terms	Reduce uncertainty premium	Add the billing path to the message	Resume the pipeline

The map is not the decision. It is the checklist that keeps one function's update from sitting in one inbox while seven other decisions age.

What this does not prove

The public record does not show Ocular's internal decision process, and it does not prove that pass-through status caused Dextenza's revenue growth. The company attributed growth to increased market acceptance and its commercialization efforts. The 2020 numbers crossed the COVID-19 pandemic, which disrupted cataract surgery volumes. The ReSure Sealant comparison involves a different product with a different use pattern, not a controlled experiment.

The filings also do not show that any single decision above was made because of a payment event. They show the dates: approval, the pass-through application on the same day, the temporary code, the launch in the same month the code took effect, the permanent code, the disclosed pricing during pass-through, the disclosed expiry, and the setting-specific payment outcome after expiry.

The lesson is narrower than causation. A team launching a reimbursed product is managing payment events as launch dependencies, with the same discipline it applies to regulatory events. Record the code, the coverage, the payment, the effective dates, and the expiry. Name the seven decisions each change reopens. Assign owners before the change, not after.

Sources

Frequently asked questions

Our product is a device, not a drug. Does this apply?: The mechanism names differ. Devices have their own transitional pass-through pathway, new technology add-on payments in the inpatient setting, and category codes. The planning problem is the same: approval, coding, coverage, and payment are separate events with separate clocks, and each one reopens commercial decisions.
We have no pass-through or add-on payment path. Is reimbursement still a launch dependency?: Yes. ReSure Sealant is the example inside this article. A product paid inside a bundled procedure payment sells on a clinical and operational case made to a committee, and the site-selection, pricing, and contracting questions all still apply. They are harder, not absent.
Who should own reimbursement on a small team?: One named person, even if it is a fraction of their job. The register of codes, coverage policies, payment status, effective dates, and expiry dates cannot live in a consultant's report. The owner does not need to do the policy work. They need to keep the facts current and trip the reopen triggers.
How early should payment work start?: Ocular filed its pass-through application on the day of FDA approval. The practical rule is that the payment application timeline belongs in the launch plan beside the regulatory timeline, not after it.