How to Read a 505(b)(2) Application

A 505(b)(2) application comes up more often in a regulatory career than its name suggests — new strengths, new routes of administration, new indications, fixed-dose combinations, a formulation change to a drug that already has years of approved history behind it. The thing worth reading for isn’t the data in front of you. It’s the data that isn’t there, because the applicant is relying on someone else having already generated it, and the whole filing stands or falls on whether that reliance actually fits the product being proposed.

In brief

A 505(b)(2) application doesn’t skip proving safety and effectiveness — it skips generating all of that proof itself. Under 21 U.S.C. §355(b)(2), some of what the review relies on comes from studies the applicant didn’t conduct and has no right of reference to, most often published literature or FDA’s own prior finding that an already-approved drug is safe and effective.
21 CFR 314.54 requires the applicant to name the specific listed drug it’s leaning on — established name, dosage form, strength, route, application holder, and NDA number — and to file the same patent certification Hatch-Waxman requires of an ANDA applicant, for every listed drug relied upon.
The part of the file worth reading first is the bridge: the data connecting the applicant’s product to the listed drug’s established finding. A new salt form, strength, or route doesn’t inherit safety automatically — the bridge has to show it still holds.
A 505(b)(2) is not a faster path to a generic-style review. FDA’s 2017 guidance on choosing between an ANDA and a 505(b)(2) exists because sponsors kept guessing wrong about which pathway their own product actually fit.

What the pathway actually borrows

Section 505(b) of the FD&C Act describes two kinds of new drug application before you ever reach the abbreviated (generic) pathway in 505(j). A 505(b)(1) application contains full reports of investigations the applicant conducted or had conducted for it. A 505(b)(2) application also contains full reports of safety and effectiveness — it is a complete NDA, not a shortcut — but some of what those reports rely on comes from investigations the applicant didn’t run and has no right of reference to: published literature, or FDA’s own prior finding of safety and effectiveness for a drug already on the market. That borrowed finding is doing real work in the application. Much of the applicant’s own new data, by contrast, will have moved through an IND before it ever reaches this filing — the same application that opens any other drug’s clinical file — and if that new data shows up as a trial report rather than raw data tables, it’s read the same way any clinical study report is read.

The listed drug is the foundation, and the paperwork proves it

21 CFR 314.54 is where the pathway becomes procedural rather than conceptual. The applicant has to identify the listed drug it relies on by name, strength, dosage form, route, the holder of that drug’s approved application, and the application number itself — there’s no relying on a finding without naming exactly which approved product produced it. And because a 505(b)(2) applicant is leaning on someone else’s approved drug the same way an ANDA applicant does, it inherits the same Hatch-Waxman obligation: a patent certification or statement for every patent listed in the Orange Book against that listed drug, for every listed drug relied upon. A Paragraph IV certification — asserting that a listed patent is invalid or won’t be infringed — is often the single highest-stakes sentence in the filing, because it puts the patent holder on notice and starts a clock most people reading the clinical sections never think to look for.

Where this goes wrong

Treating “505(b)(2)” as a synonym for “easier”

The pathway borrows data, not scrutiny. FDA still reviews the complete product file — manufacturing, labeling, and whatever part of the safety and effectiveness package the applicant generated itself — with the same rigor as any other NDA.

Assuming the bridge is self-evident

A different strength, dosage form, or route doesn’t inherit the listed drug’s safety finding by citation alone. It needs its own bridging data — comparative bioavailability or pharmacokinetics, typically — showing the difference doesn’t change the basis for the original finding.

Skipping the patent certification when reading someone else’s filing

It’s easy to read past a paragraph that isn’t about safety or efficacy. But a Paragraph IV certification is the applicant telling the listed drug’s patent holder it intends to market before that patent expires — worth knowing is even there before you evaluate anything else.

Reading a 505(b)(2) application well means finding the bridge before you evaluate anything else: which listed drug the filing leans on, what specifically differs between that drug and the one being proposed, and whether the data offered to cover that difference actually covers it. Everything else in the file — the genuinely new parts — only matters once the borrowed foundation checks out.

Sources & further reading

Cornell LII — 21 U.S.C. §355(b), Section 505(b) of the FD&C Act law.cornell.edu
eCFR — 21 CFR 314.54, Procedure for Submission of an Application Requiring Investigations for Approval of a New Indication for, or Other Change From, a Listed Drug ecfr.gov
FDA Guidance for Industry — Determining Whether to Submit an ANDA or a 505(b)(2) Application (2017) fda.gov
Regulatory Academy — How to Read an IND Application regulatoryacademy.com
Regulatory Academy — How to Read a Clinical Study Report regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.