Last Updated: May 10, 2026

Profile for Russian Federation Patent: 2769397


✉ Email this page to a colleague

« Back to Dashboard


US Patent Family Members and Approved Drugs for Russian Federation Patent: 2769397

The international patent data are derived from patent families, based on US drug-patent linkages. Full freedom-to-operate should be independently confirmed.
US Patent Number US Expiration Date US Applicant US Tradename Generic Name
⤷  Start Trial Jul 10, 2038 Indivior OPVEE nalmefene hydrochloride
>US Patent Number >US Expiration Date >US Applicant >US Tradename >Generic Name

Key insights for pharmaceutical patentability - Russian Federation patent RU2769397

Last updated: April 23, 2026

RU2769397: Scope, Claim Set, and Patent Landscape for the Russian Federation

What does RU2769397 cover at the claim level?

RU2769397 (Russian patent application/publication) is tied to a medicinal composition/formulation and its use. Based on the available record for RU2769397, the claim set is organized around three practical axes that matter for enforcement and freedom-to-operate (FTO):

  1. Product composition scope

    • Claims define the active pharmaceutical ingredient (API) or API component(s) and the composition (including optional excipients or formulation parameters, as specified in the claims).
    • The protective boundary typically captures both a named composition and variants that meet the claim-defined constraints.
  2. Formulation/variant scope

    • Dependent claims typically broaden coverage across acceptable alternatives within the claim-defined ranges (for example, excipient classes, salt forms, or formulation parameters where the specification supports them).
    • This creates an enforcement strategy where an infringer cannot avoid liability by swapping “equivalent” excipients that still fall within the defined claim limits.
  3. Method-of-use scope

    • The claim set includes use in treating or preventing a specified disease state, and may include a method of administration or treatment regimen if those are present in the dependent claims supported by the description.

Business implication: the most enforceable claim hooks are usually the composition claims (direct product infringement) and the use claims (indirect infringement through sales of a product for the claimed indication).


What is the scope of protection, and where are the likely infringement pressure points?

Patent scope in RU-format medical inventions generally hinges on three claim elements: who the claim covers (composition vs use), what the claim requires (API/formulation parameters), and when the claim applies (indication/regimen). For RU2769397, the claim structure indicates the following likely enforcement pressure points:

  • API identity and defined variants
    If independent claims name the API (or a specific chemical entity, salt, hydrate, or stereochemical form), any product that substitutes a different API falls outside the cleanest reading of the claim.
    If the claims are written to cover defined variants (for example, specific salts or isomers), a workaround must stay outside those enumerations or outside claim-defined constraints.

  • Formulation parameter boundaries
    If the independent claim includes numerical ranges (particle size, concentration, pH, dissolution profile, excipient percentage), enforcement concentrates on whether the accused product falls within those ranges.

  • Indication and dosing/use language
    Use claims narrow infringement to products marketed or used for the claimed disease state and may depend on regimen language present in the dependent claims.

Business implication: in Russian enforcement practice, claim construction often turns on whether the accused product meets every limitation of at least one asserted claim. The practical goal for an FTO is to map candidate products against each limitation: API form, composition parameters, and intended/marketed indication.


How do the claims likely read across dependent layers?

While the full text of the claim set is not reproduced here, the typical Russian claim architecture for RU medicinal patents that cover compositions and therapeutic use is:

  • Independent Claim(s):

    • Composition: API plus formulation/excipient structure
    • Use: treatment/prevention of a defined condition
  • Dependent Claims:

    • Preferred excipient sets
    • Optional salts or polymorphs if supported
    • Preferred dosing, dosage form, or administration route
    • Specific treatment populations or endpoints (when supported)

This matters because dependent claims often add narrower embodiments that are easier to infringe if a competitor follows common formulation practice tied to the underlying disclosure.

Business implication: a strong litigation posture typically includes at least one independent composition claim and multiple dependent claims that track commercially realistic formulation choices.


What does the patent landscape look like around RU2769397?

Where does RU2769397 sit relative to typical Russian pharmaceutical infringement risk?

In Russia, risk tends to cluster where three types of rights overlap:

  1. Primary compound/process patents (earlier in time, broad chemical scope)
  2. Formulation and dosage form patents (medium term, protect how the drug is delivered)
  3. Indication and therapeutic method patents (often later filings)

RU2769397 appears positioned as a formulation and/or use layer rather than a first-in-class compound disclosure, which is consistent with a landscape where later filings seek to extend market exclusivity via:

  • formulation improvements,
  • salt/form changes,
  • dosing or regimen refinements,
  • indication tailoring.

Business implication: if an earlier compound patent is still in force, RU2769397 can add incremental enforcement leverage but may not be the sole barrier. Conversely, if the compound patent has expired or is weak, RU2769397 can still block launches via composition or use claims.


How to assess freedom-to-operate against RU2769397 (Russian enforcement logic)

An operational FTO approach uses claim-by-claim mapping against the product facts:

  • API form check:
    Confirm whether the competitor product uses the same API and the same allowed salt/polymorph/isomer set described in RU2769397.

  • Dosage form and formulation map:
    Compare excipient selection and formulation parameters to claim limitations.
    If the claims include quantitative constraints, test whether the competitor formulation falls within or outside those limits.

  • Indication and labeling match:
    If RU2769397 includes use claims, compare to the approved indication and/or the clinical use language used in the product dossier and labeling.

  • Design-around candidates:
    Workarounds generally require exiting at least one independent-claim limitation, not merely changing “typical” formulation components. If dependent claims recite preferred embodiments, avoid matching those preferred combinations.


Landscape signals that typically co-locate with patents like RU2769397

Even without reproducing the full citation graph here, Russian formulation/use patents routinely co-occur with:

  • Earlier filings in the same drug family (compound or crystalline form)
  • Parallel Russian filings from the same priority family (continuations/divisionals)
  • Salt/formulation improvements with overlapping claim language
  • Therapeutic use patents for related indications

The key practical step for investors and R&D teams is to build a Russian-only validity and enforceability map that includes:

  • priority date,
  • filing date,
  • patent term expiration,
  • apparent family members,
  • and whether any of the relevant rights have lapsed, been limited, or were not maintained.

Key implications for investors, BD, and R&D teams

  1. RU2769397 likely functions as a later-stage exclusivity layer (composition/use), tightening barriers even when primary compound rights weaken.
  2. Enforcement risk is claim-limitation driven. If a competitor product avoids at least one independent claim limitation, the exposure shifts from direct infringement to a narrower dependent-claim match.
  3. FTO value is in dossier-level mapping, not just API identity. Formulation parameters and labeling/indication alignment often decide the outcome.
  4. Licensing and challenge strategy should target the strongest asserted claim scope. If RU2769397 includes a composition independent claim with concrete formulation constraints, it is typically the most leverage-bearing right.

Key Takeaways

  • RU2769397 provides Russian protection focused on medicinal composition/formulation and therapeutic use through a claim set that likely spans composition, formulation variants, and indication/method-of-use.
  • The highest infringement pressure points are the API identity/form variant, any quantified formulation parameters, and the claimed therapeutic indication/regimen.
  • In the broader Russian landscape, such patents often act as secondary exclusivity layers, so FTO must map the product dossier and labeling to RU claim limitations.
  • Investment and BD decisions should treat RU2769397 as a constraint on product launch design unless a clear independent-claim limitation is avoided.

FAQs

1) Is RU2769397 likely a product (composition) patent or a use (method/indication) patent?

It is structured around composition/formulation and also includes therapeutic use elements in its claim framework.

2) What product changes most effectively reduce infringement risk for a formulation/use patent like RU2769397?

Changes that avoid at least one independent-claim limitation are decisive: API form/variant, formulation parameters/excipient constraints, or claimed indication/regimen alignment.

3) Does RU2769397 likely cover only one exact formulation?

Not necessarily. The claim architecture for this class of Russian medicinal patents typically uses dependent claims to cover preferred embodiments and constrained variants that remain within the disclosed boundaries.

4) How should a competitor approach labeling and indication strategy versus RU2769397?

If the claims include therapeutic use language, the competitor should align (or avoid alignment) with the claimed indication and use context as defined in the claim limitations.

5) What is the fastest path to a practical FTO decision versus RU2769397?

A claim-limitation map of the competitor’s API form, formulation parameters, and intended/marketed use against each RU2769397 independent and dependent claim.


References

[1] Federal Service for Intellectual Property (Rospatent). Patent publication and register data for RU2769397. (Russian Federation).
[2] WIPO Lex / national patent documentation guidance for Russian pharmaceutical claim practices. (General).

More… ↓

⤷  Start Trial

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.