Orphan exclusivity now bars one indication, not a disease

This blog has already drawn the line between what a special status buys and what it doesn’t, in breakthrough designation’s speed without an approval, and the line between an asset a sponsor earns and one it can spend on an unrelated drug, in a priority review voucher that isn’t tied to one drug. Orphan drug exclusivity draws a third line, and Congress just redrew it. The seven years of market protection a sponsor earns by bringing a designated drug to approval was read for several years as covering the whole rare disease the drug was designated for. As of February 2026, a statutory amendment narrows that protection to the specific use FDA actually approved.

Designation is a request; exclusivity is a reward for approval

Section 526 of the Act, 21 U.S.C. 360bb, lets a sponsor request orphan designation for a drug intended to treat a rare disease or condition — one affecting fewer than 200,000 people in the United States, or more than that if there’s no reasonable expectation the U.S. market will recover the drug’s development costs. A sponsor files that request before submitting a marketing application, and FDA’s implementing regulation at 21 CFR 316.20 spells out what the request has to show. Designation by itself buys tax credits, a user-fee waiver, and eligibility for orphan grant funding. It doesn’t buy market exclusivity. That’s a separate reward, under a separate section, that doesn’t exist until the drug is actually approved.

A court read the exclusivity statute’s own words literally, and FDA’s practice didn’t survive the reading

Section 527 of the Act, 21 U.S.C. 360cc, bars FDA from approving a second sponsor’s “same drug” for the “same disease or condition” for seven years after the first approval. FDA had long read that second phrase narrowly — as reaching only the specific use the first drug was approved for, not every use within the designated disease. The Eleventh Circuit rejected that reading in Catalyst Pharmaceuticals v. Becerra, decided in 2021, holding the statute’s text unambiguous and broader than FDA’s practice. The immediate casualty was a competing product approved for a narrower use within the same disease Catalyst’s own drug was designated for; FDA had to withdraw it. The agency’s own January 2023 Federal Register notice announcing compliance with the ruling made a point of limiting that compliance to the one product the case was about, while saying it would keep applying its narrower reading everywhere else — which left the scope of orphan exclusivity depending on which product, and which court, happened to be asking.

Congress closed that gap by rewriting the statute’s own phrase

Section 6605 of the Consolidated Appropriations Act, 2026, enacted February 3, 2026 as part of the Mikaela Naylon Give Kids a Chance Act, amended 21 U.S.C. 360cc directly: it replaces “same disease or condition” with “same approved use or indication within such rare disease or condition.” That’s a narrower bar than the one Catalyst read into the old text, and it’s the bar FDA had been applying administratively before the case forced it to stop. A second sponsor’s drug, approved for a different use inside the same designated rare disease, no longer has to wait out the first sponsor’s seven years to get there — it only has to clear the first sponsor’s exclusivity when it’s going after the same approved use.

Clinical superiority is still the other way around the wall

Even inside that narrower scope, a second drug can still get approved for the very same use during the exclusivity period if it’s clinically superior to the first. 21 CFR 316.3(b) defines that as a significant therapeutic advantage shown through greater effectiveness, greater safety, or — in unusual cases — a major contribution to patient care; cost and convenience don’t count toward that third ground. A separate exception at 316.36 lets a second sponsor in if the first one can’t assure an adequate supply. Neither exception turns on the disease-versus-indication question Congress just settled; both operate inside whatever scope the exclusivity bar currently has.

A hypothesis at designation isn’t the same showing as a demonstration at approval

The clinical-superiority question actually surfaces twice, at two different evidentiary standards. A sponsor seeking designation for a drug that’s otherwise the same as an already-designated or approved drug only has to present a plausible hypothesis of clinical superiority, under 316.20. By the time that drug is up for approval, 316.34(c) requires actually demonstrating superiority, not just hypothesizing it. The D.C. Circuit upheld that two-stage structure in Eagle Pharmaceuticals v. Azar in 2020, rejecting a reading that would have made exclusivity turn on the hypothesis alone. A tracker that records “clinical superiority: asserted” as a single checkbox has collapsed two different legal findings, made months or years apart, into one that doesn’t match either.

Where this meets the file

An orphan drug tracker that records only “orphan designated” and a disease name has nowhere to put the field that now decides the exclusivity question: the specific approved indication the exclusivity actually attaches to. A tracking template that keeps the designated disease, the approved indication, the approval date exclusivity runs from, and any clinical-superiority showing as separate required fields is previewed in the launch catalog alongside this week’s other drug-lifecycle templates. If your program tracked this distinction before the 2026 fix made it official, the shelf takes that correction directly.