GLP1 and GIP US Listed Patents and Exclusivity Viewer
Inspect US FDA listed-patent and exclusivity records for selected semaglutide, tirzepatide and liraglutide applications, starting with Ozempic application NDA209637. The reference uses a real September 2026 FDA source capture. Listed dates are source facts to inspect, not a forecast of unrestricted market entry or a legal opinion on patent scope.
Selected semaglutide, tirzepatide and liraglutide applications, including matching ANDAs in the retained capture. Orange Book source file EOBZIP_2026_09.zip was captured on 14 October 2026. The selected dataset was built on 16 October 2026. No Purple Book rows or change-history records are included; source metadata and hashes are retained.
Begin with the application and product identity
Drug names can refer to an ingredient, a brand, a formulation or several regulatory applications. The initial application identifier provides a precise starting point for the retained FDA records. Check product numbers, strength and dosage-form context before assuming that a listing applies uniformly to every product containing the same ingredient.
The reference includes selected incretin-related applications and matching abbreviated applications from the capture. It is not a search of every peptide patent or every incretin development programme. Semaglutide, tirzepatide and liraglutide are grouped here to support an explicit source-inspection task, while their molecular and pharmacological differences remain outside the meaning of a shared table heading.
Keep listed facts separate from legal conclusions
A patent record can carry a number, a date, flags and a use code. Those fields should be interpreted through the source documentation and the actual claims where appropriate. A listing is not an adjudication that every possible competing product infringes. Conversely, absence from the selected source is not evidence that no relevant patent exists.
Regulatory exclusivity is a separate category with its own basis and scope. A chart that places dates on one axis can make unlike records appear equivalent. Retain the record type and any native rule label alongside a calculated date. The page does not collapse patent listings and exclusivity into a single definitive end of protection.
Preserve the capture when discussing a timeline
The September file name, October retrieval date and dataset build time describe different events. A source URL can later serve a newer release, so the retained hash and capture metadata matter when reproducing a discussion. A date comparison is meaningful only when both the source version and comparison date are explicit.
This reference omits change history and Purple Book rows. Those omissions are declared coverage boundaries, not findings about the products. For a consequential commercial or legal decision, consult the relevant current records and qualified analysis of the actual question. The interactive workspace helps organise and trace the supplied data; it does not decide enforceability, claim scope or launch feasibility.
Equations and variables
Source-date ordering
Δt = listed date − comparison date
- Δt
- Calendar distance to a stated source date; not time until legal freedom to operate
- listed date
- A date supplied by the source or a separately labelled native rule
- comparison date
- Explicit date used for the comparison
Scope and limitations
- US selected-application scope only. Orange Book listings do not enumerate all patents, jurisdictions, litigation outcomes or commercial restrictions relevant to a product.
- Patent listings, statutory exclusivity and regulatory approval are distinct records. A latest listed date is not an assured launch date, enforceability finding or freedom-to-operate conclusion.
- No change history is included in this reference dataset. Empty change results do not mean the FDA records have never changed. Source code definitions retain their existing unverified qualifications.
Sources and provenance
- FDA Orange Book data filesFDA source terms; no new licence classification
Listed protection is not a claim construction or freedom-to-operate opinion.
- FDA Orange Book downloadable dataExisting FDA source terms; retained capture metadata
The URL may update; the retained file is EOBZIP_2026_09.zip with capture time and SHA-256.
- FDA Orange Book preface and explanatory materialFDA source terms; methodology reference
Technical questions
Is this a worldwide GLP1 patent landscape?
No. It is a selected US FDA application dataset for semaglutide, tirzepatide and liraglutide. It does not search patent families across jurisdictions or determine claim scope. A worldwide patent landscape requires a different search strategy and legal analysis.
Does the last listed patent date establish a generic launch date?
No. A listed date alone does not resolve patent validity, claim coverage, litigation, settlement, regulatory requirements or other constraints. The page displays source records and labelled rules, not a prediction of market entry or a freedom-to-operate opinion.
Why are patents and exclusivity shown separately?
They originate in different legal and regulatory mechanisms and can apply to different aspects or product subsets. Combining them into one unlabeled expiry date loses that distinction. Inspect the individual records, source dates, product numbers and any stated rule before interpreting a timeline.
Connected workflows
- KRAS G12D trial-record exploration
Distinguish development-stage evidence from product protection.
- HER2 and TROP2 ADC trial-record exploration
Inspect clinical studies without inferring patent coverage.
- Lipinski rule-of-five property inspection
Keep molecular descriptors separate from regulatory and legal status.
- FDA Orange Book Exclusivity Codes and Expiry Guide
Read the statutory exclusivity codes beside the listed patents.
- Orange Book Patent Flags, Use Codes, and ANDA Context
Inspect the patent flags, use codes and Paragraph IV certifications on the same application.