On this page
What makes an orphan drug designation request complete and persuasive?
Define the drug and rare disease or condition, explain the medically plausible use with all relevant evidence, and document the appropriate U.S. population or cost-recovery basis. Address any orphan-subset or same-drug clinical-superiority issue. Submit a complete request through the OOPD route before the sponsor’s marketing application for that drug and condition; designation is a separate decision from approval.
Before you begin
FDA orphan drug designation requests for drugs and biologics under Part 316; not rare-pediatric-disease designation or an approval application.
What you will prepare: A source-backed designation package and correct OOPD submission handoff.
Define the drug, disease and proposed use precisely
Start with the sponsor/contact, drug identity and source, specified rare disease or condition, proposed use and regulatory history. A broad platform description is not the drug identity, and a convenient trial-enrollment subgroup is not automatically a distinct orphan disease or qualifying subset.
Prepare the scientific rationale from relevant in-vitro, disease-model and clinical evidence, including negative and inconclusive findings. Explain why the evidence supports a medically plausible use in this condition. Do not substitute a general mechanism description or toxicology package for the disease-specific rationale.
Make the population argument reproducible
Identify the relevant U.S. population basis and authoritative references. Document case definition, population year, data sources, arithmetic and uncertainty. Distinguish treatment prevalence from the annual population relevant to certain preventive, diagnostic or vaccine uses. The regulation also provides a cost-recovery basis for specified larger-population circumstances; that requires its own evidence, not an assertion that development is expensive.
For an orphan subset, show why properties of the drug make people outside the subset inappropriate candidates. Do not create rarity merely by restricting the proposed label. If the drug is otherwise the same as an already approved drug for the same disease/condition, assess the additional plausible clinical-superiority hypothesis described in 316.20(a) and (b)(5). Obtain the regulatory/scientific evaluation instead of asserting that a new sponsor or formulation is sufficient.
Assemble the request and use the actual designation route
Use a content index aligned to 316.20(b): request; parties/product source; condition and need; drug description and rationale; same-drug issue if relevant; subset if relevant; regulatory/marketing history; rarity or cost-recovery evidence. Attach the pertinent references and obtain authorized execution.
FDA lists OOPD submission routes including the CDER NextGen portal. A document stored under 1.12.17 in an application is not by itself proof that OOPD received a designation request. Preserve the actual submission receipt and designation decision. Designation does not establish marketing approval or guarantee exclusivity.
Worked review: worldwide incidence does not answer U.S. prevalence
Fictional editorial exercise: a treatment request cites a global annual incidence estimate and labels it the number of affected U.S. patients. Rebuild the epidemiologic argument with an appropriate U.S. basis and transparent conversions.
If the proposal changes from treatment to prevention, reassess the relevant population. If no defensible estimate is available, report the gap and involve the epidemiology/regulatory owner; do not select the lowest published number to fit the threshold.
Connect the eight content elements to specific evidence
Use the sequence in 316.20(b) as a review index. A polished epidemiology section cannot compensate for missing product identity or a disease-specific scientific rationale.
| Required content area | Useful preparation record | Review question |
|---|---|---|
| Designation request | Exact disease or condition and requested designation | Is the request specific enough to evaluate? |
| Sponsor and product source | Sponsor/contact/agent details, product name and source | Are the responsible party and actual drug identifiable? |
| Disease and proposed use | Case definition, intended use and unmet need | Is the proposed population scientifically coherent? |
| Drug and scientific rationale | Identity, properties and relevant laboratory, disease-model and clinical evidence | Does the evidence support a medically plausible use, including negative or inconclusive findings? |
| Same-drug issue, when applicable | Approved-product comparison and plausible superiority hypothesis | Is the proposed difference relevant to clinical superiority? |
| Orphan subset, when applicable | Drug properties and why others are inappropriate candidates | Is the subset drug-driven rather than a convenient label restriction? |
| Regulatory and marketing history | U.S./foreign status, uses and adverse regulatory actions | Does the account agree with the actual program history? |
| Rarity or cost-recovery basis | Authoritative references, calculation and assumptions | Can another reviewer reproduce the conclusion? |
For a treatment-prevalence argument, name the disease definition, U.S. population basis, source year, rate units and calculation. Incidence counts new cases over time; prevalence concerns affected people. Do not change one into the other by relabeling a column. For vaccine, diagnostic and preventive uses, 316.20(b)(8) instead addresses the number of people to whom the drug will be administered in the United States per year. Establish the relevant population before collecting a convenient statistic.
Fictional epidemiology exercise: assume a U.S. denominator of 340 million people solely for this arithmetic exercise. A prevalence estimate of 55 per 100,000 gives 187,000 affected people; an alternative estimate of 65 per 100,000 gives 221,000. Explain the case definitions, methods, dates and relevance of the estimates. Do not select the lower one just because it falls below the threshold or present the uncertainty as resolved. The regulation says fewer than 200,000: exactly 200,000 does not meet that population criterion. The alternative cost-recovery route has its own evidentiary requirements.
For a subset of a more common disease, explain why the drug's properties make people outside the subset inappropriate candidates. “We only plan to enroll this subgroup” does not answer that question. Preserve the distinction between a medically justified orphan subset and a commercial development choice.
If the proposed product is otherwise the same as an already approved drug for the same disease or condition, 316.20 calls for a plausible clinical-superiority hypothesis. A different sponsor, new package or more optimistic development plan does not itself establish that hypothesis. Conversely, another sponsor's designation does not automatically prevent a separate complete request. Do not confuse an already designated product with an already approved same drug when assessing the applicable question.
Under 316.23, submit the designation request before that sponsor submits the marketing application for the same drug and rare disease or condition. An already approved drug can be proposed for an unapproved use under the provision's separate condition. Plan the actual OOPD handoff early enough to preserve the correct sequence; a Module 1 copy is not evidence of receipt. FDA's current resource says a request submitted through CDER NextGen does not also need email submission.
Reconcile the clinical rationale with the clinical overview. Keep any RMAT request separately supported: rare-disease eligibility and preliminary clinical evidence for an expedited program are different assessments.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Does a population of exactly 200,000 meet the ordinary orphan population criterion?
The criterion in 316.20(b)(8) is fewer than 200,000 people in the United States, with a separate annual-administered population basis for specified uses. Exactly 200,000 does not satisfy that numerical condition. Assess the alternative cost-recovery provision on its own evidence rather than rounding the population downward.
Can a sponsor create an orphan subset by narrowing trial enrollment?
A narrow trial population alone does not establish an orphan subset. Section 316.20(b)(6) requires a showing that properties of the drug make the remaining people with the disease inappropriate candidates. Explain that drug-specific rationale and supporting evidence rather than relying only on the intended label or development plan.
Should negative or inconclusive findings be omitted from the orphan scientific rationale?
No. Section 316.20(b)(4) calls for all relevant available laboratory, disease-model and clinical information, whether positive, negative or inconclusive. Explain the weight and relevance of those findings. A mechanism summary or selected positive experiment does not replace the complete medically plausible rationale.
Does another sponsor’s orphan designation prevent a request for the same drug and condition?
More than one sponsor can receive designation, but each must submit a complete supporting request. Separately assess whether the product is otherwise the same as an already approved drug for that condition, which raises the plausible clinical-superiority question. Designation and approval status are not interchangeable.
Can the orphan designation request wait until after the same marketing application is submitted?
Section 316.23(a) places the request before that sponsor’s marketing application for the same drug and rare disease or condition. Preserve the actual submission sequence and OOPD receipt. The separate provision for an already approved drug concerns an unapproved use; it is not permission to disregard the timing for the same use.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Regulation
21 CFR 316.23: timing of orphan designation requests ↗Paragraphs (a)–(b); reopened October 6, 2026, eCFR displayed currency through October 2, 2026.
Regulation
21 CFR 316.20: content of an orphan designation request ↗Paragraphs (a)–(c), especially (b)(1)–(8); current through September 18, 2026.
FDA resource
FDA: Designating an Orphan Product ↗Current designation and submission routes checked September 22, 2026; NextGen portal and other OOPD routes are separate from eCTD organization.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.12.17. A heading identifies placement, not mandatory applicability.