United States: Angiomax Patents Limited To Example

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 discussed in this article and this article. 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.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Similar Articles
Relevancy Powered by MondaqAI
In association with
Related Topics
Similar Articles
Relevancy Powered by MondaqAI
Related Articles
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Mondaq Free Registration
Gain access to Mondaq global archive of over 375,000 articles covering 200 countries with a personalised News Alert and automatic login on this device.
Mondaq News Alert (some suggested topics and region)
Select Topics
Registration (please scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.


The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.


Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions