|
Patent landscape, scope, and claims: |
US Patent 9,974,746 (injectable nanoparticulate active agent; flake-like aggregation reduction): claim scope, infringement levers, and US patent landscape
US Drug Patent 9,974,746 protects an injectable nanoparticulate drug composition and a process to make it, where the core novelty is a flake-like aggregation reducing agent (specific buffers at pH > 7.0 or specific sugars) used with nanoparticulate active agent (poorly soluble in the liquid) and surface stabilizers, while controlling particle size and coarse particle counts (particles above 10 μm and above 25 μm). The claims are broad on stabilizer choice and phase descriptors but narrow on (i) the specific aggregation-reduction agents and (ii) the quantitative coarse-particle limits.
What does US Patent 9,974,746 claim and how broad is its scope?
Core claim coverage (independent claim 1):
- An injectable nanoparticulate active agent composition made by a method that includes:
- (a) preparing a dispersion of a nanoparticulate active agent and at least one surface stabilizer, where:
- active agent has effective average particle size < 2000 nm
- dispersion uses a liquid in which the active agent is poorly soluble
- includes at least one surface stabilizer
- (b) adding a flake-like aggregation reducing agent to that dispersion, where the reducing agent is:
- (i) a buffer chosen from: phosphate buffer, acetate buffer, citrate buffer, sodium phosphate, potassium phosphate, sodium acetate resulting in pH > 7.0, or
- (ii) a sugar chosen from: sucrose, mannitol, dextrose
- composition has stringent limits on coarse particles:
- ≤ 6,000 active agent particles > 10 μm
- ≤ 600 active agent particles > 25 μm
Claim 2–3 (aggregation reducing agent subtypes):
- Claim 2 locks buffer subset (same list).
- Claim 3 locks sugar subset (sucrose, mannitol, dextrose).
Claim 4 (active ingredient example):
- Claim 4 specifies meloxicam as the active agent.
Claim 5 (nanoparticle size narrowing ladder):
- Replaces <2000 nm with many alternative ceilings down to <50 nm (each listed value is a separate permitted boundary).
Claims 6–8 (coarse-particle limit narrowing ladders):
- Claim 6 tightens to:
- ≤ 3,000 particles > 10 μm
- ≤ 300 particles > 25 μm
- Claim 7 and 8 provide even lower ceilings (multiple alternative values), e.g. for >25 μm and >10 μm, respectively.
Claim 9 (surface stabilizer categories + expansive exemplars):
- “Selected from” broad classes (non-ionic, ionic, anionic, cationic, zwitterionic).
- Dependent claim 10 enumerates an extremely large roster of specific stabilizers including surfactants, polymers (PEG, PVP, celluloses), lipids, cationic polymers, and charged phospholipids.
Claims 11–13 (active agent phase + method timing):
- Claim 11 allows crystalline, amorphous, semi-crystalline, or any combination.
- Claim 12 says steps (a) and (b) are simultaneous.
- Claim 13 says steps (a) and (b) are sequential.
Claim 14–15 (excipient add-ons):
- Claim 14 allows one or more excipients.
- Claim 15 lists typical excipient classes (binding, filling, lubricating, suspending, preservatives, wetting, disintegrants, etc.).
Claim scope takeaway
- The “hard” limitation set is:
(i) nanoparticle size ceiling (<2000 nm or narrower values), (ii) poorly soluble drug in the liquid, (iii) presence of surface stabilizer, (iv) flake-like aggregation reducing agent limited to the specific buffer list at pH > 7.0 or specific sugars, and (v) coarse particle count limits (10 μm and 25 μm thresholds).
- The “soft” limitation set is:
broad stabilizer genus and the option to run steps simultaneously or sequentially; active phase is not restricted; excipients are permitted.
Which elements are most important for infringement: the buffer/sugar and particle-count thresholds?
Most infringement-sensitive limitations
-
Flake-like aggregation reducing agent identity
- Only two sanctioned baskets:
- buffers from the specified list that lead to pH > 7.0, or
- sugars from the specified list (sucrose, mannitol, dextrose).
- A product that uses a different buffer system (or a sugar not listed) is a potential design-around.
-
pH > 7.0 requirement (for buffers)
- Buffer basket is “resulting in” pH > 7.0. That makes the pH setting operationally defining for that branch.
-
Coarse particle count limits
- Claim 1 imposes numeric maximums for particles above 10 μm and above 25 μm.
- These limits are unusual and are likely to drive assay and regulatory-style particulate testing methodology.
- A competitor can attempt design-around by controlling coarse particles above those thresholds (but that can be technically difficult for injectable nanoparticulate dispersions).
Least infringement-sensitive limitations
- Surface stabilizer list is expansive and likely to encompass many standard stabilizers used in nanoparticle injectable formulations.
- Phase is not restricted.
- Timing (simultaneous vs sequential addition) is both claimed.
How do the dependent claims narrow the particle size and particle-count ranges?
Nanoparticle “effective average particle size” ceiling ladders (Claim 5)
- Base: < 2000 nm
- Dependent options include: <1900, <1800, … down to <50 nm.
Coarse particle count ceilings
- Claim 1 baseline:
- ≤ 6,000 particles > 10 μm
- ≤ 600 particles > 25 μm
- Claim 6 baseline tighter:
- ≤ 3,000 particles > 10 μm
- ≤ 300 particles > 25 μm
- Claim 7 tightens for >25 μm:
- ranges listed: <1000, <900, <800, … down to <50 particles >25 μm
- Claim 8 tightens for >10 μm:
- ranges listed: <10,000, <9,000, <8,000, … down to <1,000 particles >10 μm
Practical claim layering
- Claim 1 is already a “tight” particulate-control claim.
- Claims 5–8 create a set of alternative narrower formulations. If an accused product matches any narrower ladder value, the narrower dependent claim may become easier to plead.
How does US 9,974,746 treat the surface stabilizer: does it allow almost anything?
Categorical permission
- Claim 9 allows stabilizer selection within broad charge categories:
- non-ionic, ionic, anionic, cationic, zwitterionic
Exemplars in Claim 10
- Claim 10 enumerates a large number of specific stabilizers across:
- surfactants (e.g., sodium lauryl sulfate, benzalkonium chloride variants in the list, dioctyl sulfosuccinate)
- polymers (PEG, PVP, poloxamers, celluloses, polyvinyl alcohol)
- lipids/phospholipids and charged phospholipids
- cationic polymers and polysaccharides
- many glucoside-based nonionic surfactants
- This structure suggests claim drafters intend to capture multiple formulation chemistries while keeping the novelty in the flake-like aggregation reducing agent + particulate-count control.
What is the “flake-like aggregation reducing agent” scope and how can competitors design around it?
Two authorized mechanisms
- Buffer route: phosphate/acetate/citrate (and specific sodium/potassium phosphate and sodium acetate variants) that yields pH > 7.0.
- Sugar route: sucrose, mannitol, dextrose.
Design-around vectors (by claim structure)
- Swap to a buffer outside the listed group (e.g., different buffering salts) while maintaining dispersion stability.
- Use a sugar not listed, or a combination where the “flake-like aggregation reducing agent” is not any of the listed sugars.
- Maintain nanoparticle size and stabilizer, but fail the coarse particle count thresholds (10 μm and/or 25 μm) by allowing more large particles.
Most direct design-around
- Use neither:
- listed buffers producing pH > 7.0, nor
- listed sugars.
This attacks the independent claim’s limiting “flake-like aggregation reducing agent is selected from…” language.
What is the process claim coverage: does it require simultaneity, sequence, or either?
Claim 1 is a method that includes steps (a) and (b). Dependent claims expand permissibility:
- Claim 12: steps (a) and (b) can be performed simultaneously.
- Claim 13: steps can be performed sequentially.
This reduces process-timing defenses. If an accused process includes both the nanoparticle dispersion with stabilizer and subsequent/parallel addition of the specified flake-like aggregation reducing agent, timing is unlikely to be a path to avoid.
What active ingredient is protected: is it limited to meloxicam or broader?
- The independent claim 1 is written as a generic “nanoparticulate active agent.”
- Claim 4 explicitly covers meloxicam.
- That structure typically means:
- the patent covers nanoparticulate formulations broadly (within the technical limitations), and
- meloxicam is a specifically called-out dependent scope point.
From a litigation posture standpoint, “active agent is meloxicam” can matter for:
- specificity of prior art mapping,
- commercial relevance (if the product is meloxicam),
- and whether an accused product’s API matches the dependent claim.
Where does 9,974,746 sit in the US nanoparticle drug formulation landscape?
Claim-positioning relative to common nanoparticle patents
US nanoparticle patents often cluster into:
- Particle size and stabilization patents (broad on stabilizers)
- Surface chemistry and coating patents
- Formulation excipient patents (buffers, sugars, tonicity agents)
- Manufacturing methods (milling, precipitation, homogenization)
- Particulate and stability control patents (aggregation, flocculation, coarse particle reduction)
US 9,974,746 is strongest in the intersection of:
- nanoparticle dispersion with surface stabilizers,
- poorly soluble drug in the liquid,
- explicit coarse particle-count ceilings,
- and a narrow set of aggregation-reduction agents.
That is a narrower, more assay-anchored formulation niche than many general nanoparticle coating patents.
Field risk to competitors
- Competitors cannot rely only on using a nanoparticulate dispersion with stabilizers; they must also:
- meet the same controlled “flake-like aggregation” reduction approach and
- hit the coarse particle-count limits.
What US Orange Book or FDA listing risks follow from this patent structure?
This prompt requests a detailed landscape tied to the specific US patent, but no FDA listing identifiers, Orange Book numbers, application numbers (NDA/ANDA), assignee, filing history, or expiration dates are provided for US 9,974,746 in the input. Without those, an Orange Book-style mapping (related patents, listing status, and FDA reference product linkage) cannot be produced as a complete and accurate answer.
Given the constraints, the analysis below stays at the claim-set and landscape-logic level rather than generating an Orange Book chronology.
Patent estate mapping: what other claim families are typically adjacent to 9,974,746?
Even without the patent family document list, the claim architecture indicates adjacent litigation and freedom-to-operate risk areas:
-
Nanoparticulate poorly soluble drug dispersions
- Claims that define dispersion media, stabilizer type, and nanoparticle size.
-
Aggregation control mechanisms
- Patents that claim:
- flake-like aggregation reduction
- anti-aggregation buffer/sugar additives
- pH-dependent aggregation control.
-
Particulate control and specification-linked claims
- Patents that include:
- counts of particles above specific micrometer thresholds.
- These tend to be paired with analytical methods (not shown here).
-
Secondary formulation patents
- Excipients, tonicity, preservatives, and delivery format constraints.
Because claim 10 enumerates a wide stabilizer roster, competitors facing an infringement allegation are more likely to defend via:
- the specific additive identity (buffer/sugar),
- the pH condition,
- or the coarse particle-count results.
How strong is the claim against generic or follow-on nanoparticle formulations?
Strength indicators inside claim language
- The claim includes:
- a defined particle size ceiling for “effective average particle size”
- explicit micrometer particle-count thresholds
- a defined list of flake-like aggregation reducing agents
- explicit pH condition for buffers
- Those are objective constraints that can be tested.
Weakness indicators
- The stabilizer component is broad and likely easy to replicate.
- The “injectable nanoparticulate” framing might not exclude many nanoparticle formulations unless they fail the additive identity or particulate-count limits.
Likely litigation battlegrounds
- Whether the accused formulation uses one of the listed buffers/sugars and achieves the required pH.
- Whether the accused formulation meets the particle-count limits for >10 μm and >25 μm.
- Whether particle sizing and “effective average particle size” are measured in a way consistent with claim interpretation.
Key Takeaways
- US 9,974,746 is a nanoparticulate injectable formulation patent whose enforceability hinges on (1) the identity of the flake-like aggregation reducing agent (specific buffers yielding pH > 7.0 or specific sugars) and (2) numeric coarse particle counts (≤ 6,000 particles >10 μm and ≤ 600 particles >25 μm, with tighter dependent ladders).
- The patent grants wide latitude on surface stabilizers (broad categories plus extensive exemplars) and does not restrict crystalline/amorphous phase.
- Design-around is most feasible by changing the aggregation reducing agent outside the listed buffer/sugar group or by failing the micrometer particle-count thresholds.
- Process-timing arguments are weak because claims cover simultaneous or sequential addition of the key reducing agent.
FAQs
-
Can an injectable nanoparticulate formulation avoid infringement by using a different buffer system than phosphate/acetate/citrate?
The independent claim requires the flake-like aggregation reducing agent be selected from the listed buffer group (with pH > 7.0) or listed sugars.
-
Does changing the surface stabilizer type provide a safe harbor from US 9,974,746?
No. Surface stabilizer scope is broad, and claim 10 lists many possible stabilizers across charges.
-
What matters more for infringement risk: nanoparticle size (<2000 nm) or the coarse particle limits (>10 μm, >25 μm)?
Both are limiting. The coarse particle counts are unusually specific and are often the most measurable and defensible differentiator.
-
Does the patent cover both simultaneous and sequential addition of the aggregation reducing agent?
Yes. Dependent claims explicitly cover both timing modes.
-
Is meloxicam required to be the active ingredient to infringe?
Claim 1 is not limited to meloxicam; meloxicam is covered in the dependent claim.
More… ↓
⤷ Start Trial
|
