Angiomax Patents Limited To Example

by Foley & Lardner LLP
Contact

In The Medicines Co. v. Mylan, Inc., the Federal Circuit construed composition claims of two Angiomax patents as requiring the recited “batches” to be made by a specific “efficient mixing” process illustrated in one of the examples. While doing so may have preserved the validity of the patents, it required reversal of the district court’s infringement ruling.

The Angiomax Patents At Issue

The patents at issue were U.S. Patent No. 7,582,727 and U.S. Patent No. 7,598,343, which are Orange Book-listed patents for Angiomax® (bivalirudin), which is “used to prevent blood clotting in patients undergoing cardiac catheterization.” These are the same patents almost lost to the on-sale bar, as previously discussed. Claim 1 of the ‘727 patent recites:

1. Pharmaceutical batches of a drug product comprising bivalirudin (SEQ ID NO: 1) and a pharmaceutically acceptable carrier for use as an anticoagulant in a subject in need thereof, wherein the batches have a pH adjusted by a base, said pH is about 5-6 when reconstituted in an aqueous solution for injection, and wherein the batches have a maximum impurity level of Asp(^9)-bivalirudin that does not exceed about 0.6% as measured by HPLC.

None of the claims of the ‘727 patent use product-by-process language or recite method steps. Claim 1 of the ‘343 patent recites (with emphasis added):

1. Pharmaceutical batches of a drug product comprising bivalirudin (SEQ ID NO: 1) and a pharmaceutically acceptable carrier, for use as an anticoagulant in a subject in need thereof, said batches prepared by a compounding process comprising: (i) dissolving bivalirudin in a solvent to form a first solution; (ii) efficiently mixing a pH-adjusting solution with the first solution to form a second solution, wherein the pH-adjusting solution comprises a pH-adjusting solution solvent; and (iii) removing the solvent and pH-adjusting solution solvent from the second solution; wherein the batches have a pH adjusted by a base, said pH is about 5-6 when reconstituted in an aqueous solution for injection, and wherein the batches have a maximum impurity level of Asp(^9)-bivalirudin that does not exceed about 0.6% as measured by HPLC.

(Asp(^9)-bivalirudin is an impurity having aspartic acid instead of asparagine as its 9th amino acid residue.)

According to the Federal Circuit decision, the FDA required The Medicines Company to limit the level of asp(^9)-bivalirudin to less than 1.5 percent. Prior to the invention at issue, The Medicines Company made and sold individual batches of bivalirudin with Asp(^9)-bivalirudin levels below 0.6%, although there was batch-to-batch variability that required The Medicines Company to reject batches that did not satisfy this purity requirement. Thus, the court characterized the invention at issue as addressing the problem of batch variability.

The Federal Circuit Decision

The Federal Circuit decision was authored by Judge Dyk and joined by Judges Wallach and Hughes. The decision focuses on claim construction, and interprets the recited term “batches” as requiring the “efficient mixing” discussed in the specification, as performed in Example 5 of the patents.

Claim Construction: “Batches” = “Compounding Process”

The court focused on the recitation of “batches [that] have a maximum impurity level of Asp(^9)-bivalirudin that does not exceed about 0.6%.” The court noted that the patents define “batches” as follows:

As used here, “batch” or “pharmaceutical batch” refers to material produced by a single execution of a compounding process of various embodiments of the present invention. “Batches” or “pharmaceutical batches” as defined herein may include a single batch, wherein the single batch is representative of all commercial batches (see generally, Manual of Policies and Procedures, Center for Drug Evaluation and Research, MAPP 5225.1, Guidance on the Packaging of Test Batches at 1), and wherein the levels of, for example, Asp(^9)- bivalirudin, total impurities, and largest unknown impurity, and the reconstitution time represent levels for all potential batches made by said process. “Batches” may also include all batches prepared by a same compounding process.” ’727 patent, col. 5 ll. 24–36; ’343 patent, col. 5

The district court adopted this definition with the further clarification that the “batches” must be made “by a particular compounding process.” According to the Federal Circuit decision, The Medicines Company argued that the “batches” limitation “is satisfied whenever an accused infringer consistently produces batches having Asp(^9) levels below 0.6 percent, and that the claims do not require the use of a particular process that achieves batch consistency.” The court gave the following reasons for rejecting such a claim construction:

  • “adopting Medicines’ interpretation of the batches limitation would yield an unworkable claim construction” requiring “forward-looking assessments of whether an accused infringer’s production of future … batches would be likely to generate Asp(^9) levels greater than ‘about 0.6%.'”
  • “the specification and prosecution history of the patents in suit … demonstrate that the invention disclosed by the ’727 and ’343 patents is a compounding process that achieves batch consistency.”
  • “Medicines’ admission to the district court that ‘[w]hen viewed in the context of the specification, it is readily apparent that the [definition of “pharmaceutical batches”] refers to the compounding processes described in the patents-in-suit.'”

Thus, the Federal Circuit concluded:

[W]e … conclude that the batches limitation requires the use of a compounding process that achieves batch consistency. In doing so, we note that our decision does not impermissibly add a process limitation to a product claim that does not require a process because the specification’s definition of “batches” by itself injects a compounding process as a limitation in the asserted claims.

Claim Construction: “Compounding Process” = “Efficient Mixing”

The decision also explains why the “compounding process” required by the claims “must use ‘efficient mixing'”:

  • “[A]part from efficient mixing, no part of the patents’ disclosure teaches another method capable of producing consistent batches.”
  • The patents state that “‘the [efficient mixing] process demonstrated in Example 5 produced batches generally and consistently having lower levels of impurities than the [inefficient mixing] process of Example 4.'”
  • The patents state that “consistent ‘batch(es) may be prepared by a compounding process comprising dissolving bivalirudin in a solvent to form a bivalirudin solution, efficiently mixing a pH-adjusting solution with the bivalirudin solution to form a compounding solution, and removing solvents from the compounding solution. This compounding process includes all of the embodiments as described.'”
  • Statements in the Petitions to Make Special filed in each application “stated that ‘various embodiments’ of the ‘present invention . . . relate to a process [that] involves efficiently mixing the pH-adjusting solution and the dissolved bivalirudin solution, which is not performed in the Applicants’ prior compounding process.'”

Thus, the court read the patents as teaching “efficient mixing as a necessary and sufficient condition for achieving batch consistency.”

Claim Construction: “Efficient Mixing” = Example 5

With regard to what “efficient mixing” means, the court gave two reasons for rejecting The Medicines Company’s reliance on the following statement in the specification:

Efficient mixing of the pH-adjusting solution with the bivalirudin solution will minimize levels of Asp.sup.9-bivalirudin in the compounding solution.

First, the court noted that it did not follow the “linguistic formula” used in the rest of the specification “to signal … defined terms,” i.e., “the defined term in quotation marks, followed by the terms ‘refers to’ or ‘as defined herein.'” Second, the court found the sentence to provide “a mere recitation of the results obtained from ‘efficient mixing’ rather than a definition of what the efficient mixing process is.” Turning to the remainder of the specification, the court acknowledged teachings that “‘[e]fficient mixing . . . may be achieved through various methods,'” but found them to be “vague and unhelpful”—a “laundry list of mixing techniques that individually (or in combination) may (or may not) constitute efficient mixing.” Instead, the court focused on Examples 4 and 5, which it characterized as “clearly stat[ing] what efficient mixing is and is not.” Although the district court had construed “efficient mixing” as excluding the inefficient mixing of Example 4, the Federal Circuit determined that “efficient mixing” is defined by the mixing of Example 5:

Example 5 … is not merely the only disclosed embodiment of efficient mixing—it is the only description of efficient mixing in the patents in suit that casts light on what efficient mixing is and that enables one of ordinary skill in the art to achieve the objects of the claimed invention.

Thus, the court “construe[d] the ‘efficient mixing’ required by the patents … to require using the efficient mixing conditions of Example 5.” Since Mylan did not use that methodology, the court determined that “Mylan’s ANDA cannot infringe the asserted claims of the ’727 patent and the ’343 patent.”

Should The Product Claims Be Limited To The Exemplified Method?

Reading this decision I was struck by the contrast with the Federal Circuit’s 2013 decision in AstraZeneca LP v. Breath Limited, where the court refused to limit the recited “micronized powder composition” having a purity level of “at least 98.5%” to products sterilized by the specific method described in the specification. There, the court cited earlier decisions for the principle that a specific “method of manufacture, even when cited as advantageous, does not of itself convert product claims into claims limited to a particular process. . . . A novel product that meets the criteria of patentability is not limited to the process by which it was made.” Although the AstraZeneca decision was non-precedential, the cases it relied upon were not.

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Foley & Lardner LLP | Attorney Advertising

Written by:

Foley & Lardner LLP
Contact
more
less

Foley & Lardner LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Privacy Policy (Updated: October 8, 2015):
hide

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.

Security

JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at info@jdsupra.com. In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at: info@jdsupra.com.

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.