Last Updated: July 10, 2026

Patent: 10,206,910


✉ Email this page to a colleague

« Back to Dashboard


Summary for Patent: 10,206,910
Title:Apilimod for use in the treatment of renal cancer
Abstract: The present disclosure relates to methods for treating renal cancer with apilimod and related compositions and methods.
Inventor(s): Beeharry; Neil (Guilford, CT), Gayle; Sophia (East Haven, CT), Landrette; Sean (Meriden, CT), Beckett; Paul (Yorktown Heights, NY), Conrad; Chris (Guilford, CT), Xu; Tian (Guilford, CT), Rothberg; Jonathan M. (Guilford, CT), Lichenstein; Henri (Guilford, CT)
Assignee: LAM Therapeutics, Inc. (Guilford, CT)
Application Number:15/524,844
Patent Claims:see list of patent claims
Patent landscape, scope, and claims summary:

United States Patent 10,206,910: Claims Assessment and US Patent Landscape for Apilimod Dimesylate + VEGF Inhibitor in Clear Cell Renal Carcinoma

What does US 10,206,910 claim in legal terms?

US 10,206,910 is drafted as a therapeutic method for clear cell renal carcinoma (ccRCC) using apilimod dimesylate in combination with a VEGF-pathway inhibitor, with optional escalation to additional agents and specified sub-sets for VEGF and immuno-oncology classes.

Claim-set scope (independent claim anchor and dependent expansions)

Claim Core limitation Operational breadth
1 Method treating ccRCC by administering a therapeutically effective amount of apilimod dimesylate with a VEGF inhibitor Combination-dosing method in ccRCC; VEGF inhibitor not limited in Claim 1
2 Further includes at least one additional active agent Expands to “triple” or “multi” regimens
3-4 Additional agent can be therapeutic or non-therapeutic; therapeutic agent is from broad oncology classes including protein kinase inhibitors Broad class-level coverage for co-therapies
6 VEGF inhibitor limited to pazopanib or sorafenib (or combination) narrows VEGF subset to two TKIs
7-8 If the therapeutic agent is a PD-1/PD-L1 pathway inhibitor, it is selected from a defined list of antibodies narrows immune co-therapy to specific listed PD-1/PD-L1 agents
9-11 Adds optional non-therapeutic agents to ameliorate apilimod side effects, including antiemetics and other symptomatic agents Creates “side-effect management” dependent coverage
12 Requires apilimod amount effective to inhibit PIKfyve kinase activity in cancer cells Adds a mechanism-based quantitative anchor (target engagement frame)
13 Specifies ccRCC is refractory to standard treatment or metastatic Limits patient population and treatment setting
14 Composition form suitable for oral or IV Delivery modality constraint
15 VEGF inhibitor includes a broader list (bevacizumab, sunitinib, pazopanib, axitinib, sorafenib, regorafenib, lenvatinib, motesanib, vandetanib) Broadens VEGF subset compared with Claim 6

Key construction points

  • The invention’s center of gravity is combination therapy: apilimod dimesylate plus a VEGF inhibitor to treat ccRCC.
  • Dependent claims create multiple claim “slices”: (i) VEGF subset lists, (ii) immune-oncology co-therapy lists, (iii) mechanism (PIKfyve inhibition), (iv) patient setting (refractory/metastatic), and (v) supportive care agents to manage apilimod tolerability.

What is the claim’s critical novelty axis?

The claim is not a method of apilimod monotherapy; it is a combination method with a VEGF inhibitor, and its dependent structure tries to lock in:

  1. Specific therapeutic context: clear cell renal carcinoma.
  2. Specific pharmacological pairing: apilimod dimesylate + VEGF inhibitor.
  3. Mechanistic quantification: dosing tied to PIKfyve kinase inhibition (Claim 12).
  4. Regimen modularity: optional addition of other therapeutic or non-therapeutic agents, including PD-1/PD-L1 inhibitors (Claims 2-4, 7-8).
  5. VEGF inhibitor pinning through both narrow and broad enumerations (Claims 6 and 15).

From a patentability and enforcement perspective, this structure typically faces two pressure points:

  • Combination obviousness: VEGF inhibitors are standard in ccRCC, so the novelty must lie in the rationale and evidence that apilimod dimesylate provides a non-obvious complementary effect when paired with VEGF inhibition.
  • Enablement and sufficiency across the enumerated VEGF inhibitor set: the broader the VEGF list (Claim 15), the harder it is to justify that apilimod works similarly across different VEGF-targeting mechanisms and kinase binding profiles without overextending disclosure.

How likely are these claims to survive obviousness and written description challenges in the US?

Without the patent specification text, priority date, prosecution history, and the cited references used in the file wrapper, the evaluation rests on the claim language’s breadth and typical US PTAB and district court stress tests for similar claim formats.

1) Combination method claims are exposed to a “routine pairing” narrative

A PTAB obviousness strategy for a combination method usually proceeds as:

  • Identify apilimod dimesylate as a known compound (or as disclosed in related documents) with a known biological target.
  • Identify VEGF inhibitors as standard ccRCC therapy.
  • Argue that a POSA would combine the known agent with VEGF inhibition for improved anti-tumor effect and/or pathway synergy.
  • Use generic evidence of VEGF-driven tumor survival and the general rationale of multi-pathway blockade.

What Claim 12 tries to do

  • Claim 12 converts apilimod dosage into a target engagement limitation: “amount effective to inhibit PIKfyve kinase activity in cancer cells.”
  • Target engagement-based limitations sometimes help rebut arguments that the combination is speculative by requiring a specific pharmacodynamic relationship.

What the rest of the claim set does not do

  • The claims do not explicitly require a measurable clinical endpoint beyond “therapeutically effective amount.”
  • They do not tie synergy to a specific biomarker response in ccRCC (at least in the claim text provided).
  • They do not require a specific scheduling (concurrent vs sequential) beyond administration in combination.

Net effect: the breadth is still vulnerable unless the specification provides strong, ccRCC-specific synergy data with VEGF inhibitors and supports the mechanism-driven dosing.

2) Breadth expansion via VEGF lists increases both coverage and vulnerability

Claim 6 narrows VEGF inhibitors to pazopanib or sorafenib. Claim 15 expands to a broader list including bevacizumab and multiple TKIs.

Critical difference

  • Bevacizumab is an antibody ligand trap, not a kinase inhibitor. Pairing apilimod with bevacizumab raises questions about whether the same disclosed rationale applies across VEGF pathway blockade modalities.
  • Including multiple VEGF TKIs (sunitinib, axitinib, regorafenib, lenvatinib, motesanib, vandetanib) can be argued as “reasonably related” within VEGF inhibition, but it can also be argued as a lack of support if the disclosure only tests a subset.

3) The “PD-1/PD-L1 pathway inhibitor” slice depends heavily on listing completeness and support

Claims 7-8 list PD-1/PD-L1 agents including:

  • pembrolizumab, avelumab, atezolizumab, nivolumab
  • pidilizumab, MSB0010718C, MEDI4736

This kind of list typically faces:

  • Written description risk if the specification does not explicitly support each listed agent.
  • Enablement risk if the combination mechanism depends on drug-specific properties (dose, scheduling, immunogenicity) and the specification does not provide adequate regimen support.

4) Supportive care dependent claims (ondansetron/others; pindolol/risperidone)

Claims 9-11 add non-therapeutic agents selected to ameliorate apilimod side effects.

For patentability, such dependent claims can be easier to defend as they often reduce prior art matching to the exact supportive-care bundle. For infringement and validity, they still tend to be:

  • Narrower in coverage (requires use of listed supportive drugs).
  • Potentially less central for commercial licensing unless the specification frames tolerability management as part of the treatment protocol.

5) Patient subset (refractory or metastatic) can be a partial shield, not a full one

Claim 13 narrows to refractory or metastatic ccRCC.

That limitation often reduces prior art matching if earlier documents describe earlier-line settings or non-metastatic disease. But in practice, many oncology references cover metastatic disease broadly, so it is not a guarantee against combination obviousness.

How does the claim language map to an actionable infringement risk profile?

Infringement “core” the market will actually do

The most infringement-relevant commercial activity is:

  • Using apilimod dimesylate in ccRCC
  • Paired with a VEGF inhibitor such as the widely used class (pazopanib, sunitinib, bevacizumab, sorafenib/axitinib).

Claim 15 is the largest “umbrella” for VEGF inhibitors; if enforcement relies on broad enumerations, it likely targets the most clinically common VEGF combinations.

Infringement “edge” areas

  • If apilimod is only tested/used with VEGF inhibitors not listed, enforcement on these claims weakens.
  • If apilimod dosing is not framed as inhibiting PIKfyve activity (Claim 12), then the mechanism-based dependent claim may not be strongest for enforcement, depending on how the patent is litigated.
  • If clinical practice uses PD-1/PD-L1 inhibitors commonly but not specifically in the listed forms, then Claims 7-8 may be harder to enforce.
  • Supportive-care dependent claims only matter if the exact antiemetic or other listed non-therapeutic agents are used as part of the protocol.

Patent landscape implications for US 10,206,910 (how the field will contest it)

This assessment is about landscape mechanics: where the most likely competing patents and challenges cluster, given the claim’s pillars (apilimod, PIKfyve, ccRCC, VEGF inhibitors, immunotherapy co-therapy).

Likely competitive clusters

  1. Apilimod and PIKfyve-related oncology

    • Patents and applications that claim apilimod or PIKfyve modulation for cancers broadly.
    • The primary question in the landscape becomes whether those earlier disclosures include ccRCC and/or VEGF combination regimens.
  2. VEGF inhibitor combinations in ccRCC

    • Many existing patents cover VEGF inhibition with:
      • immunotherapy,
      • other targeted therapies,
      • standard-of-care multi-agent regimens.
    • Those documents do not necessarily mention apilimod, but they can drive obviousness arguments once apilimod is treated as a known oncology agent.
  3. Immuno-oncology combination regimens

    • PD-1/PD-L1 combinations are heavily patented in ccRCC.
    • Claims 7-8 try to anchor co-therapy using listed checkpoint inhibitors, but the landscape may include numerous generic combination disclosures that can be leveraged for obviousness depending on how apilimod is characterized.

Most likely legal attack paths

  • Obviousness based on known apilimod + standard VEGF therapy: strongest against Claim 1 and Claim 6/15 broad VEGF sets unless there is ccRCC-specific synergy evidence.
  • Obviousness using immunotherapy combination documents: to attack Claims 7-8 if those agents are treated as standard add-ons rather than specific to apilimod.
  • Written description/enablement for the breadth of VEGF listings and checkpoint inhibitor lists: hardest for Claim 15 and Claims 8’s specific antibody list if the specification disclosure is narrow.

Summary of claim-by-claim vulnerability signals

Claim Main likely vulnerability Why
1 Combination obviousness ccRCC + VEGF inhibitors are standard; apilimod must show non-obvious ccRCC pairing rationale
2-4 Overbreadth in “additional active agent” Open-ended add-on language can be attacked as routine or unsupported expansion
6 Narrower VEGF set Easier to defend than broad lists if spec supports pazopanib/sorafenib pairing
7-8 Enablement / written description of listed antibodies Must be supported across each listed agent and regimen form
9-11 Lower strategic importance, narrower enforcement Requires specific supportive drugs; validity is not usually the main battlefield
12 Potentially stronger defensive anchor Converts dose into a target-engagement limitation (PIKfyve inhibition)
13 Partial novelty shield Limits to refractory/metastatic; may still be anticipated by metastatic oncology literature
14 Delivery route support check If spec supports oral and IV, this is usually a non-issue; otherwise it can become a support/enablement issue
15 Breadth and modality spread Includes bevacizumab and many VEGF TKIs; increases support burden

Key Takeaways

  • US 10,206,910 is a ccRCC treatment method built around a combination: apilimod dimesylate + VEGF inhibitor, with dependent claims expanding into specific VEGF subsets, PD-1/PD-L1 checkpoint inhibitors, optional additional agents, and mechanism-based dosing via PIKfyve inhibition.
  • The primary enforceability pressure point is combination obviousness: VEGF inhibitors are standard in ccRCC, so the claims need strong, ccRCC-specific support for why apilimod is not a routine add-on.
  • The main validity risk concentrates on breadth: Claim 15’s wide VEGF list (including bevacizumab plus multiple TKIs) and Claim 8’s enumerated checkpoint antibodies increase exposure to written description and enablement challenges if the specification only tests subsets.
  • The strongest claim-language defense lever is Claim 12’s PIKfyve inhibition dosing anchor, which can constrain arguments that apilimod’s role is speculative or untethered to its cellular target.
  • Commercial infringement risk will track the most common ccRCC regimens pairing a VEGF inhibitor with new targeted agents; enforcement will most likely focus on the VEGF-inhibitor lists in Claim 15 and/or Claim 6 rather than the supportive-care dependent claims.

FAQs

  1. What is the central claim scope of US 10,206,910?
    A method to treat clear cell renal carcinoma by administering apilimod dimesylate with a VEGF inhibitor, with optional additional agents.

  2. Which dependent claims narrow the VEGF inhibitor selection?
    Claim 6 limits VEGF inhibitors to pazopanib or sorafenib; Claim 15 expands to a broader enumerated list that includes bevacizumab and multiple VEGF TKIs.

  3. Does the patent require a specific mechanism of action?
    Yes in dependent Claim 12: dosing must be effective to inhibit PIKfyve kinase activity in cancer cells.

  4. Are immunotherapy agents covered?
    Yes. Dependent Claims 7-8 cover PD-1/PD-L1 pathway inhibitors, listed as pembrolizumab, avelumab, atezolizumab, nivolumab, pidilizumab, MSB0010718C, and MEDI4736.

  5. Do the claims include supportive-care drugs?
    Yes. Dependent Claims 9-11 include non-therapeutic agents chosen to ameliorate apilimod side effects, including antiemetics (ondansetron/granisetron/dolsetron/palonosetron) and other agents (pindolol/risperidone).


References

[1] United States Patent No. 10,206,910 (claims as provided by user prompt).

More… ↓

⤷  Start Trial

Details for Patent 10,206,910

Applicant Tradename Biologic Ingredient Dosage Form BLA Approval Date Patent No. Expiredate
Genentech, Inc. AVASTIN bevacizumab Injection 125085 February 26, 2004 ⤷  Start Trial 2035-11-06
Merck Sharp & Dohme Llc KEYTRUDA pembrolizumab For Injection 125514 September 04, 2014 ⤷  Start Trial 2035-11-06
Merck Sharp & Dohme Llc KEYTRUDA pembrolizumab Injection 125514 January 15, 2015 ⤷  Start Trial 2035-11-06
Genentech, Inc. TECENTRIQ atezolizumab Injection 761034 May 18, 2016 ⤷  Start Trial 2035-11-06
Genentech, Inc. TECENTRIQ atezolizumab Injection 761034 March 08, 2019 ⤷  Start Trial 2035-11-06
Emd Serono, Inc. BAVENCIO avelumab Injection 761049 March 23, 2017 ⤷  Start Trial 2035-11-06
>Applicant >Tradename >Biologic Ingredient >Dosage Form >BLA >Approval Date >Patent No. >Expiredate

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.