United States: Another Slam Dunk Infuse Win – Preemption And More

Last Updated: September 29 2016
Article by Michelle Yeary

If you're even remotely interested in the topic of preemption in Pre-Market Approved (PMA) medical devices that were used in an off-label manner, simply search this blog for our Infuse cases. There are dozens and almost all are complete victories for the defense. What occasionally survives are fraud or misrepresentation claims, although they have a tough time meeting the heightened pleading standard of Rule 9(b), or failure to warn claims where a court recognizes failure to submit adverse events to the FDA as parallel to a state law duty to warn physicians. As you'll easily see from our prior writings, we don't understand that parallelism at all.

The most recent Infuse victory strikes a blow at each and every attempt by plaintiffs to circumvent, dodge, sidestep, and elude preemption and pleadings standards. And with each by-pass blocked, plaintiffs' claims had nowhere to go.

As a quick refresher, Infuse is a medical device used to stimulate bone growth in spinal fusion surgeries. It is a multi-component device that received FDA PMA approval for use in single-level, anterior, lumbar surgeries. Aaron v. Medtronic, Inc., — F. Supp.3d –, 2016 WL 5242957, *1-2 (W.D. Ohio Sep. 22, 2016). Aaron is actually a consolidation of the claims of several hundred plaintiffs who alleged they were injured by their surgeon's use of the Infuse device in an off-label manner. Specifically, they allege the device was either implanted without all of its component parts, implanted posteriorly, implanted at multiple levels, or implanted in their cervical or thoracic spines. Id. at *2. Plaintiffs' causes of action are fraud/misrepresentation, strict liability failure to warn, strict liability design defect, negligence, and breach of express and implied warranties. Id. Defendants moved to dismiss all claims on several grounds, including most predominantly preemption.

Before getting to the substantive analysis, the court had to consider what pleadings standard to apply. Wait. Isn't it TwIqbal? What's the issue? The answer is the Seventh Circuit decision in Bausch v. Stryker. The Aaron plaintiffs alleged that they did not need to plead the specific federal law or regulations that defendant allegedly violated because medical device products liability cases should have a "more permissive" review standard. Id. at *3. Plaintiffs got that idea from Bausch which held that particularity in pleading the specific FDA regulations violated was not necessary due to much of the "critical information" being kept confidential. Id. at *3-4. Many courts disagree with Bausch, including the Sixth Circuit which held in a non-medical device case that a "natural imbalance of information" does not warrant lowering Rule 8's pleading standards. Id. at *4. The discovery process cannot be used to find sufficient factual support for plaintiffs' pleadings after the fact. So, Aaron applies TwIqbal, not some watered down version (although the court does state that some of plaintiffs' claims might not have withstood application of that lesser standard).

The next question the court had to answer is whether any of plaintiffs' allegations about off-label use changed the Riegel test for PMA preemption – a two-step analysis that requires the court to determine first whether the FDA has established any specific requirements for the device (satisfied in PMA devices) and if so, whether plaintiffs' state law claim impose requirements that are different from or in addition to the federal requirements. Plaintiffs' argument is that because the device was used off-label the FDA has not established any PMA requirements for Infuse as it was used on plaintiffs. Incorrect said the court. "Premarket approval extends to all components of an approved device, even when a physician uses the components separately." Id. at *6. This is confirmed by the FDCA's definition of "device" to include "any component" of the device. Id. at *7. So, off-label allegations don't change the first part of the Riegel test – PMA devices are subject to specific federal requirements.

Moving to step two of Riegel, the court had to determine whether any of plaintiffs' state law claims were parallel claims. Traditional failure to warn is always easy – it's expressly preempted because the defendant cannot provide any warning other than that approved by the FDA. Id. But, plaintiffs have tried to morph their failure to warn claims into claims for failure to submit adverse event reports to the FDA. A claim unfortunately recognized by the Ninth and Fifth Circuits. We've never understood how an FDCA requirement that a device manufacturer submit adverse event reports to the FDA was the same as a state law duty to warn physicians and the Aaron court likewise did not see the connection. There is no Ohio state law duty to report adverse events to the FDA and the federal duty to do so "is not identical and thus not parallel, to the state-law duty to provide warnings to patients or their physicians." Id. at *8.   That seems readily apparent to us, but the court goes further in breaking it down. It starts with a simple concept that the Ninth and Fifth Circuits have overlooked: "Adverse-event reports are not warnings." Id. They are regulatory submissions. Adverse event reports are anecdotal accounts of incidents. More importantly, they are not "valid scientific evidence" upon which the FDA may base a labeling change. Id. In other words, if the theory accepted by courts who have recognized this cause of action is that by submitting adverse event reports to the FDA, the manufacturer is "warning" the FDA who will then in turn require manufacturers to warn doctors – that theory is just wrong. There is no federal requirement that manufacturers submit adverse event reports to physicians or the public. There is no state-law requirement that medical device manufacturers submit adverse event reports to the FDA. The requirements are not "genuinely equivalent." Id. There is no parallel claim.

Even if not persuaded on express preemption, a failure to submit adverse event reports to the FDA fits squarely within Buckman implied preemption. As noted above, there is no state law for failure to submit reports to the FDA. The duty to submit doesn't exist absent the FDCA, so plaintiffs' claim is "an impermissible attempt to enforce exclusively federal requirements with no counterpart in state law." Id. at *12.

Design defect seems like an easy preemption question in a PMA case as well. The FDA has approved a specific design. Any design defect claim asks a jury to find that the device should have been designed in a manner different than that approved by the FDA. Express preemption. Once again plaintiffs tried a little sidestep maneuver. In their response to the motion to dismiss, they cite to some FDA manufacturing regulations and argue that their design defect claim should survive based on allegations not asserted in the complaint that defendant failed to adhere to FDA manufacturing standards. Id. at *10. But the complaint didn't allege a manufacturing defect claim, only design defect. As to the latter,

allowing a design defect claim to proceed would be tantamount to holding that a medical device design that has been approved by the FDA can nonetheless by legally deficient – an encroachment on federal regulatory authority that 21 U.S.C. §360(k) was specifically designed to prevent.


The next expressly preempted claim was breach of express warranty.   Because plaintiffs alleged breach of warranty as to effectiveness and safety, a jury would have to find the device not safe and effective – which would directly conflict with the FDA's PMA conclusion that the device was safe and effective. Id.

The last preempted claim was for "off-label promotion." Another concept for which no state-law duty exists. The "very concept" of off-label promotion doesn't exist outside the MDA and its requirement that the FDA approve medical devices and their labels. Id. at *12. There is nothing in Ohio state law that prohibits manufacturers from promoting their devices for off-label uses. Any allegation that off-label promotion is unlawful is actually a claim for violating the FDCA. Therefore, it is impliedly preempted as an attempt to privately enforce the FDCA, something that has been left exclusively to the FDA.   Id. at *13.

Although all plaintiffs' product liability claims were dismissed as preempted, the court still reviewed other state law arguments for dismissal, including one based on comment k of the Restatement. Comment k provides an exemption from strict liability for unavoidably unsafe products, such as prescription drugs and medical devices. Plaintiffs argued that whether any particular medical device is unavoidably unsafe is a case-by-case determination that could not be made at the pleadings stage. The court thought defendant had the better argument: "Infuse's classification by the FDA as a Class III medical device inherently means that it is unavoidably unsafe." Id. at *15. The court was satisfied that Infuse was an unavoidably unsafe product based on the FDA's determination that it needed to be a restricted device due to its "potential for harmful effect," and that Class II regulatory controls weren't sufficient to ensure safety and effectiveness. Id.

The court was also unpersuaded by plaintiffs' arguments that it was too early in the proceedings to determine whether there was a less risky alternative design because "there is no alternative design for Infuse that could lawfully be marketed." Id. Manufacturers are prohibited from changing the design of a PMA device without FDA permission. No need to belabor the issue in discovery.

That brings us to plaintiffs' fraud claims which are subject to the heightened pleadings requirements of Rule 9. The court focused on one of the ways in which plaintiffs' fraud allegations failed to meet that standard. Plaintiffs alleged both that their surgeon, acting as defendant's agent, knew about the risks of using the Infuse device in an off-label manner and concealed those risks from plaintiffs, and that defendant did not adequately inform plaintiff's surgeon of the risks and that he was justified in relying on defendant's concealments and misrepresentations. Id. at *17. While you can plead alternative causes of action, you can't plead inconsistent versions of the facts in support of a single claim. Id. Plaintiffs can't have it both ways. Either the surgeon had or did not have knowledge of the risks. The contradictory allegations defeated plaintiffs' fraud-based claims.

With that several hundred Infuse claims were dismissed in their entirety. Another great victory for Medtronic and a really strong opinion rejecting some of our least favorite decisions. Win-win.

This article is presented for informational purposes only and is not intended to constitute legal advice.

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.

In association with
Related Video
Up-coming Events Search
Font Size:
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
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
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.


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.


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.


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.


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.


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.


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.