United States: Another Make Work Project In New Jersey – Duty To Update Claims

Last Updated: September 13 2016
Article by James Beck

The United States Supreme Court has said it – the test for implied preemption under 21 U.S.C. §337(a) (the FDCA's no-private-enforcement provision) is whether the purported state-law cause of action would exist even in the absence of the FDCA/FDA: Buckman Co. v. Plaintiffs Legal Committee, 531 U.S. 341, 353 (2001) (preemption applies to "claims exist solely by virtue of the FDCA disclosure requirements" and to all claims where "existence of these federal enactments is a critical element"). So have federal courts of appeals.

If the claim would not exist in the absence of the FDCA, it is impliedly preempted. In other words the conduct on which the claim is premised must be the type of conduct that would traditionally give rise to liability under state law − and that would give rise to liability under state law even if the FDCA had never been enacted.

Loreto v. Procter & Gamble Co., 515 F. Appx. 576, 579 (6th Cir. 2013) (citations and quotation marks omitted). Accord Caplinger v. Medtronic, Inc., 784 F.3d 1335, 1339 (10th Cir. 2015) ("§337(a) preempts any state tort claim that exists 'solely by virtue' of an FDCA violation"); Perez v. Nidek Co., 711 F.3d 1109, 1119 (9th Cir. 2013) (preempting a "fraud by omission claim [that] exists solely by virtue of the FDCA requirements") (citation and quotation marks omitted); Lofton v. McNeil Consumer & Specialty Pharmaceuticals, 672 F.3d 372, 379 (5th Cir. 2012) (following Buckman; "tort claims are impermissible if they existing solely by virtue of the FDCA disclosure requirements").

Nonetheless, courts persist, in generic drug product liability litigation, to ignore the relevant preemption test when it comes to "duty to update" claims. In such cases, if there were no FDCA, and thus no FDA, then the FDA couldn't be telling anybody to update anything to conform to anything else. The latest example of this logic-defying trend is the New Jersey Supreme Court's recent decision in In re Reglan Litigation, ___ A.3d ___, 2016 WL 4420637 (N.J. Aug. 22, 2016) (we'll call it "NJ Reglan" since there are various other Reglan-named decisions out there).

Yes, it is an arguable violation of the FDCA's (Hatch-Waxman) "sameness" requirement for a generic manufacturer not to update its label to match changes approved by the FDA to the "reference" drug (usually but not always the innovator) labeling, although there were apparently no deadlines for doing so at the time of the first disputed label update. Id. at *14 (citing 2000 FDA guidance document – having no legal effect – recommending that generic manufacturers should "routinely monitor" the FDA's website for label updates and include them "at the very earliest time possible").

But forget Buckman for a moment. What kind of vague, squishy standard is that?

It's certainly not one that state law has any business adopting. First of all, state negligence per se law has never replaced the general tort standard of care with anything, such as an FDA guidance, that lacks force of law. E.g., Restatement (Third), Products Liability §4 (1998); Restatement (Second) of Torts §§285-288C (1965) (both limited to statutes, regulations, ordinances, etc that were legally enforceable). We discussed this state-law based limitation on negligence per se in detail here, and Bexis' book (see §4.02[3][b]) cites a raft of precedent for this proposition. We don't know of any state that imposes liability for the violation of something – such as FDA guidance documents – that even the entity that wrote it couldn't legally enforce. As stated in footnote 1 of the 2000 guidance document:

This guidance document represents the Agency's current thinking on changes in labeling of approved abbreviated new drug applications (ANDAs) following revisions in the RLD's labeling. It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.

U.S. Dep't of HHS, FDA, "Guidance for Industry: Revising ANDA Labeling Following Revision of the RLD Labeling, at 4, n.1 (May 2000) (emphasis added).

That's not all. In a development not even mentioned in NJ Reglan opinion, Congress ditched the FDA's loosey-goosey "go look for it and do it as fast as you can" updating standard right in the middle of the time period at issue in this litigation. NJ Reglan involved "nearly 1000 individual lawsuits against over fifty brand-name and generic manufacturers." 2016 WL 4420637, at *2. The claimed failures to update generic labeling ranged between six months and 4˝ years. Id. at *3. Allegedly these failures to update began in 2004 and (as to some defendants) lasted until 2009. Id. at *15.

But in 2007, Congress amended the FDCA and enacted 21 U.S.C. §355(o)(4), concerning "labeling changes requested by [FDA]." This provision imposed an actual notice requirement on the FDA. "If [FDA] becomes aware of new safety information that [it] believes should be included in the labeling of the drug, [FDA] shall promptly notify the responsible person." Id. §355(o)(4)(A). After receiving such notice, the "responsible person" must then file a supplement updating the labeling "within 30 days." Id. §355(o)(4)(B)(1).

So as of 2007, that's what the FDCA actually required for this type of agency-driven label update – no more "watch our website" advice with no force of law.

Thus, not only did the pre-2007 FDA guidance document lack force of law, but Congress then rejected the procedure that the FDA had described in the 2000 guidance. In what was actually legally enforceable (after 2007), Congress required actual notice to the responsible person before the 30-day obligation to update labeling could begin. Thus, the situation in NJ Reglan was unlike any negligence per se-style substitution of regulatory standards for a state-law standard of care that we've ever seen. The pre-2007 guidance-document standard not only had no force of law, but was found wanting and affirmatively repudiated by Congress when it chose to impose a legally enforceable label updating standard.

Desperate to avoid generic preemption after PLIVA, Inc. v. Mensing, 564 U.S. 604 (2011), and Mutual Pharmaceutical Co. v. Bartlett, 133 S. Ct. 2466 (2013), the plaintiffs in NJ Reglan alleged that various generic makers of metoclopramide didn't update their labels after the FDA approved changes to the "reference" (innovator or branded) label for Reglan in 2005 and again in 2009. NJ Reglan, 2016 WL 4420637, at *2. These changes strengthened warnings against long-term use of the drug (whether innovator or generic). Id.

As discussed, prior to the 2007 enactment of §355(o)(4), the FDA was not in the habit of giving actual "notice" of labeling changes affecting generic drugs. The NJ Reglan opinion relates:

Generic manufacturers have been given the means to learn of brand-name-labeling updates. The Office of Generic Drugs in the Office of Pharmaceutical Science, Center for Drug Evaluation and Research, at the FDA has directed generic manufacturers to "routinely monitor the Labeling Review Branch Homepage ... for information on changes in labeling." The Office of Generic Drugs "[p]lace[s] monthly updates of approved labeling changes" for brand-name drugs with approved generic counterparts "on the Labeling Review Branch Homepage." Ibid. "All approved labeling for [brand-name drugs] is [also] available from Freedom of Information Staff" at the FDA.

NJ Reglan, 2016 WL 4420637, at *8 (citation to FDA guidance document and footnote omitted) (emphasis added). Thus, instead the affirmative notice required by Congress in 2007, the FDA was apparently putting label "updates" on its homepage and expecting (via "guidance" without force of law) generics to come looking for them. Mere "means to learn" isn't "notice" to anybody.

Without discussing either a federal- or state-law basis for doing so, the unanimous New Jersey Supreme Court readily found a "violation" (of exactly what, we're not sure) on which to hang what it treated as a "common-law" claim (again, of what sort, we're not sure – the opinion never mentions negligence per se). The opinion took the presumption against preemption from Wyeth v. Levine, 555 U.S. 555 (2009) (now dead in express preemption cases) (2016 WL 4420637, at *9-10), stirred in the "New Jersey's strong public policy of ensuring that manufacturers attach adequate warnings and instructions to prescription drugs" (derived from a statute originally enacted to restrict liability) (id. at *10), and baked until a violation popped up:

Here, defendant generic manufacturers of metoclopramide tablets did not conform their labeling to that of the brand-name drug and therefore were in violation of the FDCA's sameness requirement. . . . No law prevented defendants from giving the same warnings that appeared on the labeling of the brand-name drug − the warnings that plaintiffs contend the [N.J. product liability statute] required. Defendants did not have to violate federal law to comply with state law.

Id. at 11.

Ironically, NJ Reglan declared that "[t]his case drives home the point made in [Levine] that the FDA does not have the resources to monitor the labeling of thousands of drugs after they are marketed," id., when the asserted "violation" involved various generic manufacturers allegedly not ferreting out label changes under an informal FDA procedure rejected by Congress in favor of requiring affirmative FDA notice. Nothing in NJ Reglan indicates that, either before or after 2007, the FDA ever gave such affirmative notice of label changes to any of the defendants, as §355(o)(4) contemplates. The FDA itself couldn't enforce that guidance, so how can state law do so?

NJ Reglan finished off preemption by rejecting the applicability of the Buckman principle discussed at the outset of this post. "The present case is different from Buckman because, here, the 'critical element' to plaintiffs' claims is not defendants' violation of the FDCA, but defendants' failure to give adequate warnings about the prolonged use of metoclopramide." 2016 WL 4420637, at *12.

If only that were so. Instead, the so-called "failure to give warnings" extends solely, and no further than, the alleged failure to "update" in accordance with the 2000 FDA guidance document:

Although generic drug labeling is required to be the same as that of the brand name under federal law, defendant generic manufacturers, apparently, did not update their labeling "at the very earliest time possible" in accordance with the directive of the [FDA]. . . . To be sure, to avoid a clash with Mensing and Hatch-Waxman, plaintiffs may not contend that defendant generic manufacturers had a duty to provide warnings beyond those that the FDA approved for the brand name.

Id. at *14-15. So, even though NJ Reglan asserts that "Plaintiffs' claims do not 'exist solely by virtue of' a federal regulatory scheme" under Buckman, id. at *15, the result is indistinguishable – the New Jersey cause of action for failure to update was defined by the FDA's informal pre-2007 guidance (even after 2007??), enabled by that same federal duty (even though the FDA itself couldn't enforce it), and extends no further than the federal duty.

If it quacks like a duck....

We can only repeat something we've said many times before, strange things happen – particularly in state court – when preemption and personal injury cross paths. And this one really is strange, if not utterly singular: a state-law duty to update predicated on a federal guidance document not only without force of law ab initio, but then expressly repudiated by Congress in favor of a legally-binding standard that, as far as we can tell from the opinion, no defendant ever violated because the required FDA notice was never given.

The ultimate outcome, though, probably doesn't matter much. This litigation is just another New Jersey litigation make work project. The court relied heavily, id. at *13-14 on Fulgenzi v. PLIVA, Inc., 711 F.3d 578 (6th Cir. 2013) (discussed here), another Reglan-related case, but guess what? The plaintiff lost in Fulgenzi (discussed here) because the prescribing physician never read, let alone relied on, the allegedly inadequate generic warnings:

The undisputed facts in the record establish that plaintiff's physicians did not ever read, let alone rely on, [defendant's] inadequate 2004 warning. As set forth above, proximate cause is an essential element that plaintiff must establish in order to prevail on her Ohio failure-to-warn claim. . . . [A]ny presumption in favor of proximate cause resulting from its inadequate warning is rebutted by the fact that plaintiff's prescribing physicians cannot say that they ever read [defendant's] package insert for metoclopramide − adequate or otherwise. Indeed, the inadequacy of a warning cannot be the proximate cause of a plaintiff's injuries if the user of the product failed to read the warnings accompanying the product. Even if such a warning were adequate, it could not prevent the harm if the user did not read the warning. Consequently, an inadequate warning in a prescription package insert cannot be the proximate cause of a resulting injury if the physician did not read the insert prior to prescribing the medication.

Fulgenzi v. PLIVA, Inc., 140 F. Supp.3d 637, 649-50 (N.D. Ohio 2015) (citations and quotation marks omitted). That's the law just about everywhere, as we discuss here (50-state survey of failure-to-read-warning cases). Physicians not reading the warnings at issue is a particularly strong obstacle to failure to update claims involving generic drugs – because in most cases doctors don't prescribe the generic product at all, rather the pharmacy substitutes a generic for an innovator product, or selects one of several available generics without any input from the prescriber. Doctors won't be reading labels of drugs that they didn't actually prescribe.

There are several other reasons why duty to update claims are, frankly, lousy claims for plaintiffs to pursue. We listed them here. They range from medical causation, to risks being well-known in the medical community, to product identification. We've never seen a plaintiff assert a failure-to-update claim except where forced to by the force majeure of the Supremacy Clause. Even pleading the elements of such a case – particularly causation − will be a challenge going forward. See, e.g., Brinkley v. Pfizer, Inc., 772 F.3d 1133, 1138 (8th Cir. 2014); Strayhorn v. Wyeth Pharmaceuticals, 737 F.3d 378, 399-400 (6th Cir. 2013) (both dismissing update-related claims for failure to plead causation).

So these "nearly 1,000" cases will no doubt amount to busy work for lawyers – at tremendous expense to the defendants and to the justice system as a whole. We doubt that even 5% of them (less than 50) will survive summary judgment. We further doubt that most of these cases will even get that far. Instead, we predict that they will either be dismissed (if they can't pass the red-face test on causation) or else will be settled for some portion of whatever nuisance value that NJ Reglan has conferred upon them.

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.

James Beck
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.