Last updated: April 25, 2026
What was litigated in Pfizer Inc. v. Apotex (1:13-cv-02022)?
The case is a U.S. Hatch-Waxman patent litigation styled Pfizer Inc. v. Apotex Inc., docketed as 1:13-cv-02022. It involves a branded Pfizer product and Apotex’s effort to launch a lower-cost generic under 21 U.S.C. § 355(j) (ANDA framework). The central legal structure in this docket is the standard Hatch-Waxman infringement challenge tied to the ANDA’s asserted certifications (typically Paragraph IV) and the related patent portfolio covering the brand’s active ingredient, dosage form, and/or method-of-use claims.
However, no case-specific particulars (brands, asserted patents, claim constructions, infringement theories, or disposition dates) are available in the provided input. Under the operating constraints, a complete and accurate litigation analysis cannot be produced.
Which patent(s) and claim(s) drove the dispute?
Patent-driven Hatch-Waxman dockets typically include:
- The Orange Book-listed patents identified in the brand’s patents table
- The ANDA certifications (e.g., Paragraph IV) and the asserted statutory grounds
- The asserted claim(s) for infringement and the defendant’s non-infringement or invalidity positions
- The court’s constructions and final infringement/validity holdings
No asserted patent numbers, claim sets, or infringement/invalidity findings are stated in the provided input. Without these, it is not possible to map claim scope, chart validity arguments, or quantify litigation outcomes.
What was the procedural posture and outcome?
A proper litigation summary requires hard inputs such as:
- Filing date, venue, and parties (including affiliates, subsidiaries, or generic applicants)
- Motions sequence (dismissal, preliminary injunction, summary judgment, JMOL, trial, settlement)
- Claim-construction order dates
- Final judgment date and disposition basis
- Any appellate history (Federal Circuit proceedings)
The provided input contains only the case name and docket number. No disposition, timeline, or final judgment status is available to support an accurate summary.
How does this docket typically connect to ANDA timing and exclusivity?
In Hatch-Waxman cases tied to a docket like this, business impact generally tracks:
- Whether Pfizer obtained a temporary restraining order or preliminary injunction (or was denied)
- Whether a final judgment delayed launch beyond the statutory 180-day exclusivity window
- Whether the court found patents infringed and valid, leading to permanent injunction or damages
- Whether the case settled, with defined launch dates and carve-outs
No ANDA filing date, paragraph certification, or exclusivity or settlement terms are included in the provided input.
What is the litigation value for Pfizer and Apotex from a decision standpoint?
A decision-grade analysis would typically quantify:
- Patent portfolio strength (likelihood of sustained validity/infringement)
- Exposure window (damages period based on generic launch and design-arounds)
- Economics (probability of entry delay versus settlement probability)
- Competitive impact (timing of generic entry relative to expiration of each patent and any exclusivity)
No facts in the provided input support a quantitative business assessment.
Key Takeaways
- The docket identifier (1:13-cv-02022) and case caption Pfizer Inc. v. Apotex Inc. are insufficient to produce a complete litigation summary or patent/ANDA analysis.
- A decision-grade report must include asserted patents, ANDA certification posture, claim constructions, and final disposition, none of which are present in the provided input.
FAQs
-
What court decided Pfizer Inc. v. Apotex Inc., 1:13-cv-02022?
Not provided in the input.
-
Which Pfizer product and Orange Book patents were asserted in 1:13-cv-02022?
Not provided in the input.
-
What ANDA certification (e.g., Paragraph IV) was at issue?
Not provided in the input.
-
Did the case reach summary judgment, trial, or a settlement?
Not provided in the input.
-
What was the final outcome for Apotex’s planned launch?
Not provided in the input.
References
[1] No sources were provided in the prompt.
