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.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). 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 & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd 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 or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.