Last Updated: May 11, 2026

Details for Patent: 8,642,538


✉ Email this page to a colleague

« Back to Dashboard


Summary for Patent: 8,642,538
Title:Macrocyclic hepatitis C serine protease inhibitors
Abstract:The present invention relates to novel macrocyclic compounds and methods of treating a hepatitis C infection in a subject in need of such therapy with said macrocyclic compounds. The present invention further relates to pharmaceutical compositions comprising the compounds of the present invention, or pharmaceutically acceptable salts, esters, or prodrugs thereof, in combination with a pharmaceutically acceptable carrier or excipient.
Inventor(s):Yiyin Ku, Keith F. McDaniel, Hui-Ju Chen, Jason P. Shanley, Dale J. Kempf, David J. Grampovnik
Assignee: AbbVie Inc
Application Number:US13/439,551
Patent Claim Types:
see list of patent claims
Use; Composition;
Patent landscape, scope, and claims:

United States Patent US 8,642,538: Scope of Claims, Claim-Chart Structure, and Patent Landscape for a Hepatitis C Antiviral Series

US 8,642,538 claims a broad Markush-defined small-molecule class (Compound of Formula I or I′), salts, pharmaceutical compositions, and hepatitis C treatment methods. The claim set is built to capture (1) wide structural latitude across multiple substituent vectors (A, R1, E, R5, and aryl ring substitution pattern), (2) two structural “families” within the same scaffold (J absent vs J is carbonyl-like; and I vs I′ via the “E absent” / “G = -E-R5” construction), and (3) multiple downstream claim layers (compound, composition, and method) that support both direct infringement and induced infringement theories around marketed antivirals and combination regimens.

What is claimed in US 8,642,538 at a high level?

Claim 1 is the only independent claim you provided; it is the structural engine. It defines:

  • A compound of Formula I or I′ or a pharmaceutically acceptable salt
  • A scaffold variableization across:
    • J: “J is absent” or one of multiple linker-like moieties including —C(O)—, —O—C(O)—, —N(R3)—C(O)—, —C(S)—, —C(═NR4)—, —S(O)—, —S(O2)—, or —N(R3)—C(O)—
    • A: large Markush set spanning substituted alkyl/alkenyl/alkynyl (with 0–3 heteroatoms O/S/N), substituted aryl, substituted arylalkyl, substituted alkoxy, substituted heteroaryl, substituted heterocyclic, or substituted carbocyclic
    • R1: a long list of substituents (halogen, amino, cyano, CF3, azide, nitro, OR4, SR4, SOR4, SO2R4, sulfonamide-like, carboxamide-like, etc.), with additional Markush paths including “optionally substituted aryl/heteroaryl/heterocyclic/carbocyclic” and lower alkyl/alkenyl/alkynyl with 0–3 heteroatoms
    • G: “G is -E-R5” with E absent allowed, or with E taking one of several heteroatom-containing linkages:
    • “—O—, —S—, —N(R3)—, —N(R3)S(Op)—, —N(R3)C(O)—, —N(R3)C(O)S(Op)—, —OS(Op)—, —C(O)S(Op)—, or —C(O)N(R3)S(Op)—”
    • p: 0, 1, or 2
    • R5: only H or a substituted chain/ring group (alkyl/alkenyl/alkynyl, or carbocyclic/heterocyclic/aryl/heteroaryl), with heteroatom caps (0–3 O/S/N)
    • R3 and R4: each independently selected from the same family of substituent classes (alkyl/alkenyl/alkynyl with 0–3 O/S/N; aryl/heteroaryl/heterocyclic/carbocyclic; or hydrogen)
    • L: absent or substituted alkylene/alkenylene/alkynylene (0–3 O/S/N)
    • j, k, m, n: integer ranges (j 0–4; k 0–3; m 0–2; n 0–4)
    • Terminal variableization: “Y is —C(R″)—, R′ and R″ together with the carbon atoms… form an aryl or heteroaryl ring,” with that ring optionally substituted

Claim 2–6 lock in specific sub-sets of Claim 1 parameters, shrinking the Markush ranges to particular embodiments.

How does the claim architecture map to enforceable coverage?

1) Compound claim breadth is engineered around Markush substitution vectors

Claim 1 uses combinatorial breadth by varying multiple independent substituent groups:

  • Positioning variables: j, k, m, n (discrete integers)
  • Linker/functional group variables: J and L
  • Core substituent vectors: A and G = -E-R5
  • Electronics/sterics vectors: R1 and aryl ring substitution (R′/R″ ring is substituted by “each R2” and x 0–4 in dependent Claim 6)

This makes the claim scope hard to “design around” via single-point substitutions. A competitor typically needs to change the scaffold-level connectivity that drives the Markush acceptance. Small changes that still fall within the enumerated substitution categories remain captured.

2) Method claim creates a second infringement vector for clinical-stage products

Claim 8 adds a hepatitis C viral infection treatment method: administer a therapeutically effective amount of Claim 1 compounds or salts.

That means even if a competitor supplies an API that maps to Claim 1, the method claim can support enforcement based on commercial indication and prescribing/use evidence.

3) Composition claim adds formulation and combination leverage

Claim 7 covers a pharmaceutical composition containing a therapeutically effective amount of the Claim 1 compound (or salt) with a pharmaceutically acceptable carrier.

This matters for:

  • pill/film/capsule formulations
  • solid dispersions and excipient-based product forms
  • combination products where the Claim 1 compound is present (depending on whether the claims are asserted against the whole composition)

What do the dependent claims narrow, and where are the “decision points”?

Claim 2: a specific backbone slice

  • k = 3, j = 1, and L is absent

This locks two discrete scaffold indices and removes L flexibility. If a product falls outside that index set but remains within Claim 1, Claim 1 still covers it; if a product tries to design around, this is a useful “probability” narrowing for claim strategy.

Claim 3: restricts substituent classes and sets specific E and R5 sets

  • R1 is hydrogen or halogen
  • E is —NHS(O)— or —NHS(O2)—
  • R5 is chosen from a broad list of rings/groups (cyclopropyl to imidazolyl, each optionally substituted)

This claim forms a meaningful “subfamily”: it is less permissive than Claim 1 because it restricts R1 to H or halogen and E to sulfenamide/sulfonamide-like linkages.

Claim 4: emphasizes J and A range

  • J is —C(O)—
  • A is restricted to:
    • optionally substituted —C1-C8 alkyl with 0–3 heteroatoms O/S/N
    • optionally substituted aryl
    • optionally substituted —C1-C8 alkoxy
    • optionally substituted heteroaryl
    • optionally substituted —C3-C12 cycloalkyl
    • optionally substituted —C3-C12 heterocycloalkyl

This claim carves out a “carbonyl J + constrained A” mode.

Claim 5: forces aryl fusion at R′/R″

  • R′ and R″ together form an optionally substituted aryl ring

This is narrower than Claim 1’s “aryl or heteroaryl ring” language.

Claim 6: adds explicit aryl substitution definition

  • R′ and R″ and their attached atoms form an aryl substituted by (R2)x
  • x = 0, 1, 2, 3, or 4
  • R2 enumerates the same R2-like substituent universe seen in R1 (halogen, hydroxy, amino, CN, CF3, N3, NO2, OR4, SR4, sulfonamide and carboxamide-type substituents, etc.) plus aryl/heteroaryl/heterocyclic/carbocyclic and lower alkyl/alkenyl/alkynyl with 0–3 O/S/N

Claim 6 functions like an “overlay claim” for substitution patterns on the R′/R″ aryl motif.

Claim 7: composition

  • pharmaceutical composition with therapeutically effective amount of Claim 1 compound or salt + pharmaceutically acceptable carrier/excipient

Claims 8, 15–20: method scope in more constrained embodiments

  • Claim 8 is the base method claim.
  • Claims 15 and 18–20 describe method embodiments with specific k, j, L, aryl substitution scheme, and A limitations.
  • Claims 16–17 restrict E = —N(R3)S(Op)—, R3 = H, p = 2, and R5 to carbocyclic or heteroaryl.

What are the “most enforceable” subsets for competitive mapping?

From a landscape perspective, you typically prioritize subclaims that:

1) match how actual marketed chemotypes are drawn (ring identity and heteroaryl substitution), 2) are narrower enough to be cited in invalidity or non-infringement disputes, 3) align to likely SAR variations seen in development series.

The most decision-like dependent claims in your set are:

  • Claim 3 (R1 = H or halogen; E limited to sulfenamide/sulfonamide; R5 restricted to specific ring classes)
  • Claim 4 (J = —C(O)— and A restricted to C1–C8 alkyl/alkoxy and specific ring ranges)
  • Claim 6 and Claim 5 (how the R′/R″ aryl/heteroaryl ring is substituted)
  • Claim 15 (explicit x 0–4 substitution pattern on the aryl core with k/j fixed)
  • Claim 16–17 (E = —N(R3)S(Op)— and p = 2 with R5 class restrictions)
  • Claims 18–20 (J = —C(O)— and A is optionally substituted heteroaryl; with A = pyrazinyl in Claim 20)

These dependent claims provide practical “handles” for freedom-to-operate (FTO) assessments because they reduce the search space from the enormous Claim 1 universe.

How broad is Claim 1 in practice?

Claim 1 is highly permissive by Markush design:

  • Linkers and functional groups accept many heteroatom-containing moieties (O, S, N) and multiple oxidation states and sulfonamide-like connectivity patterns in E and substituent lists.
  • A covers multiple chemical classes: alkyl/alkenyl/alkynyl, aryl/arylalkyl, alkoxy, heteroaryl, heterocyclic, and carbocyclic.
  • R1 includes a long substituent set including halogens, strong electron-withdrawing groups (CN, CF3, nitro), and multiple carbonyl/sulfur-linked groups (C(O)R4, SO2R4, SOR4, etc.).
  • R5 allows either H or a substituted alkyl/alkenyl/alkynyl or multiple ring families, again with heteroatom constraints.
  • Aryl substitution on the R′/R″ ring is allowed via x up to 4 substituents.

This breadth tends to make the primary design-around strategy shift from “change a substituent” to “change the scaffold architecture” so that at least one required Markush-dimension mapping fails (for example, altering whether J is “absent” versus forced to be “—C(O)—” or changing connectivity that prevents E from being in the enumerated set).

What does the patent landscape look like for US 8,642,538?

A complete landscape requires bibliographic record details (priority dates, assignees, family members, citing/related patents, and prosecution history). Those data are not included in the input you provided, so a full, accurate landscape cannot be produced from the claims text alone.

What can be done strictly from the claim set is to infer landscape risk channels:

1) Direct competition within hepatitis C antivirals

The presence of a hepatitis C viral infection treatment method (Claim 8) ties the compound class to that therapeutic area. In this domain, development histories and later generics often create a dense citation network of:

  • earlier HCV-targeted chemotypes
  • follow-on analogs with substitutions in permissive Markush positions
  • formulation and combination patents around marketed regimens

2) Generics and API use risk

If a competitor’s compound reads on Claim 1, infringement risk extends to:

  • API sales for HCV treatment use (depending on jurisdictional doctrines and carve-outs)
  • formulation patents (Claim 7)
  • labeling and prescribing evidence supporting the method claim (Claim 8)

3) Follow-on “narrower embodiment” enforcement

Dependent claims (3–6 and 15–20) are structured to let the patentee assert narrower sub-classes when proving infringement of a particular competitor compound that matches only a limited slice of Claim 1.

How to read the scope for competitor mapping (practical claim tests)

A practical infringement assessment against US 8,642,538 typically uses layered filters aligned to your claim dependencies:

1) Core scaffold mapping

  • Does the compound map to Formula I or I′ connectivity with the “Y” aryl/heteroaryl ring definition? 2) J and A
  • Is J absent or is it specifically —C(O)— (or another enumerated option)?
  • Does A fall within the allowed families and sizes (notably cycloalkyl/cycloalkyl ranges in Claim 4; heteroaryl including pyrazinyl in Claims 18–20)? 3) G = -E-R5
  • Is E absent, or does E match one of the enumerated E functional group templates?
  • Is R5 the correct allowed type (H vs substituted ring/chain), and does it match the class requirements in Claims 3, 16, 17, 10, 11? 4) R1 substituent class
  • Is R1 restricted to H/halogen (Claim 3), or does it match the expansive R1 definition in Claim 1? 5) Aryl substitution pattern (x)
  • If asserting via Claim 6/15, check aryl substitution count and allowed R2 substituent families.

This layered approach reflects how Claim 1 breadth is “pinned down” by dependent embodiments.

Key Takeaways

  • US 8,642,538 claim scope is combinatorial: Claim 1 allows wide variation across J, A, E/R5, R1, and an aryl/heteroaryl ring substitution pattern, anchored to a hepatitis C treatment method (Claim 8) and a composition claim (Claim 7).
  • The most actionable narrowing in your set comes from Claims 3, 4, 5, 6, and 15–20, each of which fixes discrete indices and constrains functional groups or substituent classes (notably R1 = H/halogen; E = —NHS(O)— or —NHS(O2)—; J = —C(O)—; A heteroaryl including pyrazinyl).
  • Landscape risk is channel-based rather than citation-based from the inputs provided: any competitor compound that fits the enumerated Markush dimensions plus the hepatitis C indication pathway becomes exposed under compound, composition, and method theories.

FAQs

1) Is Claim 8 limited to a specific HCV target or mechanism?

No target or mechanism is stated in your provided claim text. Claim 8 is a hepatitis C infection treatment method defined by administration of a Claim 1 compound (or salt).

2) Does Claim 1 require J to be present?

No. Claim 1 explicitly allows J is absent and also provides enumerated options when J is present.

3) What does Claim 3 change relative to Claim 1?

Claim 3 narrows the substituent universe by setting R1 = H or halogen, restricting E to —NHS(O)— or —NHS(O2)—, and limiting R5 to specified ring classes (each optionally substituted).

4) How do Claims 18–20 narrow the heteroaryl selection?

They require J = —C(O)— and A is optionally substituted heteroaryl, then pin down A = pyrazinyl in Claim 20.

5) What do x values do in Claim 6 and Claim 15?

They bound the number of substituents on the aryl motif formed by R′ and R″: x = 0 to 4. The substituent identity must also match the enumerated R2 universe.


References

[1] United States Patent US 8,642,538. “A method of treating a hepatitis C viral infection” and compound claims with Formula I/I′ definitions (claims provided in prompt).

More… ↓

⤷  Start Trial


Drugs Protected by US Patent 8,642,538

Applicant Tradename Generic Name Dosage NDA Approval Date TE Type RLD RS Patent No. Patent Expiration Product Substance Delist Req. Patented / Exclusive Use Submissiondate
Abbvie VIEKIRA XR dasabuvir sodium; ombitasvir; paritaprevir; ritonavir TABLET, EXTENDED RELEASE;ORAL 208624-001 Jul 22, 2016 DISCN Yes No 8,642,538 ⤷  Start Trial Y Y TREATMENT OF HCV INFECTION USING PARITAPREVIR ⤷  Start Trial
Abbvie TECHNIVIE ombitasvir; paritaprevir; ritonavir TABLET;ORAL 207931-001 Jul 24, 2015 DISCN Yes No 8,642,538 ⤷  Start Trial Y Y TREATMENT OF HCV INFECTION USING PARITAPREVIR ⤷  Start Trial
Abbvie VIEKIRA PAK (COPACKAGED) dasabuvir sodium; ombitasvir, paritaprevir, ritonavir TABLET;ORAL 206619-001 Dec 19, 2014 DISCN Yes No 8,642,538 ⤷  Start Trial Y Y TREATMENT OF HCV INFECTION USING PARITAPREVIR ⤷  Start Trial
>Applicant >Tradename >Generic Name >Dosage >NDA >Approval Date >TE >Type >RLD >RS >Patent No. >Patent Expiration >Product >Substance >Delist Req. >Patented / Exclusive Use >Submissiondate

International Family Members for US Patent 8,642,538

Country Patent Number Estimated Expiration Supplementary Protection Certificate SPC Country SPC Expiration
European Patent Office 2340029 ⤷  Start Trial CA 2015 00013 Denmark ⤷  Start Trial
European Patent Office 2340029 ⤷  Start Trial PA2015011 Lithuania ⤷  Start Trial
European Patent Office 2340029 ⤷  Start Trial C20150019 00156 Estonia ⤷  Start Trial
European Patent Office 2340029 ⤷  Start Trial 92667 Luxembourg ⤷  Start Trial
>Country >Patent Number >Estimated Expiration >Supplementary Protection Certificate >SPC Country >SPC Expiration

Make Better Decisions: Try a trial or see plans & pricing

Drugs may be covered by multiple patents or regulatory protections. All trademarks and applicant names are the property of their respective owners or licensors. Although great care is taken in the proper and correct provision of this service, thinkBiotech LLC does not accept any responsibility for possible consequences of errors or omissions in the provided data. The data presented herein is for information purposes only. There is no warranty that the data contained herein is error free. We do not provide individual investment advice. This service is not registered with any financial regulatory agency. The information we publish is educational only and based on our opinions plus our models. By using DrugPatentWatch you acknowledge that we do not provide personalized recommendations or advice. thinkBiotech performs no independent verification of facts as provided by public sources nor are attempts made to provide legal or investing advice. Any reliance on data provided herein is done solely at the discretion of the user. Users of this service are advised to seek professional advice and independent confirmation before considering acting on any of the provided information. thinkBiotech LLC reserves the right to amend, extend or withdraw any part or all of the offered service without notice.