Scope and Claims Analysis for US Patent 9,034,822 (Dabigatran Antibody Reversal)
US Patent 9,034,822 claims a method of reversing dabigatran anticoagulant activity in a patient by administering a specific anti-dabigatran antibody defined by CDR sequences in heavy and light chain variable domains. The claim set is broad on antibody format (monoclonal, polyclonal, humanized, fragments, scFv/Fab/SMIP, diabody) but narrow on epitope identity via fixed CDR1/CDR2/CDR3 sequence identities and preferred complete variable domain embodiments (dependent claims). Core commercial and litigation relevance centers on whether a competitor’s reversal agent uses the same CDR-defined binding specificity (or a sufficiently close substitute) for dabigatran and/or its 1-O-acylglucuronide metabolite.
What does US Patent 9,034,822 claim for reversing dabigatran anticoagulation?
Answer: It claims an in vivo method for reversing the anticoagulant effect of dabigatran or dabigatran 1-O-acylglucuronide by administering a dabigatran-binding antibody whose heavy and light chain variable domains are specified by CDR sequence identities.
Claim 1: Independent method claim scope
Claim 1 is structured as a treatment method:
- Patient condition: “patient being treated with dabigatran… a prodrug of dabigatran or a pharmaceutically acceptable salt thereof”
- Reversal target: “reversing the anticoagulant effect of dabigatran or 1-O-acylglucuronide of dabigatran”
- Intervention: administering “an effective amount” of an antibody molecule with:
- Heavy chain variable domain defined by:
- CDR1: SEQ ID NO: 1
- CDR2: SEQ ID NO: 7
- CDR3: SEQ ID NO: 10
- Light chain variable domain defined by:
- CDR1: SEQ ID NO: 13
- CDR2: SEQ ID NO: 14
- CDR3: SEQ ID NO: 15
Infringement anchor: Even if a candidate antibody is not identical outside the CDRs, literal infringement is driven by whether the antibody has variable domains containing the exact CDR1/2/3 sequences at the specified positions. That makes the epitope binding “identity” claim-like via sequence-defined CDRs rather than functional binding alone.
Important claim construction points (practical):
- The claim is limited to antibody molecules that have the specified CDR identities. It is not limited to full-length IgG; dependent claims expand formats but independent claim 1 already requires the specified CDR-defined variable domains.
- The claim covers reversal of anticoagulation for patients taking dabigatran therapy, including dabigatran etexilate (prodrug).
- The claim expressly includes dabigatran 1-O-acylglucuronide, which can matter for reversal agents targeting circulating active metabolite and/or drug-protein binding dynamics.
Dependent claims: Added embodiments and format latitude
Claim 2 (preferred variable domains):
- Heavy chain variable domain: SEQ ID NO: 24
- Light chain variable domain: SEQ ID NO: 27
This is narrower than claim 1 because it requires a specific complete variable domain sequence pairing (not just CDR identities). If an accused antibody uses different frameworks but preserves the same CDRs, claim 1 remains the primary theory; if the full variable domains match, claim 2 provides an easier literal match.
Claim 3 (antibody class and fragment coverage):
The antibody molecule may be:
- polyclonal or monoclonal
- human, humanized, chimeric
- fragment of an antibody
- single chain antibody
- SMIP (Small Modular Immunopharmaceutical)
- diabody
This clause is designed to prevent “format escape” arguments where the antibody is engineered into non-IgG architectures.
Claim 4 (scFv + linker peptide):
- antibody is scFv
- heavy and light variable domains linked via linker selected from:
- SEQ ID NO: 28, 29, 30, 31
Claim 5 (Fab):
- Fab molecule with:
- Fd fragment comprising SEQ ID NO: 36
- light chain comprising SEQ ID NO: 37
Claims 6-7 (fragment and scFv restatements):
- Claim 6: Fab, Fab’, or F(ab’)2
- Claim 7: single chain antibody is scFv
Claim 8 (dose relationship):
- effective amount includes at least equimolar antibody to dabigatran or dabigatran 1-O-acylglucuronide
This is a dosing-scoping feature. If an accused product uses a lower molar ratio approach, it may avoid claim 8 but not necessarily claim 1 unless claim 8 is required for infringement (it is dependent, so only applies if claim 8 is asserted).
Claim 9 (route of administration):
- given intravenously as a bolus
Again dependent. Route specifics may be relevant for design-around and regulatory prescribing patterns.
How broad are the claims: CDR-defined specificity vs antibody-format breadth?
Answer: The patent blends narrow epitope definition (fixed CDR sequences) with broad antibody form (multiple antibody formats). This creates a landscape where design-arounds must change the binding specificity (CDR identity) rather than just switching delivery format.
Scope mechanics
- Narrow element: exact CDR sequence identities for heavy and light chains (independent claim 1).
- Broad element: any antibody type that includes those CDRs and variable domains, across multiple engineering formats (claims 3-7, plus claim 9 route/dosing dependent elements).
What the claims do not require
Based on the text provided:
- No explicit requirement for particular Fc engineering or effector function.
- No explicit requirement for human-only frameworks.
- No explicit requirement for manufacturing process or conjugation chemistry.
- No explicit requirement for a specific dosing regimen other than dependent equimolar and bolus limitations.
Design-around implications
A competitor seeking to avoid literal infringement would need to change at least one of the CDR sequences (or avoid the specific variable domain sequences in claim 2) while still providing functional reversal. Because claim 1 is framed as a method with a structurally defined antibody, competitors cannot generally avoid risk by changing only:
- IgG vs Fab vs scFv format
- route (unless claim 9 is asserted)
- dose ratio (unless claim 8 is asserted)
Which dabigatran targets are covered: dabigatran vs 1-O-acylglucuronide?
Answer: The method reverses anticoagulant effect of dabigatran or dabigatran 1-O-acylglucuronide.
Why the metabolite inclusion matters
Including the 1-O-acylglucuronide expands potential clinical relevance:
- It can broaden the antibody’s binding/reversal coverage to include active metabolite species or drug forms present in circulation.
- It can impact arguments about whether an accused antibody that binds only dabigatran (not the glucuronide) can still infringe the method claim. In practice, infringement theories would argue whether the claimed antibody effectively reverses anticoagulation with respect to either species named in claim 1.
What antibody molecules fall inside the claim under the provided CDR definitions?
Answer: Any antibody molecule whose variable domains include the specified CDR sequences for heavy and light chains, including full antibodies and multiple fragment/engineered constructs.
Covered antibody classes (dependent claim 3)
- Polyclonal antibody
- Monoclonal antibody
- Human / humanized / chimeric antibodies
- Antibody fragments
- Single chain antibodies including SMIP and diabody
Covered engineered formats (dependent claims 4-7)
- scFv with specified linker peptide options (SEQ ID NO: 28-31)
- Fab with specified Fd and light chain sequence embodiments (SEQ ID NO: 36-37)
- Fab’, Fab, F(ab’)2
- scFv restatement as single chain variable fragment
How do claims 8 and 9 affect infringement and generic entry risk?
Answer: They add narrower dependent limitations on dosing equivalency and administration route that can matter for claim construction strategy but do not generally eliminate infringement risk under claim 1.
Claim 8: equimolar antibody
- Requires at least equimolar antibody-to-dabigatran or antibody-to-dabigatran 1-O-acylglucuronide.
Practical effect:
- If a product’s labeled dosing uses lower molar antibody-to-anticoagulant ratios, it may be argued as not meeting dependent claim 8. But claim 1 can still be asserted without that dose relationship unless the patentee limits to claim 8.
Claim 9: IV bolus
- Requires intravenous bolus administration.
Practical effect:
- If administration is not a bolus (e.g., infusion), it may avoid dependent claim 9. Claim 1 remains the key risk anchor.
What does the patent landscape likely look like around US 9,034,822 (scope-centered, without external listings)?
Answer: Without the rest of the family’s publication numbers, continuations, and prosecution history, the landscape cannot be fully mapped. What can be stated from the claim architecture is the likely “adjacent protection” pattern: reversal-by-antibody IP typically clusters around (i) CDR-defined lead antibodies, (ii) variable domain/framework variants, (iii) fragment format and linker variants, and (iv) dosing and administration method claims.
High-probability adjacent claim zones (inferred from claim set structure)
- Variable domain embodiments beyond the core CDRs (like claim 2)
- Alternative linkers for scFv architectures (like claim 4)
- Specific fragment definitions (like claim 5)
- Dose ratio formulations (like claim 8)
- Route of administration claims (like claim 9)
This claim style signals that the patent holder is seeking to cover both:
- The antibody’s binding specificity (CDR identity)
- The therapeutic implementation (formats, route, dosing relation)
How strong is patent 9,034,822 for blocking an alternative dabigatran reversal antibody?
Answer: Strength is tied primarily to whether an alternative antibody uses the same CDR sequences. The breadth of antibody format reduces escape pathways; the narrowness of CDR identity makes the key question binding-specificity equivalence.
Literal infringement is sequence-driven
- If an accused antibody’s heavy/light variable domains have the exact CDR sequences (SEQ IDs listed), it is within the independent claim scaffold.
The “equivalents” lane depends on prosecution history and claim construction
Because the claims are already sequence-defined, equivalence arguments typically become fact-intensive and hinge on whether substitution in CDRs still achieves substantially the same binding to dabigatran and/or 1-O-acylglucuronide.
Practical enforcement target
For licensing or litigation, the patent is positioned to assert against:
- dabigatran reversal antibodies marketed or in development where CDR identity matches the claimed SEQ IDs
- biosimilar-like antibody engineering variants that preserve CDRs but change format (IgG vs fragment)
Key takeaways
- US 9,034,822 claims a CDR-sequence-defined antibody method for reversing dabigatran and dabigatran 1-O-acylglucuronide anticoagulant effect in patients receiving dabigatran therapy.
- Claim 1 is the main risk anchor: it requires exact heavy and light chain CDR1/CDR2/CDR3 sequence identities (SEQ ID NOs 1, 7, 10 for heavy; 13, 14, 15 for light).
- Dependent claims broaden the antibody formats (IgG, fragments, scFv, Fab, SMIP, diabody) but narrow via specific variable domain embodiments (claim 2) and specific dosing/route constraints (claims 8-9).
- Design-around is most plausible by changing antibody binding specificity (CDRs) rather than changing delivery format, route, or fragment architecture alone.
FAQs
1) Can an IV infusion version avoid claim 9?
If claim 9 is asserted, only IV bolus meets the dependent limitation; claim 1 could still be asserted if the antibody CDRs match.
2) Does the patent cover reversal when dabigatran etexilate is used?
Yes. Claim 1 explicitly includes dabigatran etexilate and other dabigatran prodrugs.
3) Is binding to only dabigatran (not 1-O-acylglucuronide) outside the claim?
Claim 1 includes reversing anticoagulant effect of dabigatran or its 1-O-acylglucuronide; avoidance would depend on whether infringement turns on functional reversal for both species versus either species named in the method.
4) Would switching from a monoclonal antibody to a fragment like Fab avoid infringement?
No, if the antibody fragment still has the claimed heavy/light CDR sequence identities required by claim 1. Dependent claims expressly cover Fab and related formats.
5) What is the central variable for licensing talks around this patent?
Whether candidate reversal antibodies use the exact claimed CDR sequences (and, for the preferred embodiment, the specific variable domain sequences of claim 2).
