US Patent 8,940,718 (US8940718): Scope, Claim Construction, and US Patent Estate Analysis for HCV NS5B Polymerase Inhibitor Chemotypes
US 8,940,718 is a small-molecule patent centered on HCV NS5B polymerase inhibitor compounds defined by a Formula (I) “E1a-V1a—C(═O)—P1a—W1a—P1b—C(═O)—V1b-E1b (I)” core, with broad substitution language for linker groups and end-cap amide moieties. The claim set includes: (i) a compound Markush genus (claim 1) plus multiple dependent claims tightening substitutions on the imidazole-containing portion (claims 2-3), (ii) end-cap amide selections (claims 4-9, 11), (iii) specific embodiments of the heteroaromatic substituent patterns (claims 11-21), and (iv) downstream coverage for pharmaceutical compositions (claim 24-25) and methods for treating hepatitis C, including combination regimens with interferon/pegylated interferon and ribavirin (claims 26-28).
Because the claim text you provided is partially redacted at key points (P1a/P1b/W1a/V1a/V1b/R9a/R9b substituent definitions appear as blanks in several places), this analysis focuses on what is structurally and legally determinative from the portions that are explicit: the backbone architecture, the main Markush levers, and the claim layering strategy that drives infringement risk and freedom-to-operate.
What is the chemical scope of US Patent 8,940,718’s Formula (I) and how broad are the Markush groups?
Short answer: Claim 1 recites a broad Markush genus around a symmetric/asymmetric di-carbonyl “E1a-V1a—C(═O)—P1a—W1a—P1b—C(═O)—V1b-E1b” scaffold, with variable substituents on the W1a position and defined choices for end-cap amide residues (E1a/E1b), plus variable R9a/R9b “taken together are” options. The genus is then narrowed by dependent claims to imidazole substitution patterns and specific end-cap amide choices.
Claim 1 backbone architecture (what must be present for infringement)
Claim 1 requires the compound to be:
- E1a-V1a—C(═O)—P1a—W1a—P1b—C(═O)—V1b-E1b (Formula I)
This is a gating limitation: a candidate compound must have two carbonyl-linked segments flanking a P1a—W1a—P1b region, with end caps expressed as E1a-V1a on one side and V1b-E1b on the other.
Even with Markush breadth elsewhere, infringement turns on matching that structural skeleton.
Key variable: W1a and its substituent tolerance
The claim states W1a is (blank in your text), and then provides substituent options:
- W1a is optionally substituted with halo, alkyl, haloalkyl, or cyano.
Legal effect:
- This is a classic substitution-on-a-defined-atom pattern. It means the heteroatom or ring atom labeled W1a is fixed in identity by the (redacted) definition of W1a, but the claim tolerates a meaningful set of substituents (halogen, methyl/alkyl, halomethyl-like groups, and cyano).
Key variable: Y5 and X5 (side pattern constraints)
Claim 1 also defines:
- Y5 is —O—CH2—, or —CH2—O—
- X5 is —CH═CH—
These are structural constraints on substituent orientation/connectivity:
- The claim distinguishes the oxygen-CH2 connectivity direction (O-CH2 vs CH2-O) and fixes the presence of a vinylene (CH═CH) motif.
A competitor can avoid infringement only by removing those motifs or replacing them with non-equivalent structural features outside the claim language.
Key variable: E1a and E1b end-caps (amide-type Markush)
Claim 1 defines E1a and E1b as either directly:
- —N(H)(alkoxycarbonyl)
- —N(H)(cycloalkylcarbonyl)
- —N(H)(cycloalkyloxycarbonyl)
or as paired with V1a/V1b “taken together are R9a / R9b”.
Legal effect:
- The end caps are restricted to carbamate/amido derivatives of specific functional types.
- This is a meaningful narrowing compared with full “any amide” language; it is still broad within those functional classes (alkoxycarbonyl vs cycloalkylcarbonyl vs cycloalkyloxycarbonyl).
P1a and P1b positions
Claim 1 includes:
- P1a is selected from: (blank in your text)
- P1b is selected from: (blank in your text)
Given that this definition is redacted, the safest legal conclusion from your provided text is:
- P1a and P1b are not free-form; they are limited to enumerated choices within the patent specification’s claim text.
- Any “design-around” that changes P1a/P1b identity can avoid infringement even if other regions match.
R9a / R9b “taken together are” clauses
Claim 1 also includes alternative coverage:
- E1a-V1a taken together are R9a
- E1b-V1b taken together are R9b
with R9a and R9b each independently limited to (blank).
These “taken together” clauses are usually drafted to:
- capture conformationally/chemically related variants,
- while ensuring that certain linked fragments collectively fall within enumerated R-groups.
From a claim construction perspective, this matters because infringement of a “taken together” limitation generally requires the coupled fragment match simultaneously, not piecemeal.
Which specific dependent claims narrow the imidazole substitution pattern in US 8,940,718?
Claims 2 and 3 are the most direct “structure tightening” you supplied:
Claim 2: imidazole (formula A1) optional substitution set
“Claim 2 … wherein the imidazole ring shown in formula A1 or A2 is optionally substituted with…”
- halo
- haloalkyl
- cyano
- alkyl
Legal effect:
- It expands the tolerated substitution types on the imidazole ring. The claim does not list substitution number limits in your text; it says “optionally substituted with one or more groups” meaning zero or multiple substituents may be present, subject to the underlying imidazole valences and the specification’s actual defined structure.
Claim 3: imidazole (formula A2) narrower substitution set
For the A2 imidazole ring, the claim lists:
- halo, haloalkyl, cyano, or alkyl (again “optionally substituted with one or more”).
In effect, claims 2 and 3 appear to cover imidazole variants with permissible substituents from the same broad set, but tailored to which imidazole drawing (A1 vs A2) is used.
How does US 8,940,718 treat end-cap selection (E1a/E1b) and what are the strongest narrowing points?
Claims 4 through 9 plus 11 define end-cap choices in a more concrete way.
End-cap “at least one” vs “both”
- Claim 4: at least one of E1a and E1b is —N(H)(alkoxycarbonyl).
- Claim 5: both E1a and E1b are —N(H)C(═O)OMe (methoxycarbonyl on N).
- Claim 6: repeats Claim 5 (exact same limitation text).
- Claim 7: at least one of E1a and E1b is —N(H)(cycloalkylcarbonyl) or —N(H)(cycloalkyloxycarbonyl).
- Claim 8: at least one of E1a and E1b is cyclopropylcarbonylamino, cyclobutylcarbonylamino, cyclopropyloxycarbonylamino, or cyclobutyloxycarbonylamino.
- Claim 9: E1a and E1b each independently selected from the same four cyclopropyl/cyclobutyl carbonyl or oxycarbonyl amino end caps.
Legal effect:
- The broad genus in claim 1 may allow multiple end-cap types, while dependent claims fence in particular carbamates/amides. These dependents matter for infringement strategy and for assessing which design-arounds reduce risk.
Claim 11: E1a-V1a taken together are R9a OR E1b-V1b taken together are R9b
This claim is another “coupled fragment” restriction that can be used to anchor specific variants inside the R9 group boundaries.
Given that the R9 definitions are redacted, claim 11 is legally significant but not fully actionable from the text alone.
How many formulation and method-of-treatment claims does US 8,940,718 add, and what do they cover?
Pharmaceutical composition coverage
- Claim 24: “A pharmaceutical composition comprising the compound as described in claim 1 … and at least one pharmaceutically acceptable carrier.”
- Claim 25: composition further comprising an inhibitor of HCV NS5B polymerase.
Legal effect:
- Claim 24 covers standard formulation with carriers. It is broad to the point of often being hard to design around if the underlying compound is in-claim.
- Claim 25 is a combination formulation claim that adds another NS5B polymerase inhibitor component. This can expand settlement pressure for multi-drug regimens.
Method of treatment coverage
- Claim 26: “A method of treating hepatitis C … administering … a therapeutically effective amount of the compound …”
- Claim 27: method further comprising interferon or pegylated interferon
- Claim 28: method further comprising ribavirin
Legal effect:
- These are direct use/combination claims. Even if a generic avoids manufacturing the compound, infringement risk can exist if a combination regimen is practiced with an infringing compound.
Where are the claim “pressure points” for design-around and invalidity arguments?
1) Matching the Formula (I) skeleton
The core scaffold is required. Generic chemotypes that materially alter:
- the carbonyl positioning relative to P1a/P1b,
- the identity of P1a/P1b allowed options,
- or the Y5/X5 motif (O-CH2 / CH2-O and CH═CH),
are the most viable design-around directions.
2) End-cap restrictions (E1a/E1b)
Because E1a/E1b are limited to N(H)(alkoxycarbonyl), N(H)(cycloalkylcarbonyl), or N(H)(cycloalkyloxycarbonyl), and dependent claims emphasize specific end-caps like N(H)C(═O)OMe and cyclopropyl/cyclobutyl variants, competitor compounds with different protecting group chemistries or different N-acyl types can fall outside.
3) W1a substitution sets
W1a substituent tolerance is explicit: halo, alkyl, haloalkyl, cyano. That narrows avoidance: substitutes outside that set (e.g., hydroxy, alkoxy not considered “alkyl,” amines, sulfonamides) could be used to shift out of claim language if the W1a identity remains the same.
What does the claim set imply about the patent’s breadth in the HCV NS5B inhibitor landscape?
The claim language indicates the patent targets an NS5B polymerase inhibitor chemotype class with:
- defined linker geometry,
- imidazole-containing structural motifs (A1/A2),
- and carbamate/amides at N with alkoxycarbonyl or cycloalkyl/cycloalkyloxycarbonyl.
That aligns with how HCV NS5B inhibitors were typically protected: scaffold genus plus end-cap variants plus imidazole substitution diversity, then downstream composition and regimen claims for interferon and ribavirin.
From a commercial risk lens:
- if the active ingredient used in marketed products sits inside claim 1’s scaffold and end-cap language, the patent estate tends to be enforceable against both API and formulations.
- if it sits just outside on P1a/P1b identity or E1a/E1b end-cap chemistry, dependent claims can still be avoided.
US 8,940,718 claim chart (text-based) to operationalize infringement screening
| Claim |
Main limitation category |
What a candidate must show to infringe |
| 1 |
Formula (I) scaffold |
Presence of E1a-V1a—C(═O)—P1a—W1a—P1b—C(═O)—V1b-E1b plus W1a substituent options, Y5 and X5 motifs, and E1a/E1b limited to specified N(H) carbonyl/carbamate types (or paired R9a/R9b) |
| 2 |
Imidazole substitution (A1/A2) |
Imidazole ring substituted with halo/haloalkyl/cyano/alkyl (one or more optional) |
| 3 |
Imidazole substitution (A2) |
Same substitution set for A2 imidazole ring variant |
| 4 |
At least one end-cap choice |
E1a or E1b is N(H)(alkoxycarbonyl) |
| 5/6 |
Specific end-caps both sides |
E1a and E1b are N(H)C(═O)OMe |
| 7 |
End-cap class |
At least one of E1a/E1b is cycloalkylcarbonyl or cycloalkyloxycarbonyl |
| 8 |
Cyclopropyl/cyclobutyl end-cap list |
At least one end-cap among the four listed cyclopropyl/cyclobutyl carbonyl or oxycarbonyl amino types |
| 9 |
Both end-caps chosen from list |
E1a and E1b each independently selected among the four listed end-caps |
| 11 |
“Taken together” R9a/R9b |
Coupled E1a-V1a or E1b-V1b matches enumerated R9 options (redacted) |
| 24 |
Composition |
API plus pharmaceutically acceptable carrier |
| 25 |
Composition + NS5B combination |
Addition of another HCV NS5B polymerase inhibitor |
| 26-28 |
Methods and combinations |
Administration for hepatitis C; optionally with interferon/pegylated interferon; optionally with ribavirin |
How should stakeholders read the claim strategy for licensing and litigation posture?
1) Genus claim 1 drives core enforcement leverage
Claim 1 is the anchor. If an accused compound reads on claim 1, then:
- claim 24 and 26 provide formulation and method pathways,
- claim 25 and 27/28 provide combination and regimen hooks.
2) Dependent claims create settlement granularity
Even if a candidate compound is close-but-not-identical, dependent claims (2-3, 4-9) offer multiple claim-entry points. This increases settlement odds because accused products often share imidazole substitution and end-cap families.
3) Combination claims can expand defendant set
Claim 25 and claims 27-28 pull into the business of multi-agent HCV regimens. In legacy HCV treatment frameworks, interferon/peg-interferon and ribavirin combination use is common, which can broaden enforcement options against practices involving the patented compound.
Key Takeaways
- US 8,940,718 is scaffold-centric: Claim 1 requires a specific NS5B inhibitor Formula (I) architecture with E1a/E1b carbamate/amido end caps and fixed Y5 (O-CH2/CH2-O) and X5 (CH═CH) motifs.
- Breadth is driven by Markush substituent sets: W1a tolerates halo/alkyl/haloalkyl/cyano substitutions; imidazole substitutions (claims 2-3) allow halo/haloalkyl/cyano/alkyl variants.
- Most effective design-arounds likely target P1a/P1b identity or end-cap chemistry: Because E1a/E1b are constrained to defined N(H) carbonyl/carbamate classes, changing that chemistry can exit claim language.
- Downstream coverage is robust: Composition (claim 24-25) and method-of-treatment with interferon/pegylated interferon and ribavirin (claims 26-28) extend enforcement beyond API manufacture to formulation and regimen practice.
FAQs
-
Does US 8,940,718 cover both API and finished drug products?
Yes. Claim 24 covers pharmaceutical compositions containing the claim 1 compound with acceptable carriers.
-
Are interferon and ribavirin explicitly claimed with the hepatitis C treatment method?
Yes. Claims 27 and 28 add interferon/pegylated interferon and ribavirin to the method of treating hepatitis C.
-
What substituent types are allowed on W1a?
Halo, alkyl, haloalkyl, or cyano (with W1a identity itself defined in the (redacted) W1a definition in claim 1).
-
How are imidazole substitutions handled?
Claims 2-3 permit imidazole ring substitution with halo, haloalkyl, cyano, and alkyl (one or more optional).
-
Which claim language most directly limits freedom-to-operate beyond scaffold matching?
The coupled end-cap definitions (E1a/E1b) and the “taken together are R9a/R9b” provisions, plus the constrained enumerations for P1a/P1b (redacted in your text).
References
- US Patent 8,940,718. “Method for treating hepatitis C,” claims 1-28 (claim text provided in prompt).
