Share This Page
Details for Patent: 9,248,199
✉ Email this page to a colleague
Which drugs does patent 9,248,199 protect, and when does it expire?
Patent 9,248,199 protects OXBRYTA and is included in two NDAs.
Summary for Patent: 9,248,199
| Title: | 1:1 adducts of sickle hemoglobin | ||||||||||||
| Abstract: | Provide herein are 1:1 adducts of sickle hemoglobin (HbS) and a compound of formula (I), as defined herein, suitable as modulators of HbS, and methods for their use in treating disorders mediated by hemoglobin and disorders that would benefit from tissue and/or cellular oxygenation. | ||||||||||||
| Inventor(s): | Brian W. Metcalf | ||||||||||||
| Assignee: | Global Blood Therapeutics Inc | ||||||||||||
| Application Number: | US14/167,632 | ||||||||||||
|
Patent Claim Types: see list of patent claims | Use; Composition; | ||||||||||||
| Patent landscape, scope, and claims: | US Patent 9,248,199: Scope, Claims, and Patent Landscape for HbS Oxygen-Affinity/Occlusion Therapy Using a Benzaldehyde Pyrazolylpyridine EtherUnited States Patent 9,248,199 covers a method of increasing the oxygen affinity of sickle hemoglobin (HbS) and inhibiting HbS sickling in vivo via administration of a single named small molecule (or a salt) described as: 2-(((2-(1-isopropyl-1H-pyrazol-5-yl)pyridin-3-yl)oxy)methyl)-6-hydroxybenzaldehyde, including its salts. The operative scope is defined by formation of a 1:1 HbS adduct in vivo, where the adduct increases oxygen affinity and inhibits sickling. What is the invention’s functional “center of gravity”?The claim language makes HbS binding and adduct stoichiometry in vivo the pivot:
This makes the enforceable boundary less about a broad “oxygen affinity increase” concept and more about doing it with this specific benzaldehyde ether scaffold under conditions that produce the 1:1 HbS adduct. How broad is the claim scope by compound definition?Core active ingredientBoth claims are limited to administration of:
There is no claim text that expands to:
Structural lock-in risk for design-aroundBecause the active is recited in full chemical name form (not as a Markush group), the claim’s “chemical scope” is tightly anchored. A competitor that substitutes any part of the core structure (pyrazole substitution, pyridine substitution pattern, ether linkage, benzaldehyde hydroxy position, or aldehyde itself) risks falling outside the literal wording unless it still uses the same compound/salt. What does “a sufficient amount” cover, and how does that affect enforceability?“A sufficient amount” is a dose-intent trigger, not a specific mg/kg number. In practice, this:
Still, because the claims do not quantify dose, there is no explicit numeric ceiling or floor that can be used to carve out non-infringing dosing. How broad is the patient population?Both claims cover:
That language is broad. It does not limit to adults, pediatrics, transfusion-dependent patients, or particular clinical phenotypes. Is “in vivo 1:1 adduct” a hard boundary or a scientific description?It is both a mechanistic requirement and a constraint on infringement theory. The claims require that administration be such that the compound:
This does two things:
From a competitor perspective, design-around options that change stoichiometry (for example, compounds binding HbS at different stoichiometries or forming mixtures of species) could be argued as outside “1:1 adduct” even if oxygen affinity changes. What is the scope distinction between Claim 1 and Claim 2?Claim 1 (oxygen affinity)
Claim 2 (anti-sickling)
Both depend on the same adduct formation requirement. The difference is the endpoint. That matters because a compound could, in theory, form the same adduct but show different physiologic effects across assay conditions (Claim 1) or clinical endpoints (Claim 2). The claims still require the relevant functional outcome under “in vivo” conditions. What exactly are the independent claim elements?Claim 1 element-by-element
Claim 2 element-by-element
How does claim wording affect “product” versus “method” infringement?These are method-of-treatment claims. They capture acts of administration, not just possession or manufacturing of the compound. A generic or formulation company that sells the compound for research use would not automatically infringe. A company promoting or delivering it into patients “in need thereof” could be accused of direct infringement if the other elements are met, particularly in vivo 1:1 adduct formation and the functional endpoint. How does this patent fit into the broader HbS oxygen-modifier landscape?The claims track a common mechanistic theme in sickle cell pharmacology: small molecules that shift HbS oxygen affinity or otherwise stabilize non-sickling hemoglobin states. However, this patent’s enforceable hook is specific compound identity plus a 1:1 HbS adduct. What are the most relevant competitor claim categories around this patent?1) Direct analogs that match the exact compound identity
2) Structural analogs that retain the “1:1 adduct” behavior
3) Compounds that change oxygen affinity without forming a 1:1 HbS adduct
4) Compounds that inhibit sickling via different mechanisms
Which existing drug classes most likely overlap on the mechanism axis?Even without mapping every related patent family in this dataset, the functional outcomes align to at least two broad therapeutic buckets:
US 9,248,199 is best categorized with oxygen affinity modifiers, but it is narrower because it specifies a particular chemical structure and demands 1:1 HbS adduct formation. What does “patent landscape” mean here, operationally?For investment and R&D planning, the landscape question breaks into three enforceability vectors:
Patent-scope implications for pipeline and licensingLikely strongest enforcement theory
Likely design-around pressure points
Claim-by-claim risk map for R&D and FTO (based on the provided claim text)Claim 1 risk drivers
Claim 2 risk drivers
Scenario mapping (how a court may read the claims)
This map assumes the claim is construed as written, with literal limitation to the specified compound/salt. What is missing for a full US “patent landscape” map?A complete patent landscape requires the patent family members, priority chain, related continuations, prosecution history, and citing/cited documents in the US system. Those data are not present in the record provided. The analysis above therefore limits itself to scope and enforceability logic embedded in the claim text. (Per instruction constraints, no additional data requests or speculation are included.) Key Takeaways
FAQs1) Do the claims cover manufacturing the compound, or only administering it? 2) Is the “1:1 adduct in vivo” requirement common to both claims? 3) Can a competitor avoid liability by dosing differently? 4) Does Claim 2 also require increased oxygen affinity? 5) What is the most direct design-around based on the claim text? References
More… ↓ |
Drugs Protected by US Patent 9,248,199
| Applicant | Tradename | Generic Name | Dosage | NDA | Approval Date | TE | Type | RLD | RS | Patent No. | Patent Expiration | Product | Substance | Delist Req. | Patented / Exclusive Use | Submissiondate |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Global Blood Theraps | OXBRYTA | voxelotor | TABLET, FOR SUSPENSION;ORAL | 216157-001 | Dec 17, 2021 | DISCN | Yes | No | ⤷ Start Trial | ⤷ Start Trial | TREATMENT OF SICKLE CELL DISEASE BY ADMINISTERING VOXELOTOR, AS RECITED IN CLAIM 1 | ⤷ Start Trial | ||||
| Global Blood Theraps | OXBRYTA | voxelotor | TABLET, FOR SUSPENSION;ORAL | 216157-001 | Dec 17, 2021 | DISCN | Yes | No | ⤷ Start Trial | ⤷ Start Trial | TREATMENT OF SICKLE CELL DISEASE BY ADMINISTERING VOXELOTOR, AS RECITED IN CLAIM 2 | ⤷ Start Trial | ||||
| Global Blood Theraps | OXBRYTA | voxelotor | TABLET;ORAL | 213137-002 | Oct 14, 2022 | DISCN | Yes | No | ⤷ Start Trial | ⤷ Start Trial | TREATMENT OF SICKLE CELL DISEASE BY ADMINISTERING VOXELOTOR, AS RECITED IN CLAIM 1 | ⤷ 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 |
