BSCR Firm News/Blogs Feedhttps://www.bscr-law.com/?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10en-us23 Jul 2019 00:00:00 -0800firmwisehttps://blogs.law.harvard.edu/tech/rssCan't satisfy both the FDA and the State? The judge will be the judge of that.https://www.bscr-law.com/?t=40&an=92364&format=xml&p=5258&stylesheet=blog20 Jun 2019Drug / Device Law Blog<p>In May 2019, in a move rejecting the reasoning of the Third Circuit, the U.S. Supreme Court dove into two critical aspects of preemption analysis in <i>Merck Sharp &amp; Dohme Corp. v. Albrecht et al.</i>, No. 17-290, slip op. (U.S. May 20, 2019). The Court addressed <i>who</i> will decide whether preemption exists (a judge), and<i> how</i> to decide whether preemption exists where FDA action and state law conflict thereby destroying a plaintiff&rsquo;s related state claims.</p> <p>Specifically, the Court held a plaintiff&rsquo;s claim that a drug manufacturer failed to warn pursuant to state law will fail when a judge applies a &ldquo;clear evidence&rdquo; standard and finds that the relevant federal and state laws &ldquo;irreconcilably conflict.&rdquo;</p> <p>Petitioner drug manufacturer, Merck Sharp &amp; Dohme Corporation, sought Supreme Court review of the Third Circuit&rsquo;s decision to vacate and remand the lower court&rsquo;s Order granting Merck&rsquo;s Motion for Summary Judgment.&nbsp; The Respondents, more than 500 individuals who filed individual suits which were consolidated into a multi-district litigation (MDL), were prescribed an osteoporosis drug manufactured by Merck (Fosamax) and subsequently suffered rare thigh bone breaks (referred to in litigation as &ldquo;atypical femoral fractures&rdquo;).&nbsp; The Respondents alleged Merck breached a legal duty imposed by the state to warn of the risk of atypical femoral fractures associated with using Fosamax.&nbsp; Merck countered these claims with an &ldquo;impossibility preemption&rdquo; defense, arguing the Respondents&rsquo; state law claims should be dismissed because conflicting federal law displaces, or preempts, the state requirement.&nbsp; The Court fleshed out preemption standards set forth in an earlier Supreme Court case (<i>Wyeth v. Levine</i>) in an explicit attempt to aid lower courts when conducting preemption analyses, and remanded the case with these new understandings.&nbsp; While the Court remanded the case, it did opine that &ldquo;there is sufficient evidence to find that Merck violated state law by failing to add a warning about atypical femoral fractures to the Fosamax label.&rdquo;</p> <p>Under <i>Wyeth v. Levine</i>, 555 U.S. 555 (2009), a state-law failure-to-warn claim is preempted where there is &ldquo;clear evidence&rdquo; that the FDA would not have approved a change to the label.&nbsp; Since <i>Wyeth</i>, courts have struggled to both define and apply this &ldquo;clear evidence&rdquo; standard.&nbsp; In <i>Merck</i>, the Court elaborated on the clear evidence standard set out in <i>Wyeth </i>and held that Merck would have to show two things to trigger state law preemption: (1) Merck gave the FDA an evaluation or analysis concerning the specific dangers that would have merited the additional warning, and (2) Merck presented the would-be-state-compliant warning but was prohibited from adding said warning by the FDA.</p> <p>The original Fosamax label was approved by the FDA in 1995.&nbsp; The original label did not warn of the risk of atypical femoral fractures.&nbsp; While the Court points to the fact that Merck scientists knew of at least a &ldquo;theoretical risk&rdquo; of these fractures, Merck brought the theoretical considerations to the FDA&rsquo;s attention and the FDA approved a Fosamax label without requiring mention of the risk.&nbsp; In 2008, Merck applied to change the Fosamax label in two ways: (1) add reference to &ldquo;low-energy femoral shaft fracture&rdquo; in the Adverse Reactions section of the label, and (2) provide longer discussion focused on the risk of stress fractures in the Precautions section.&nbsp; The FDA approved the first addition, but rejected the second on the basis that <i>the discussion of &ldquo;stress fractures&rdquo; was not sufficiently related to the risk of the specific atypical femoral fracture.</i>&nbsp; This is because atypical femoral fractures are low energy fractures that are<i> the result</i> <i>of stress fractures</i>, and have different pain symptoms and more severe repair remedies.&nbsp; At that time, the FDA did however invite Merck to resubmit its application to address label change deficiencies.&nbsp; Instead, Merck withdrew its application and changed the Adverse Reactions section through the &ldquo;changes being effected&rdquo; (CBE) process.&nbsp; The CBE process is provided within the FDA regulations and permits drug manufacturers to change labels without prior FDA approval where &ldquo;newly acquired information &hellip; based on reasonable evidence&rdquo; warrants a new or stronger warning.&nbsp; A warning about &ldquo;atypical femoral fractures&rdquo; appeared on the Fosamax label in 2011, after the FDA ordered a label change based on its own analysis.&nbsp;</p> <p>Finally, the Court reiterates the long-standing principle that the only FDA agency actions capable of answering whether preemption exists are those taken pursuant to the FDA&rsquo;s congressionally delegated authority.&nbsp; Where, as in <i>Merck</i>, the answer to preemption revolves around a question of agency disapproval, the Court unambiguously held the question of agency disapproval is a question of law for a judge to decide, not a jury.&nbsp; Chatter of the role of a jury, specifically regarding factual questions about the meaning and effect of an agency decision in preemption cases, was silenced by the Court&rsquo;s Opinion.&nbsp; The Court unabashedly admits there are such factual questions within a preemption analysis, but held that those questions are &ldquo;subsumed within an already tightly circumscribed legal analysis and do not warrant submission alone or together with the larger pre-emption question to a jury.&rdquo;&nbsp; Ultimately, the Supreme Court remanded the case because the Third Circuit improperly analyzed the question of preemption as one of fact for a jury, rather than a question of law, and because the Court has now clarified how to properly apply the clear evidence standard.</p> <p><b>What does this mean for your company? </b></p> <p>If you, like Merck, are in the business of manufacturing drugs, you can take solace in the fact that an FDA preemption argument is in the hands of a judge.&nbsp; Because the Supreme Court has now held this issue is one exclusively for the Court, it may be ruled upon during motion practice with less strife related to facts &ldquo;subsumed&rdquo; in this kind of complex legal analysis.&nbsp; But this strategic advantage cuts both ways.&nbsp; Drug-manufacturers will now have to show that the company submitted a state law required warning to the FDA.&nbsp; Litigation of these issues to date has largely involved questions about what exactly the FDA rejected when disapproving label changes.&nbsp; The Court makes clear that the manufacturer&rsquo;s proposed label change cannot be of some broader, less threatening risk &ndash; like stress fractures &ndash; when the company has knowledge of a specific, less appeasing risk &ndash; like atypical femoral fractures.&nbsp; This is to say, while the power that comes with an impossibility preemption defense can be a great litigation tool, the responsibility to fully inform and present the FDA with state-compliant warnings is equally great.&nbsp;</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Consider Playing By This Book's Rules: FDA-MITRE Cybersecurity Guidancehttps://www.bscr-law.com/?t=40&an=83739&format=xml&p=5258&stylesheet=blog31 Oct 2018Drug / Device Law Blog<p>As part of Cybersecurity Awareness Month, we continue our discussion about the <a href="https://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm622074.htm">FDA&rsquo;s efforts</a> to help prepare various entities to address cybersecurity threats, vulnerabilities, and even attacks. In our previous <a href="https://www.bscr-law.com/?t=40&amp;an=80904&amp;format=xml&amp;stylesheet=blog&amp;p=5258">post</a>, we previewed the FDA and MITRE&rsquo;s cybersecurity Regional Incident Preparedness and Response Playbook (the &ldquo;<a href="https://www.mitre.org/publications/technical-papers/mitre-creates-playbook-on-medical-device-cybersecurity">playbook</a>&rdquo;) for health care delivery organizations.&nbsp;Here, we take a more in depth look into what that playbook has to offer.</p> <p>The playbook&rsquo;s focus is primarily aimed at preparing Health Care Delivery Organizations (&ldquo;HDOs&rdquo;), including their stay, for addressing and responding to cybersecurity threats. The <a href="https://www.mitre.org/publications/technical-papers/mitre-creates-playbook-on-medical-device-cybersecurity">playbook</a> is not intended to address the day-to-day patch management of devices, but rather addresses threats and vulnerabilities for large-scale, multi-patient impact and patient safety concerns.</p> <p>The <a href="https://www.mitre.org/publications/technical-papers/mitre-creates-playbook-on-medical-device-cybersecurity">playbook</a>&rsquo;s guidance primarily consists of four guiding steps, going in chronological order: (1) preparation, (2) detection and analysis, (3) containment eradication and recovery, and (4) post-incident activity.&nbsp;Below is a summary of these action steps, but you are encouraged to read the actual <a href="https://www.mitre.org/publications/technical-papers/mitre-creates-playbook-on-medical-device-cybersecurity">playbook</a> for a more in-depth explanation and/or expansion on the summary below.</p> <p><strong>(1)&nbsp;&nbsp; PREPARATION</strong></p> <p>Assess and bolster cyber defensive measures and develop handling process and procedures to enable better operations when an incident arises.</p> <p>Suggested Steps: &nbsp;&nbsp;</p> <p style="margin-left: 40px;">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Incorporate cybersecurity awareness into medical device procurement in order to strengthen the response to a cybersecurity incident.&nbsp;(<i>E.g. Request a Software Bill of Materials to identify and address vulnerable device components.)</i></p> <p style="margin-left: 40px;">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Take a medical device asset inventory. (<i>E.g. Identify device name and description, physical location of device, device owner and manager.</i>)</p> <p style="margin-left: 40px;">3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Perform a hazard vulnerability analysis to assess and identify potential gaps in emergency planning, including a review as anticipated cybersecurity threats and existing mitigations. (<i>E.g. Identify potential cybersecurity risks, such as lack of staff with the ability to detect and respond to a cybersecurity incident.</i>)</p> <p style="margin-left: 40px;">4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Prepare medical technical specialists (<i>i.e. the response team to all hazard incidents</i>) with cybersecurity and medical device expertise as part of the hospital incident management team.</p> <p style="margin-left: 40px;">5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Create an Emergency Operation Plan to determine how the HDO will &ldquo;respond to and recover from a threat, hazard, or other incident&rdquo; with a device. (<i>E.g. Identify members and their roles and responsibilities.</i>)</p> <p style="margin-left: 40px;">6.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Create an overall Incident Response communication plan (<i>E.g. Identity key internal and external communication roles</i>.)</p> <p style="margin-left: 80px;">a.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Specify incident-sharing expectations for all participants in the above communication plan. (<i>E.g. What incidents can and cannot be shared?</i>)</p> <p style="margin-left: 80px;">b.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Identify cybersecurity incidents, initiate outreach to manufacturer and then to broader healthcare community.&nbsp;</p> <p style="margin-left: 80px;">c.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Implement external incident notification and continue to stay abreast of intrusion information and/or mitigation recommendations from manufacturer(s).</p> <p style="margin-left: 80px;">d.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Create a communication template for how incident notification will occur and how.</p> <p style="margin-left: 40px;">7.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Implement user awareness training with all medical device users in your company and conduct preparedness and response exercises for all-hazards.</p> <p><strong>(2)&nbsp;&nbsp; DETECTION AND ANALYSIS</strong></p> <p>Identify and establish that an incident has occurred.</p> <p>Suggested Steps:</p> <p style="margin-left: 40px;">1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Define the priority of and appropriate level of response to incidents.</p> <p style="margin-left: 40px;">2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Implement formal and informal reporting obligations (<i>Note: Manufacturers are required to conduct a formal notification of the incident to its customers and user community.</i>)</p> <p style="margin-left: 40px;">3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The incident investigation and analysis can begin once initial incident parameters have been set.&nbsp;</p> <p style="margin-left: 40px;">4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; All activities taken to address cybersecurity incidents and responses must be recorded or otherwise documented.&nbsp;Benefits of recording these activities include preserving evidence for potential criminal activity and learning to improve the response for the future.</p> <p><strong>(3)&nbsp;&nbsp; CONTAINMENT ERADICATION AND RECOVERY</strong></p> <p>Response to the confirmed cybersecurity incident begins.&nbsp;Such activities could include a strategy of &ldquo;contain, clear, and deny&rdquo; <i>(i.e. halt cybersecurity incident, fix it and restore services quickly) </i>or a &ldquo;monitor and record&rdquo; strategy<i> (i.e. watch and &ldquo;capture&rdquo; adversary actions)</i>.<br /> <br /> <strong>(4)&nbsp;&nbsp; POST-INCIDENT ACTIVITY</strong></p> <p>Identify what went well and what did not; such information can be leveraged to improve existing plan and future response. It is also suggested to retain a trained, digital forensics expert to fully identify the damage done.</p> <p>For immediate, additional information about addressing cybersecurity breaches in medical devices, consider visiting the BSCR blog posts below addressing cybersecurity:</p> <ul> <li><a href="https://www.bscr-law.com/?t=40&amp;an=80904&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Summary of FDA&rsquo;s 10.1.18 Announcement</a>.</li> <li>Three-part series on addressing cybersecurity breaches in medical devices:&nbsp;<a href="https://www.bscr-law.com/?t=40&amp;an=61608&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part I</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=62085&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part II</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=62097&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part III</a>.</li> <li>Four-part series addressing postmarket management of cybersecurity in medical devices: <a href="https://www.bscr-law.com/?t=40&amp;an=49777&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part I</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=49845&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part II</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=50038&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part III</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=50131&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part IV</a>.</li> </ul>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10FDA Announces Strengthened Focus On Cybersecurityhttps://www.bscr-law.com/?t=40&an=80904&format=xml&p=5258&stylesheet=blog11 Oct 2018Drug / Device Law Blog<p>CYBERSECURITY. In a <a href="https://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm622074.htm">statement</a> issued from FDA Commissioner Scott Gottlieb, M.D., the FDA made clear the threat of cybersecurity attacks are no longer a theoretical discussion, but are present and as such steps must be taken to proactively address future threats. Such attacks are already here in other capacities, including attacks on financial institutions, government agencies, and health care systems.&nbsp;</p> <p>The FDA&rsquo;s specific concerns revolve around attacks on patient medical devices.&nbsp;Cybersecurity researchers have found various vulnerabilities in patient medical devices that could result in bad actors gaining access and control over the patient&rsquo;s medical device.&nbsp;&nbsp; While &ldquo;FDA isn&rsquo;t aware of any reports of an unauthorized user exploiting a cybersecurity vulnerability in a medical device that is in use by a patient,&rdquo; the &ldquo;risk of such an attack persists.&rdquo;&nbsp;As a result, in an effort to instill confidence in both patients and providers that it can effectively address any reported medical device cyber vulnerabilities, the FDA has determined that it is important to address such a threat of an attack now.</p> <p>In taking such proactive steps, the FDA announced it has coordinated with the MITRE Corporation to launch a cybersecurity &ldquo;<a href="https://www.mitre.org/publications/technical-papers/mitre-creates-playbook-on-medical-device-cybersecurity">playbook</a>&rdquo; for health care delivery organizations, along with the &ldquo;signing of two significant <a href="https://www.fda.gov/AboutFDA/PartnershipsCollaborations/MemorandaofUnderstandingMOUs/default.htm">memoranda of understanding</a>.&rdquo;&nbsp;A &ldquo;sneak peek&rdquo; at the playbook shows it addressing the types of readiness health care delivery organizations should consider in order to be better prepared and address cybersecurity incidents involving their respective medical devices. The memoranda, among other actions, created such groups as information sharing analysis organizations, which are groups of experts (aimed to include manufacturers who share potential vulnerabilities and threats) that gather, analyze and disseminate important information about cyber threats. &nbsp;</p> <p>The FDA&rsquo;s work in addressing cybersecurity threats dates back to 2013 with the establishment of its medical device cybersecurity program.&nbsp;The FDA has issued a premarket and postmarket guidance for manufacturers to consider in addressing their cybersecurity vulnerabilities and threats.&nbsp;While the FDA&rsquo;s premarket guidance was finalized in 2014, it announced in this statement that it plans on publishing a &ldquo;significant update to that guidance to reflect the FDA&rsquo;s most current understandings of, and recommendations regarding, this evolving space.&rdquo; One such example included providing customers with a list of cybersecurity bill of materials to ensure that device customers and users are able to respond quickly to potential cybersecurity threats.&nbsp;</p> <p>Finally, the FDA is taking steps to bring additional resources to build its medical device cybersecurity program, starting with its <a href="https://www.fda.gov/NewsEvents/Newsroom/PressAnnouncements/ucm596554.htm">Fiscal Year 2019 Budget</a> in order to establish additional &ldquo;regulatory paradigms&rdquo; to proactively address vulnerabilities and threats.</p> <p>Be on the lookout for a future discussion of the FDA&rsquo;s collaborative &ldquo;playbook&rdquo; with MITRE, as well as a posting on the FDA&rsquo;s &ldquo;significant update&rdquo; to its 2014 premarket guidance.</p> <p>For immediate, additional information about addressing cybersecurity breaches in medical devices, visit our prior posts addressing cybersecurity:</p> <ul> <li>Three-part series on addressing cybersecurity breaches in medical devices:&nbsp;<a href="https://www.bscr-law.com/?t=40&amp;an=61608&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part I</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=62085&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part II</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=62097&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part III</a>;</li> <li>Four-part series addressing postmarket management of cybersecurity in medical devices: <a href="https://www.bscr-law.com/?t=40&amp;an=49777&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part I</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=49845&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part II</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=50038&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part III</a>, <a href="https://www.bscr-law.com/?t=40&amp;an=50131&amp;format=xml&amp;stylesheet=blog&amp;p=5258">Part IV</a>.</li> </ul>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10"Impossibility Preemption" Remains Alive and Well in Missouri for Generic Drug Manufacturershttps://www.bscr-law.com/?t=40&an=75694&format=xml&p=5258&stylesheet=blog06 Apr 2018Drug / Device Law Blog<p>&ldquo;Impossibility preemption&rdquo; applies to bar tort claims where it is impossible for a party to comply with both state and federal law. In the recent opinion of <i>Raskas v. Teva Pharms. USA, Inc.</i>, No. 4:17-CV-2261 RLW, 2018 U.S. Dist. LEXIS 3507 (E.D. Mo. January 8, 2018), the Eastern District of Missouri reaffirmed application of &ldquo;impossibility preemption&rdquo; to generic drug manufacturers &nbsp;on strict liability and negligent defective design and failure to warn claims.&nbsp;</p> <p>The allegations in the <i>Raskas v. Teva</i> complaint provide the story of a young man, Ralph Raskas, who, after seeking treatment for nausea and vomiting, ingested the medication prescribed by his physician - generic metoclopramide - and allegedly developed pain and restlessness in his legs.&nbsp;After being diagnosed with &ldquo;drug-induced acute akathisia,&rdquo; he complained of significant pain and eventually committed suicide after two prior attempts.&nbsp;&nbsp;His father filed a wrongful death action against Teva Pharmaceuticals, USA (Teva) and Actavis Elizabeth, LLC (Actavis) - manufacturers of the dispensed generic metoclopramide - alleging that the drug caused his son&rsquo;s neurological injuries and suicide.&nbsp;Plaintiff asserted claims for strict liability and negligent defective design and failure to warn, negligence in identifying risks associated with the drug, as well as what he contended was a failure to update the generic medication&rsquo;s labeling to conform to that of its brand name equivalent.&nbsp;Relying upon <i>PLIVA, Inc. v. Mensing</i>, 564 U.S. 608 (2011), and <i>Mutual Pharm. Co. v. Bartlett</i>, 570 U.S. 472 (2013), Teva and Actavis sought dismissal of all claims against them on federal preemption grounds.&nbsp;</p> <p>The <i>Raskas</i> court began its analysis of the plaintiff&rsquo;s claims by reviewing the approval requirements of the Food and Drug Administration (FDA) for both brand name and generic drugs.&nbsp;To gain approval of brand name drugs, a manufacturer must submit a new-drug application (NDA) that includes clinical investigative reports and all relevant information to allow the agency to determine whether the drug is safe for use.&nbsp;On the other hand, approval of a generic drug typically requires only that the generic be &ldquo;bioequivalent&rdquo; to the branded medication.&nbsp;In fact, a generic may receive FDA approval without any <i>in</i> <i>vivo</i> studies, solely based on <i>in</i> <i>vitro</i> studies that study dissolution of the proposed generic. &nbsp;<i>See </i>21 C.F.R. &sect;&sect; 320.24(b)(5) and 320.22(d)(3).</p> <p>Critically for the generic drug manufacturers in <i>Raskas</i>, 21 C.F.R. Part 314 prohibits generic drug manufacturers from 1) making any unilateral changes to a drug&rsquo;s label, and 2) deviating from the drug&rsquo;s approved formulation.&nbsp;<i>See</i> 21 21 C.F.R. &sect;&sect; 314.94(a)(8)(iii), 314.150(b)(10), and 314.70(b)(2)(i).&nbsp;These federal regulatory restrictions are the basis for the &ldquo;impossibility preemption&rdquo; found in <i>Raskas</i>.</p> <p>In rejecting the plaintiff&rsquo;s defective design claims, the court considered <i>Brinkley v. Pfizer, Inc.</i>, 772 F.3d 1133 (8<sup>th</sup> Cir. 2014), in which metoclopramide design defect claims were specifically precluded due to preemption because the only way the manufacturer could avoid liability under Missouri law was by redesigning the product.&nbsp;If a generic drug manufacturer were required to redesign the product to comply with Missouri state law, it would be impossible to comply with federal law, which requires a generic drug&rsquo;s formulation to be bioequivalent to the branded medication and the generic&rsquo;s labeling to be identical to that of the brand name drug.&nbsp;This is the definition, and a descriptive example, of impossibility preemption, which provides that &ldquo;[w]here state and federal law directly conflict, state law must give way.&rdquo;&nbsp;<i>Mensing</i>, 564 U.S. at 617.&nbsp;</p> <p>Raskas&rsquo;s failure to warn claims were found to be similarly barred by impossibility preemption, because the warning labels on the generic metoclopramide manufactured by Teva and Actavis were required, under 21 C.F.R. Part 314, to be identical to those of the brand name medication Reglan&reg;.&nbsp;If the failure to warn claims were allowed to proceed, generic drug manufacturers - in order to escape state tort liability - would be required to relabel their products to provide additional information or warnings, which is directly prohibited under federal regulations.&nbsp;The Missouri federal district court in <i>Raskas</i> determined it would be impossible for Teva and Actavis to comply with both state and federal law in this instance, so dismissal of the failure to warn claims against them was appropriate.&nbsp;</p> <p>Although the plaintiff attempted to distinguish its claims from those presented in controlling legal precedent, the court ultimately concluded that impossibility preemption applied to each of the asserted negligence, strict liability, and wrongful death claims for failure to warn or defective design.&nbsp;The plaintiff was, however, granted leave to amend his complaint to adequately plead an alleged claim against Teva and Actavis for failure to update their labeling to conform to that of Reglan&reg;, the brand name medication.</p> <p>The <i>Raskas</i> opinion may be found <a href="/B07AF5/assets/files/Documents/2018.01.08 Raskas v. Teva Order.pdf">here</a>&nbsp;in its entirety.</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Breaking Up [Plaintiffs] Is [Not] Hard To Dohttps://www.bscr-law.com/?t=40&an=75525&format=xml&p=5258&stylesheet=blog28 Mar 2018Drug / Device Law Blog<p>While Neil Sedaka may have convinced many that breaking up is hard to do, Judge Stephen N. Limbaugh, Jr. of the United States District Court for the Eastern District of Missouri (&ldquo;EDMO&rdquo;) has made it clear that breaking up non-Missouri related Plaintiffs from a product liability case is certainly not hard to do in the post-<i>Bristol-Myers Squibb Co.</i> era.</p> <p>On January 24, 2018, the EDMO added to the split in authority between Missouri and California, two forums favored by Plaintiffs, thereby testing the limits of <i>Bristol-Myers Squibb Co. v. Super Ct. of Cal., 137 S. Ct. 1772 (2017) (&ldquo;BMS&rdquo;)</i>.In <i>Nedra Dyson, et al., v. Bayer Corporation, et al.</i>, No. 4:17CV2584- SNLJ, (E.D. MO Jan. 24, 2018) (&ldquo;<i>Dyson</i>&rdquo;), Judge Limbaugh of the EDMO granted Defendants&rsquo; Motion to Dismiss 92 non-Missouri related Plaintiffs in a product liability lawsuit based on a lack of personal jurisdiction, finding that a Defendant&rsquo;s clinical trials and marketing of a product in the state of Missouri does not establish personal jurisdiction for purposes of non-Missouri related Plaintiffs&rsquo; claims for that product. This is consistent with other recent EDMO decisions:</p> <ul> <li><i>See Siegfried v. Boehringer Ingelheim Pharmaceuticals, Inc.</i>, 2017 WL 2778107 (E.D. Mo. June 27, 2017);</li> <li><i>Jordan v. Bayer Corp.</i>, No. 4:17cv865(CEJ), 2017 WL 3006993 (E.D. Mo. July 14, 2017);</li> <li><i>Jinright v. Johnson &amp; Johnson, Inc., </i>2017 WL 3731317 (E.D. Mo. Aug. 30, 2017);</li> <li><i>Shaeffer et al., v. Bayer Corp., et al., </i>4:17-CV-01973 JAR (E.D. Mo. Feb. 21, 2018).</li> </ul> <p>The <i>Dyson</i> Defendants, who were also not citizens of Missouri, relied on <i>BMS</i> to argue that the EDMO lacked personal jurisdiction over the claims of 92 non-Missouri related Plaintiffs, and should be dismissed. The Defendants argued that dismissal of these Plaintiffs would provide complete diversity between the remaining Plaintiffs and Defendants and the amount in controversy would still exceed $75,000.&nbsp;This quickly became a fight between the parties, with one side trying to persuade the court to decide personal jurisdiction before subject matter jurisdiction and the other side arguing vice-versa. Ultimately, the court determined that personal jurisdiction could and should be decided prior to subject matter jurisdiction, because it provided the more straightforward analysis in light of <i>BMS</i>.&nbsp;Deciding subject matter jurisdiction would involve resolution of notoriously complex issues, reasoned the court.</p> <p><i><u>Quick Recap On BMS:</u></i>&nbsp;<i>As a brief refresher, BMS involved both California and out of state Plaintiffs who sued in California state court based on alleged injuries caused by Defendant BMS&rsquo; drug. The United States Supreme Court, who took the case on a writ of certiorari, overturned the state court, applying &ldquo;settled principles regarding specific jurisdiction,&rdquo; finding that California state courts fail to retain specific personal jurisdiction over non-resident Defendants for claims asserted by non-resident Plaintiffs&nbsp;that do not arise out of or relate to the Defendant&rsquo;s contacts with the forum. The Court rejected Plaintiffs arguments for specific personal jurisdiction based on alleged marketing and promotion of the product and clinical trials held in the state of California. The Court would also not allow the resident Plaintiffs&rsquo; allegations to confer personal jurisdiction over the non-resident Plaintiffs claims.&nbsp;Therefore, the Supreme Court dismissed the claims of the non-resident Plaintiffs.</i></p> <p>In <i>Dyson</i>, the non-Missouri related Plaintiffs conceded that the medical device at issue (Essure) was not implanted in Missouri. However, Plaintiffs argued that their allegations concerning Defendant Bayer&rsquo;s connections with Missouri should support the court&rsquo;s exercise of personal jurisdiction. Plaintiffs alleged that Bayer&rsquo;s marketing strategy was developed in Missouri, Missouri was one of the eight sites chosen to conduct pre-market clinical devices on the product (Essure), the original manufacture of the product&rsquo;s conduct was in Missouri, the sponsoring of biased medical trials was in Missouri, and St. Louis, Missouri was the first city to commercially offer the Essure implant procedure.&nbsp;</p> <p>Those arguments failed to persuade Judge Limbaugh, who ultimately found that the <i>Dyson </i>Plaintiffs failed to make a <i>prima facie</i> showing for personal jurisdiction and, as such, he denied their motion for jurisdictional discovery to support those arguments. Relying on <i>BMS</i>, Judge Limbaugh rejected Plaintiffs&rsquo; marketing campaign arguments, pointing out that the non-Missouri Plaintiffs not only failed to allege they viewed Essure advertising in Missouri, but also failed to allege they purchased, were prescribed or were injured by the product in Missouri. Thus, it was not relevant that Defendant first marketed Essure in Missouri. As for Plaintiffs&rsquo; argument regarding clinical trials in Missouri, Judge Limbaugh found such alleged conduct too attenuated to serve as a basis for specific personal jurisdiction over Defendants. In fact, the non-Missouri Plaintiffs failed to allege they even participated in a Missouri clinical study or that they reviewed and relied on the Missouri clinical studies in deciding to use the products.</p> <p>In contrast to <i>Dyson</i>, Plaintiffs have tried to rely on the recent California case&nbsp;<i>Dubose v. Bristol-Myers Squibb Co.</i>, No. 17-cv-00244, 2017 U.S. Dist. LEXIS 99504 (N.D. Cal. June 27, 2017) in support of specific personal jurisdiction over non-forum Defendants.&nbsp;<i>Dubose</i>, however, does not appear to employ the same analysis as <i>BMS</i> or its progeny.</p> <p>In <i>Dubose</i>, a South Carolina resident Plaintiff sued AstraZeneca, Bristol-Myers Squibb, and McKesson in California federal court, alleging a defect in a prescription diabetes drug. &nbsp;The&nbsp;<i>Dubose&nbsp;</i>court relied upon&nbsp;<i>Walden v. Fiore</i>, 134 S.Ct. 1115 (2014), a 2014 U.S. Supreme Court decision that was in fact a pro-Defendant ruling intended to limit the states&rsquo;&nbsp;exercise of personal jurisdiction over non-resident Defendants. The <i>Dubose </i>Court&nbsp;reasoned that because&nbsp;<i>Walden</i>&nbsp;stressed that only the Defendants&rsquo;&nbsp;conduct could justify exercise of personal jurisdiction, any jurisdictional analysis should ignore Plaintiff&rsquo;s residence or place of injury, and focus instead upon conduct that might &ldquo;tether&rdquo;&nbsp;the Defendant to the forum state. Ultimately, the Court relied on the Ninth Circuit&rsquo;s preexisting &ldquo;but for&rdquo; test, holding that the pre-approval clinical trials were &ldquo;part of an unbroken chain of events leading to Plaintiff&rsquo;s alleged injury&rdquo; and, therefore, specific jurisdiction existed because Plaintiff&rsquo;s injuries &ldquo;would not have occurred but for [Defendants] contacts with California.&rdquo; Regardless, the <i>Dubose </i>Court ultimately transferred the case to South Carolina, the Plaintiff&rsquo;s home state.</p> <p>The judge in&nbsp;<i>Dubose&nbsp;</i>also decided&nbsp;<i>Cortina v. Bristol-Myers Squibb Co.</i>, No. 17-cv-00247-JST, 2017 U.S. Dist. LEXIS 100437 (N.D. Cal. June 27, 2017) on the same theories, denying a motion to dismiss but transferring the case to New York, where the Plaintiff was a resident and was prescribed the drug at issue.&nbsp;&nbsp;However, in a footnote, the&nbsp;<i>Cortina</i>&nbsp;court noted that, &ldquo;[it] does not mean to suggest that even a&nbsp;<i>de minimis</i>&nbsp;level of clinical trial activity would satisfy the requirements of specific jurisdiction.&rdquo; &nbsp;&nbsp;</p> <p>While the holdings for the <i>Dubose</i> and <i>Cortina</i> case appear to have relied upon attenuated claims of specific personal jurisdiction, in the EDMO, Judge Limbaugh concluded that the <i>Dyson</i> non-Missouri Plaintiffs&rsquo; claims were too attenuated from Missouri to prove specific, case linked personal jurisdiction. For example, the <i>Dubose </i>Plaintiff did not allege that she participated in any of the Defendants&rsquo; California clinical trials, but the <i>Dubose</i> court relied on others, not a party to the case, who participated in them. If specific personal jurisdiction exists in every state where a clinical trial occurred, then any Plaintiff who used the subject drug conceivably could sue the manufacturer in any of those states&mdash;no matter where the manufacturer is based and no matter where the Plaintiff resides or used the drug. It would be illogical for courts to adopt this rationale, calling that &ldquo;specific&rdquo;&nbsp;personal jurisdiction, and would be contrary to the United States Supreme Court&rsquo;s recent pronouncements on personal jurisdiction, including in <i>BMS</i>.</p> <p>Other recent cases have held similarly to the EDMO in <i>Dyson</i>, dismissing non-resident Plaintiffs due to a lack of both general and personal jurisdiction. For example, the Southern District of Illinois has been granting dismissal of non-Illinois Plaintiffs and denying remand in pharmaceutical drug, product liability cases.&nbsp;Specifically, those cases held that misjoined, multi-Plaintiff complaints no longer preclude removal, that there was no general personal jurisdiction pursuant to <i>Daimler AG v. Bauman</i>, 134 S. Ct. 756 (2014) and no specific personal jurisdiction existed pursuant to <i>BMS</i>, and/or found that conducting in-state clinical trials is not sufficient contact to support specific personal jurisdiction in suits by non-residents. <i>See</i>;&nbsp;<u>Braun&nbsp;v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4224034 (S.D. Ill. Sept. 22, 2017);&nbsp;<u>Bandy v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4224035 (S.D. Ill. Sept. 22, 2017);&nbsp;<u>Pirtle v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4224036 (S.D. Ill. Sept. 22, 2017);&nbsp;<u>Roland&nbsp;v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4224037 (S.D. Ill. Sept. 22, 2017);&nbsp;<u>Woodall&nbsp;v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4237924 (S.D. Ill. Sept. 22, 2017); and&nbsp;<u>Berousee v. Janssen Research &amp; Development, LLC</u>, 2017 WL&nbsp;4255075 (S.D. Ill. Sept. 26, 2017).</p> <p>Bringing this back to <i>Dyson</i>, Judge Limbaugh&rsquo;s decision reaffirms that it really is not that hard to break up Missouri Plaintiffs from non-Missouri Plaintiffs in a product liability lawsuit where the non-Missouri Plaintiffs cannot truthfully allege that their claims arise out of a connection to the state of Missouri (and cannot solely rely on clinical trials occurring in Missouri).&nbsp;This is not to say that non-Missouri Plaintiffs will never find another forum and/or that their claims are foreclosed; rather, those Plaintiffs have a better chance of avoiding a bad break-up by bringing their claims in the forum out of which their claims allegedly arise.&nbsp;</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Missouri Supreme Court May Be Signaling a Change in Analysis of Misjoinder of Claims in Multi-Plaintiff Product Liability Caseshttps://www.bscr-law.com/?t=40&an=69919&format=xml&p=5258&stylesheet=blog19 Oct 2017Drug / Device Law Blog<p>On October 13, 2017, the Missouri Supreme Court issued a preliminary writ of prohibition directed to Circuit Judge Rex Burlison of the Circuit Court for the City of St. Louis, temporarily staying the talc case, <i>Valerie Swann, et al. v. Johnson &amp; Johnson, et al</i>.&nbsp; The Supreme Court case number is SC96704.&nbsp; The plaintiffs, on behalf of the trial court, are to answer the writ petition by November 13, 2017.</p> <p>Plaintiff Michael Blaes is one of 47 plaintiffs in the case, who contend that they or their decedents developed ovarian cancer following use of talcum powder.&nbsp; Johnson &amp; Johnson alleges that Blaes&rsquo;s decedent did not purchase or use talcum powder in the City of St.&nbsp;Louis.&nbsp; Blaes&rsquo;s case was set for separate trial from those of the other plaintiffs, but Judge Burlison declined to formally sever his claim such that it could be reassigned and venue assessed. &nbsp;That decision is the subject of Johnson &amp; Johnson&rsquo;s petition for a writ of prohibition.</p> <p>Missouri has long had a troubled history with venue analysis.&nbsp; As part of tort reform in 2005, the legislature made significant changes to the venue statute, designed to prevent forum shopping.&nbsp; The recent explosion in &ldquo;litigation tourism&rdquo; focused in the City of St. Louis has not been due to any change in, or deficiency of, the venue statute and the joinder rules, but in changes in the application of long-standing principles of venue and joinder.</p> <p>Refusal to sever unrelated claims is at the core of the problem.&nbsp; Litigation tourism in St.&nbsp;Louis depends upon a single, anchor plaintiff who is a Missouri resident with a plausible jurisdictional claim and basis to claim venue in the City of St. Louis, with dozens of unrelated, out-of-state plaintiffs clinging to that anchor plaintiff&rsquo;s case to justify pursuit of claims in Missouri against non-residents. &nbsp;The claims are misjoined and should be severed, but to date the Missouri Supreme Court has declined to find that a trial court&rsquo;s refusal to sever misjoined claims warrants reversal on appeal unless the defendant can establish that the severance decision was prejudicial to the outcome (by establishing that the City of St. Louis is a biased venue).&nbsp; <i>See&nbsp;Barron v. Abbott Labs., Inc</i>., No. SC96151, 2017 Mo. LEXIS 403, at *6 (Sep.&nbsp;12, 2017).</p> <p>Severance has not always been this controversial, but reflects a change in the application of Missouri law and procedure in recent years.&nbsp; Rule 52.06 of the Missouri Rules of Civil Procedure is titled &ldquo;Misjoinder and nonjoinder of parties,&rdquo; and provides that &ldquo;Any claim against a party may be severed and proceeded with separately.&rdquo;&nbsp; Misjoinder of claims or parties <b>requires</b> severance of the claims.&nbsp; <i>See State ex rel. Gulf Oil Corp. v. Weinstein</i>, 379 S.W.2d 172, 174 (Mo. App. St. L. 1964).</p> <p>Rule 52.05 identifies the only circumstances under which the claims of multiple plaintiffs may be properly joined in a single action:</p> <p style="margin-left: 40px;">All persons may join in one action as plaintiffs if they assert any right to relief jointly, severally, or in the alternative in respect of or arising out of <b>the same transaction, occurrence or series of transactions or occurrences <u>and</u> if any question of law or fact common to <u>all</u> of them will arise in the action.</b></p> <p>Mo. R. Civ. P. 52.05(a) (emphasis added).&nbsp; Both tests must be met for plaintiffs to be joined in a single action.&nbsp; <i>Id.</i>; <i>State ex rel. Allen v. Barker</i>, 581 S.W.2d 818, 826 (Mo. banc 1979).&nbsp; If those requirements are not met, the claims are misjoined and severance is required.&nbsp; Even if joinder is permitted, severance is still permissible in the trial court&rsquo;s discretion, based upon factors related to fairness, economy, and prejudice.&nbsp; <i>See</i> <i>Wilson v. Bob Wood &amp; Associates, Inc.</i>, 633 S.W.2d 738, 743 (Mo. App. W.D. 1981).</p> <p>Rule 52.05(a) is analogous to Fed. R. Civ. P. 20(a), which provides that parties may be properly joined only where claims by or against them arise out of the same transaction or occurrence or present common questions of law or fact.&nbsp; In <i>State ex rel. Allen v. Barker</i>, 581 S.W.2d 818, 826 (Mo.1979) the Missouri Supreme Court discussed the adoption of Rule 52.05(a), recognized that it was patterned after the federal rule, and applied federal cases to interpret it.&nbsp; <i>Id.&nbsp; </i>The federal rule has been extensively construed, and overwhelmingly find that the claims of multiple plaintiffs are misjoined when the only commonality amongst plaintiffs is that they allege damages resulting from using the same product.&nbsp; <i>See, e.g.,</i> <i>In re Orthopedic Bone Screw Prods. Liab. Litig., MDL No. 1341</i>, 1995 WL 428683, at *5-6 (E.D. Pa. July 15, 1995).&nbsp; In the bone screw litigation, the only plaintiffs who were allowed to remain joined in a single action were those who underwent surgery by the same doctor or group of doctors, at the same hospital, and who received the same or a similar device by the same manufacturer.&nbsp; <i>Id.</i> at *5.&nbsp; There is no reason in the rule why Missouri should be applying joinder principles in a manner so inconsistent with the federal courts.</p> <p>Recent jurisprudence in the City of St. Louis and in the Eastern District Court of Appeals, in fact, is inconsistent with those courts&rsquo; own past precedent on misjoinder and severance.&nbsp; In <i>Gulf Oil</i>, plaintiffs had purchased fuel oil in unrelated transactions at different times.&nbsp; <i>Id.</i> at 174.&nbsp; These transactions did not constitute the &ldquo;same transaction nor a series of transactions.&rdquo;&nbsp; <i>Id.</i> at 175.&nbsp; Moreover, even though the plaintiffs all sustained fires, these occurred on different dates.&nbsp; <i>Id. </i>&nbsp;Accordingly, the plaintiffs&rsquo; losses did not constitute the same &ldquo;occurrence.&rdquo;&nbsp; <i>Id.&nbsp; </i></p> <p>The <i>Gulf Oil </i>court was keenly focused upon what is the &ldquo;transaction&rdquo; and what is the &ldquo;occurrence&rdquo; that is common <b><i>to the plaintiffs</i></b>.&nbsp; Because the issue is joinder of plaintiffs, it is a plaintiff-focused, not defendant-focused analysis.&nbsp; Recent jurisprudence on the eastern side of the state has shifted that focus to the notion that plaintiffs&rsquo; claims can arise out of the same transaction or occurrence when they derive from common conduct of the defendant, which has been expanded to include the design, marketing, and sale of the product.&nbsp; In reaching these decisions, the early trial court orders rely upon cases analyzing the proper joinder of <b><i>defendants</i></b>, which is, of course, a defendant-behavior-focused analysis. &nbsp;</p> <p>Taken to the illogical extreme, the approach of focusing upon the defendants&rsquo; business practices and product design to establish joinder would allow any purchaser of a product to join with any single Missouri plaintiff and to pursue their claims in Missouri.&nbsp; It is simply untenable, and seems inevitable that, if the Missouri Supreme Court does not curtail this problem, the U.S. Supreme Court will.&nbsp; Allowing non-residents to sue non-residents for extraterritorial conduct and injuries is not constitutionally defensible.&nbsp; Personal jurisdiction limitations &ldquo;are a consequence of territorial limitations on the power of the respective States.&rdquo;&nbsp; <i>Hanson v. Denckla</i>, 357 U.S. 235, 251 (1958); <i>see also World-Wide Volkswagen Corp v. Woodson</i>, 444 U.S. 286, 292 (1980) (minimum contacts requirement serves the dual functions of protecting defendant against the burden of litigation and ensuring states &ldquo;do not reach out beyond the limits imposed on them by their status as coequal sovereigns in our federal system&rdquo;). &nbsp;</p> <p>There are hopeful signs &ndash; the Eastern District Court of Appeals just overturned the first talcum verdict against Johnson &amp; Johnson for lack of personal jurisdiction.&nbsp; <i>See Estate of Fox v. Johnson &amp; Johnson</i>, No. ED104580, 2017 Mo. App. LEXIS 1043 (Mo. App. E.D. Oct. 17, 2017).&nbsp; The dust has not yet settled on these issues, however.</p> <p>Johnson &amp; Johnson&rsquo;s writ of prohibition takes a subtly different track from the issue argued in <i>Barron</i>.&nbsp; In its recent writ, Johnson &amp; Johnson does not argue that Judge Burlison erred in denying the original motion to sever based upon misjoinder of the plaintiffs&rsquo; claims, but that, when the court ordered separate trial of each of the claims, that the claims of each plaintiff should have been formally severed such that venue (and presumably jurisdiction) would be independently assessed as to each of the severed claims.</p> <p style="margin-left: 40px;">Rule 66.02 provides:</p> <p style="margin-left: 80px;">The court, in furtherance of convenience or to avoid prejudice, or when separate trials will be conducive to expedition and economy, may order a separate trial of any claim, cross-claim, counterclaim, or third-party claim, or of any separate issue or of any number of claims, cross-claims, counterclaims, third-party claims, or issues.</p> <p>Rule 52.06 provides that &ldquo;Any claim against a party may be severed and proceeded with separately.&rdquo;&nbsp; Missouri law has been somewhat ambiguous as to the relationship between these rules, including whether &ldquo;proceed[ing] separately&rdquo; with a claim is the same as severing it.</p> <p>The 3-judge concurring opinion in <i>Barron</i>, upon which Johnson &amp; Johnson relies for its writ petition, suggested that, when the trial court determines that a plaintiff&rsquo;s claims should be separately tried, it has effectively &ldquo;severed&rdquo; that plaintiff&rsquo;s claims from the remaining plaintiff(s).&nbsp; Alternatively, where the trial court has determined that the claims should not be tried together, it would ordinarily have no basis to deny a subsequent motion to sever.&nbsp; Because Mo. Rev. Stat. &sect;&nbsp;508.012 (part of the 2005 tort reform) requires reassessment of venue when a plaintiff is either added to or removed from the petition, and mandates transfer if venue is improper, the trial court&rsquo;s failure to formally sever a separately-tried claim deprives defendants of the benefit of the statute.</p> <p>When there has been severance, the normal administrative process would involve the assignment of a new case number to the severed case and, normally, random judicial reassignment.&nbsp; Severance of claims permits the court to render separate judgments which will be deemed final for purposes of appeal.&nbsp; <i>Engel Sheet Metal Equipment, Inc. v. Shewman</i>, 301 S.W.2d 856, 859 (Mo. App. St. L. 1957).&nbsp; The claims, being independent, would be subject to independent venue and jurisdictional analysis, having been unchained from the Missouri anchor plaintiff.</p> <p>It is interesting that the Supreme Court has issued a preliminary writ in the <i>Blaes</i> matter.&nbsp; Although an order for separate trials is not generally deemed to be equivalent to an order for severance, that general principle must be considered in the context of the venue statute, which does contemplate a reassessment of venue.&nbsp; A court may be required to order severance based upon misjoinder, and the Johnson &amp; Johnson argument seems targeted squarely at overcoming the &ldquo;lack of prejudice&rdquo; finding in <i>Barron</i> &ndash; the prejudice is in the denial of the rights afforded under Mo. Rev. Stat. &sect;&nbsp;508.012.&nbsp; Additionally, where the court has discretion to sever based upon judicial economy, fairness, and prejudice, it still appears to be an abuse of discretion to order 47 separate trials but refuse to sever them into independent actions.&nbsp;</p> <p>Johnson &amp; Johnson&rsquo;s writ petition may be the hook to pry loose severance orders in these multi-plaintiff cases.&nbsp; Ideally, however, the impropriety of joinder would be assessed at an earlier stage of the litigation, before decisions on trial management have been made.&nbsp; We are hopeful that recent developments in the talc cases indicates a shift away from recent practices in these multi-plaintiff cases.</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Is It Necessary for an Expert Opinion to Take Into Account Obvious Alternative Explanations for an Injury? Eighth Circuit Weighs In.https://www.bscr-law.com/?t=40&an=67993&format=xml&p=5258&stylesheet=blog07 Aug 2017Drug / Device Law Blog<p>In <i>Redd v. DePuy Orthopaedics, Inc.</i>, the Eighth Circuit Court of Appeals has reminded litigators of the importance of ensuring expert witnesses perform a thorough review of a matter, including apparent alternative causal explanations, prior to issuing their opinions.</p> <p>In 2008, plaintiff Redd underwent a total hip replacement, receiving an implant supplied by hip manufacturer DePuy Orthopaedics, Inc.&nbsp; At the time of her surgery, Redd suffered from a number of risk factors that placed her at a higher risk for failure of the implant as she took immunosuppressant drugs and was considered morbidly obese.&nbsp; Four years after her initial surgery, the implanted hip stem fractured.&nbsp; During the revision surgery to replace the hip stem, the doctors determined that the stem had not properly grown into the bone at the top of Redd&rsquo;s hip, which was a known possibility given her risk factors.&nbsp; Two years after her revision, Redd again experienced a hip stem fracture.&nbsp; Plaintiff brought a federal diversity action against DePuy Orthopaedics, alleging negligence and strict liability claims based on product defect and failure to warn.&nbsp; DePuy moved for summary judgment and for exclusion of plaintiff&rsquo;s expert testimony under Federal Rule of Evidence 702 and the analysis set forth in <i>Daubert v. Merrell Dow Pharmaceuticals, Inc.</i>, 509 U.S. 579 (1993).</p> <p>Plaintiff retained a professor of metallurgy and materials science, Dr. Shankar Sastry, to testify as to the cause of the fracture.&nbsp; In preparing his expert report, Dr. Sastry failed to review records related to the manufacturing process of the hip implant and disregarded consideration of biomechanical factors that could have resulted in failure of the prosthesis.&nbsp; Dr. Sastry concluded that it was the physical state of the implant&rsquo;s metal that caused the fracture.&nbsp; He further concluded that any individual environmental or biomechanical factors would have been a secondary cause of the fracture.</p> <p>In granting DePuy&rsquo;s motion to exclude Dr. Sastry&rsquo;s testimony, the US District Court for the Eastern District of Missouri concluded that Dr. Sastry lacked a scientific or factual basis to conclude that there was a manufacturing defect or to opine on causation, and that he failed to consider the necessary issues of the forces that were exerted on the implant as it was placed in Redd&rsquo;s hip.&nbsp; Following exclusion of Dr. Sastry&rsquo;s testimony, Redd lacked expert testimony on defect or causation and DePuy&rsquo;s motion for summary judgment was granted.</p> <p>On appeal, the Eighth Circuit reviewed the district court&rsquo;s exclusion of Dr. Sastry&rsquo;s testimony, the propriety of which is governed by Rule 702 and the <i>Daubert</i> standard.&nbsp; Plaintiff argued that the district court erred by requiring Dr. Sastry to exclude other potential causes of the fracture.&nbsp; The Eighth Circuit concluded that, while an expert is not required to rule out all possible causes of an injury, he or she nonetheless should adequately account for obvious alternative explanations.&nbsp; Dr. Sastry did not consider the obvious alternative explanation for the fracture&mdash;failure of the hip stem to grow into the patient&rsquo;s upper hip bone and subsequent failure to properly distribute her weight&mdash;which was a known possibility at the time of Redd&rsquo;s surgery given her risk factors.&nbsp; Because Dr. Sastry failed to consider the individual biomechanical forces placed on the prosthesis in issuing his report, the district court&rsquo;s decision to exclude the causation testimony was affirmed.</p> <p>The opinion may be found <a href="http://media.ca8.uscourts.gov/opndir/17/07/163428U.pdf">here</a>.</p> <p>For more on Missouri&rsquo;s recent adoption of the expert witness standard set forth in Federal Rules of Evidence 702 and <i>Daubert</i>, see <i>T<a href="https://www.bscr-law.com/?t=40&amp;an=64345&amp;format=xml&amp;stylesheet=blog&amp;p=5258">he Daubert Standard &ndash; Coming Soon to a Missouri Court Near You</a>.</i></p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10FDA - Postmarket Management of Cybersecurity in Medical Deviceshttps://www.bscr-law.com/?t=40&an=66629&format=xml&p=5258&stylesheet=blog05 Jun 2017Drug / Device Law Blog<p>It seems almost impossible in today&rsquo;s world to escape our dependence on technology. From the minute we wake-up in the morning, we access news reports on our tablets, keep track of our health with fitness trackers, receive and respond to e-mails on our mobile phones, and many of us rely upon interconnected medical devices, such as insulin pumps, to safely navigate through a typical day.&nbsp; But such convenience is not without risk.&nbsp;</p> <p>Medical devices, like all interconnected technology, can be vulnerable to security breaches, which &ldquo;may compromise the essential clinical performance of a device&rdquo; and potentially impact patient safety.&nbsp; The Food and Drug Administration (&ldquo;FDA&rdquo;) thoroughly understands this benefit v. risk balance, and has issued a number of recommendations that address comprehensive cybersecurity over the lifecycle of medical device products.&nbsp; Most recently, on December 27, 2016, the FDA issued its final Guidance on Postmarket Management of Cybersecurity in Medical Devices.&nbsp; The recommendations apply to medical devices that use software, including programmable logic and software that is regulated as a medical device, including mobile medical apps.&nbsp; You can link to the full text of the Guidance <a href="https://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/UCM482022.pdf"><i>here</i></a>.&nbsp; This final Guidance closely resembles a draft of the document, issued for comment almost a year prior.&nbsp; For more details on our take of the draft Guidance, see our prior series &ldquo;FDA Issues Draft Guidance Document for Postmarket Management of Cybersecurity in Medical Devices&rdquo; posted in four parts <a href="https://www.bscr-law.com/?t=40&amp;an=49777&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>, <a href="https://www.bscr-law.com/?t=40&amp;an=49845&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>, <a href="https://www.bscr-law.com/?t=40&amp;an=50038&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>, and <a href="https://www.bscr-law.com/?t=40&amp;an=50131&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>.&nbsp; This Postmarket Guidance also follows the FDA&rsquo;s Guidance on medical device premarket cybersecurity, issued in October 2014, discussed in more detail <a href="https://www.bscr-law.com/?t=40&amp;an=62097&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>.</p> <p>The final Guidance outlines steps that medical device manufacturers and health care systems should take to monitor, identify, understand and address cybersecurity risks once medical devices and mobile medical devices have entered the marketplace.&nbsp; Yet, don&rsquo;t allow the &ldquo;guidance&rdquo; nature of the document fool you into believing its recommendations are optional, as the FDA takes the position that manufacturers are required to ensure the safety and efficacy of their medical devices, and should they choose not to follow this guidance, the device vendor must have in place another similar cybersecurity strategy in order to avoid regulatory scrutiny.</p> <p>From this Guidance emerges two predominant concepts: 1) the Guidance, like its predecessor draft and the 2014 Premarket Guidance, follows a risk-based approach, <i>i.e.</i>, guiding manufacturers to identify, assess, and mitigate risks that emerge after the device has been introduced to market; and 2) medical device cybersecurity and cybersecurity risk management must be proactively addressed throughout the entire lifestyle of a product, and is a shared responsibility among stakeholders including health care facilities, patients, providers, and manufacturers of medical devices.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn1" name="_ftnref1" title="">[1]</a>&nbsp; In other words, cybersecurity controls should be incorporated into the design, development and manufacture of a device.&nbsp; But after marketing and during patient use, the device should be continuously monitored, and cybersecurity concerns addressed.</p> <p>As Suzanne B. Schwartz, the FDA&rsquo;s associate director for science and strategic partnerships, stated in a blog post concurrent with the issuance of the Guidance itself, &ldquo;[w]ith this guidance, we now have an outline of steps the FDA recommends manufacturers take to remain vigilant and continually address the cybersecurity risks of marketed medical devices.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn2" name="_ftnref2" title="">[2]</a>&nbsp; &ldquo;This approach enables manufacturers to focus on continuous quality improvement, which is essential to ensuring the safety and effectiveness of medical devices at all stages in the device&rsquo;s lifecycle.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn3" name="_ftnref3" title="">[3]</a>&nbsp; Essential to the FDA&rsquo;s recommendations is the belief that device manufacturers implement comprehensive cybersecurity risk management programs and documentation which emphasizes &ldquo;addressing vulnerabilities which may permit the unauthorized access, modification, misuse or denial of use, or the unauthorized use of information that is stored, accessed, or transferred from a medical device to an external recipient, and may result in patient harm. Manufacturers should respond in a timely fashion to address identified vulnerabilities.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn4" name="_ftnref4" title="">[4]</a></p> <p>Critical components of such a program include:</p> <ul> <li>Monitoring cybersecurity information sources for identification and detection of cybersecurity vulnerabilities and risk;</li> <li>Maintaining robust software lifecycle processes that include mechanisms for:&nbsp; <ul> <li>monitoring third party software components for new vulnerabilities throughout the device&rsquo;s total product lifecycle;</li> <li>design verification and validation for software updates and patches that are used to remediate vulnerabilities, including those related to Off-the-shelf software;</li> </ul> </li> <li>Understanding, assessing and detecting presence and impact of a vulnerability;</li> <li>Establishing and communicating processes for vulnerability intake and handling</li> <li>Note: The FDA has recognized ISO/IEC 30111:2013: Information Technology &ndash; Security Techniques &ndash; Vulnerability Handling Processes;</li> <li>Using threat modeling to clearly define how to maintain safety and essential performance of a device by developing mitigations that protect, respond and recover from the cybersecurity risk;</li> <li>Adopting a coordinated vulnerability disclosure policy and practice. The FDA has recognized ISO/IEC 29147:2014: Information Technology &ndash; Security Techniques &ndash; Vulnerability Disclosure which may be a useful resource for manufacturers; and</li> <li>Deploying mitigations that address cybersecurity risk early and prior to exploitation.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn5" name="_ftnref5" title="">[5]</a></li> </ul> <p>It is further recommended that the program incorporate elements consistent with the National Institute of Standards and Technology&rsquo;s (NIST) Framework for Improving Critical Infrastructure Cybersecurity (<i>i.e.</i>, Identify, Protect, Detect, Respond, and Recover).&nbsp; For more details on these concepts, please see our previous discussion, which can be found <a href="https://www.bscr-law.com/?t=40&amp;an=50131&amp;format=xml&amp;stylesheet=blog&amp;p=5258"><i>here</i></a>.</p> <p>Perhaps more important than the shared responsibility of risk mitigation in cybersecurity among all stakeholders, is the concept that, in the FDA&rsquo;s view, cybersecurity risk management should revolve around assessing the<em>risk to the device&rsquo;s essential clinical performance, which focuses on assessing the risk of patient harm</em><em>.</em><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn6" name="_ftnref6" title="">[6]</a>&nbsp; As the Guidance explains, &ldquo;[a] key purpose of conducting the cyber-vulnerability risk assessment is to evaluate whether the risk of patient harm is controlled (acceptable) or uncontrolled (unacceptable). One method of assessing the acceptability of risk involves using a matrix with combinations of &ldquo;exploitability&rdquo; and &ldquo;severity of patient harm&rdquo; to determine whether the risk of patient harm is controlled or uncontrolled.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn7" name="_ftnref7" title="">[7]</a>&nbsp; <em>This focus is achieved by considering:</em></p> <p style="margin-left: 40px;">(1)&nbsp;&nbsp; The <b>exploitability </b>of the cybersecurity vulnerability, and</p> <p style="margin-left: 40px;">(2)&nbsp;&nbsp; The <b>severity</b> of patient harm if the vulnerability were to be exploited.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn8" name="_ftnref8" title="">[8]</a></p> <p>Such risk is to be assessed according to these two considerations on a sliding scale, which ranges from a <b><i>controlled risk</i></b> (low probability of a cybersecurity exploit with little impact on patient health) to an <b><i>uncontrolled risk</i></b> (high probability of an exploited vulnerability that seriously threatens patient safety or even patient death).&nbsp; While in some cases the evaluation will yield a definite determination of controlled or uncontrolled, the possibility remains that not all situations will produce such distinct results.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn9" name="_ftnref9" title="">[9]</a></p> <p>The Guidance provides that manufacturers should have processes for assessing the exploitability of a cybersecurity vulnerability as well as the severity of patient harm, if the cybersecurity vulnerability were to be exploited. The FDA suggests using a cybersecurity vulnerability assessment tool or similar scoring system for rating vulnerabilities and determining the need for and urgency of the response, such as the &ldquo;Common Vulnerability Scoring System,&rdquo; Version 3.0.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn10" name="_ftnref10" title="">[10]</a>&nbsp; Many adequate methodologies may be utilized to analyze the potential severity of patient harm, yet the Guidance highlights an approach based on qualitative severity levels as described in ANSI/AAMI/ISO 14971: 2007/(R)2010: Medical Devices &ndash; Application of Risk Management to Medical Devices.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn11" name="_ftnref11" title="">[11]</a>&nbsp; These levels range from Negligible (inconvenience or temporary discomfort) to Catastrophic (resulting in patient death).</p> <p>The figure below shows the relationship between exploitability and severity of patient harm, and can be used to categorize the risk of patient harm as controlled or uncontrolled.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn12" name="_ftnref12" title="">[12]<br /> <br /> <img src="https://www.bscr-law.com/B07AF5/assets/images/Chart.jpg.jpg" hspace="0" vspace="0" align="absmiddle" alt="" border="0" width="600" height="300" /></a>&nbsp;</p> <p>While the FDA clearly distinguishes between a controlled risk and uncontrolled risk, even its illustrative chart above shows a large gray area of <i>in-between</i>, further acknowledging that it will not always be clear in which category the risk belongs.</p> <p>The FDA Guidance then sets forth recommended proper responses to controlled and uncontrolled risks.&nbsp; Controlled risk scenarios involve relatively minor issues, where there is sufficiently low (acceptable) risk of patient harm.&nbsp; However, manufacturers are still encouraged to proactively promote good cyber hygiene and reduce cybersecurity risks even when residual risk is acceptable.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn13" name="_ftnref13" title="">[13]</a>&nbsp; Uncontrolled risks, on the other hand, require immediate intervention and remediation, and must be reported under 21 CFR part 806, unless:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p> <p style="margin-left: 40px;">(1)&nbsp;&nbsp; There are no known serious adverse events or deaths associated with the vulnerability;</p> <p style="margin-left: 40px;">(2)&nbsp;&nbsp; The manufacturer communicates with its customers and user community regarding the vulnerability, identifies interim compensating controls, and develops a remediation plan to bring the risk to an acceptable level, as soon as possible, but no later than 30 days after learning of the vulnerability;</p> <p style="margin-left: 40px;">(3)&nbsp;&nbsp; The manufacturer fixes the vulnerability, validates the change, and distributes the deployable fix to its customers and user community within 60 days; and,</p> <p style="margin-left: 40px;">(4)&nbsp;&nbsp; The manufacturer actively participates as a member of an Information Sharing Analysis Organization or &ldquo;ISAO.&rdquo;<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn14" name="_ftnref14" title="">[14]</a></p> <p>Like its draft before it, the final Guidance additionally contains an essential practical element in its Appendix: &ldquo;Elements of an Effective Postmarket Cybersecurity Program.&rdquo;&nbsp; The Appendix encompasses the totality of the FDA&rsquo;s recommendations, in an easy to follow five-prong framework, consistent with the elements of the NIST Framework for Improving Critical Infrastructure Cybersecurity.&nbsp; These prongs are: A) Identify, B) Protect/Detect, C) Protect/Respond/Recover, and D) Risk Mitigation of Safety and Essential Performance.<a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftn15" name="_ftnref15" title="">[15]</a></p> <p>All medical devices come with both risks and benefits.&nbsp; While it may not always be clear whether a particular risk is categorized as controlled or uncontrolled, the FDA has been explicitly clear in both its Premarket and Postmarket Guidances that comprehensive cybersecurity and risk analysis must be addressed over the lifecycle of medical device products, keeping a primary focus on <em>the </em><em>risk of patient harm</em><em>.</em></p> <div><hr align="left" size="1" width="33%" /> <div id="ftn1"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref1" name="_ftn1" title="">[1]</a> Guidance, at 12.</p> </div> <div id="ftn2"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref2" name="_ftn2" title="">[2]</a> https://blogs.fda.gov/fdavoice/index.php/2016/12/managing-medical-device-cybersecurity-in-the-postmarket-at-the-crossroads-of-cyber-safety-and-advancing-technology/</p> </div> <div id="ftn3"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref3" name="_ftn3" title="">[3]</a> <i>Id</i>.</p> </div> <div id="ftn4"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref4" name="_ftn4" title="">[4]</a> Guidance, at 13.</p> </div> <div id="ftn5"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref5" name="_ftn5" title="">[5]</a> Guidance, at 13-14.</p> </div> <div id="ftn6"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref6" name="_ftn6" title="">[6]</a> Guidance, at 15 (emphasis in original).</p> </div> <div id="ftn7"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref7" name="_ftn7" title="">[7]</a> Guidance, at 17.</p> </div> <div id="ftn8"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref8" name="_ftn8" title="">[8]</a> Guidance, at 15.</p> </div> <div id="ftn9"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref9" name="_ftn9" title="">[9]</a> Guidance, at 17.</p> </div> <div id="ftn10"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref10" name="_ftn10" title="">[10]</a> For more details, <i>see</i> &ldquo;Common Vulnerability Scoring System,&rdquo; Version 3.0: Specification Document (https://www.first.org/cvss/specification-document).</p> </div> <div id="ftn11"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref11" name="_ftn11" title="">[11]</a> Guidance, at 17.</p> </div> <div id="ftn12"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref12" name="_ftn12" title="">[12]</a> Guidance, at 18.</p> </div> <div id="ftn13"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref13" name="_ftn13" title="">[13]</a> Guidance, at 19.</p> </div> <div id="ftn14"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref14" name="_ftn14" title="">[14]</a> Guidance, at 22-23.</p> </div> <div id="ftn15"> <p><a href="file:///C:/Users/LJR/Desktop/DRAFT%20Blog.docx#_ftnref15" name="_ftn15" title="">[15]</a> Guidance, at 27-30.</p> </div> </div>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Federal Judge Clobbers Claims in a Class III Medical Device Casehttps://www.bscr-law.com/?t=40&an=66131&format=xml&p=5258&stylesheet=blog22 May 2017Drug / Device Law Blog<p>Talk about a one-two punch. First, federal question jurisdiction kept a medical device case in federal court.&nbsp; And then came the knock-out blow: a federal judge in North Carolina ruled that federal preemption barred all of the state law claims against the medical device companies.&nbsp; In <i>Burrell v. Bayer Corp., </i>U.S Dist. LEXIS 38769 (W.D. N.C. March 17, 2017) (<i>Burrell I)</i>, Judge Max O. Cogburn, Jr. retained jurisdiction over the medical device related lawsuit based on federal question jurisdiction.&nbsp; In a subsequent order, Judge Cogburn granted Bayer&rsquo;s motion to dismiss plaintiff&rsquo;s claims because federal law preempts those claims.&nbsp; <i>Burrell v. Bayer Corp., </i>U.S Dist. LEXIS 71374 (W.D. N.C. May 10, 2017) (<i>Burrell II).&nbsp; </i></p> <p>The plaintiff in <i>Burrell</i> alleged she was injured as a result of her use of an Essure birth control device.&nbsp; The Essure device is a Class III medical device approved by the FDA through the pre-market approval process.&nbsp; Plaintiff sued various Bayer entities, as well as local doctors for malpractice to defeat diversity jurisdiction.&nbsp; Bayer removed the case to federal court arguing it belonged there because of federal question jurisdiction.&nbsp; As evidenced by the inclusion of local defendants in her Complaint, plaintiff did not want the case in federal court and, thus, filed a motion to remand.</p> <p>But the plaintiff&rsquo;s Complaint was &ldquo;replete with references to the FDA&rdquo; and included numerous allegations &ldquo;that the defendants violated the federal requirements of the Federal Food, Drug &amp; Cosmetic Act (FDCA).&rdquo;&nbsp; <i>Burrell I</i>, at *4-5.&nbsp; Because plaintiff&rsquo;s Complaint &ldquo;necessarily raise[d] federal issues,&rdquo; Judge Cogburn concluded it was &ldquo;properly a case that &lsquo;arises from&rsquo; federal law, as the MDA was passed by Congress to govern the safety and effectiveness of Class III medical devices.&rdquo;&nbsp; <i>Id. </i>at *11.&nbsp; He therefore retained jurisdiction over the case and denied plaintiff&rsquo;s motion to remand.&nbsp; <i>Id. </i></p> <p>Just under two months later, Judge Cogburn delivered the knockout punch by granting Bayer&rsquo;s motion to dismiss.&nbsp; Before delivering the decisive blow, though, Judge Cogburn had to block plaintiff&rsquo;s counter punch &ndash; a motion to reconsider the remand denial order.&nbsp; In <i>Burrell II, </i>plaintiff tried again to convince Judge Cogburn that he should remand the case to state court.&nbsp; Judge Cogburn had no trouble crushing plaintiff&rsquo;s reconsideration attack.&nbsp; For her reconsideration argument, the plaintiff relied on a 2005 Fourth Circuit case for the proposition that:</p> <p style="margin-left: 40px;">&ldquo;[A] preemption&nbsp;defense that raises a federal question is inadequate to confer federal jurisdiction. Again, a case may not be removed to federal court on the basis of a federal defense, including the defense of preemption,&quot; even if the complaint begs the assertion of the defense, and even if the defense is the only question truly at issue in the case.</p> <p><i>Burrell II, </i>at *8-9 quoting <i>Pinney v. Nokia, Inc.</i>, 402 F.3d 430, 446 (4<sup>th</sup> Cir. 2005).</p> <p>But Judge Cogburn easily rebuffed the reconsideration wrangle by distinguishing <i>Burrell</i> from <i>Pinney. </i>While federal law &ldquo;was &lsquo;lurking&rsquo; as a question in the background&rdquo; in <i>Pinney</i>, in <i>Burrell II, </i>&ldquo;[b]y plaintiff&rsquo;s own admission,&rdquo; she alleged violations of the FDCA as part of her state law claims and thus her Complaint met the requirements for federal jurisdiction.&nbsp; Motion for reconsideration denied.</p> <p>After successfully deflecting plaintiff&rsquo;s reconsideration left hook, Judge Cogburn led with a little jab about preemption.&nbsp; Usually, when a judge begins a preemption discussion by noting that &ldquo;Federal law generally recognizes a presumption against preemption,&rdquo; the defendant can expect a body blow at the end of the discussion.&nbsp; Thankfully, that was not what happened in <i>Burrell II.&nbsp; </i>Instead, Judge Cogburn followed the jab with the express and implied preemption combination by noting that &ldquo;the task of avoiding express and implied preemption is a difficult one.&rdquo;&nbsp; <i>Burrell II.&nbsp; </i>He then thoroughly analyzed plaintiff&rsquo;s claims and concluded federal law preempted all of the claims against the Bayer defendants.</p> <p><b><u>Negligent Failure to Warn Claims</u></b></p> <p>Plaintiff alleged the Bayer defendants were negligent by failing to warn of adverse events relating to Essure and that they &ldquo;were under a continuing duty to comply with requirements&rdquo; in the FDA&rsquo;s pre-market approval of Essure.&nbsp; On this point, the court agreed with the plaintiff. <i>Burrell II</i> at *12. But that agreement also meant federal law preempted plaintiff&rsquo;s negligence claims because &ldquo;plaintiff&rsquo;s cause of action is being brought because the Bayer defendants allegedly failed to meet those reporting requirements.&rdquo;&nbsp; <i>Id. </i>at *12-13.</p> <p>To insure the negligent failure to warn claims remained knocked out, as an added bonus, Judge Cogburn also ruled that &ldquo;plaintiff cannot support a finding of causation&rdquo; for those warnings claims.&nbsp; <i>Id. </i>at * 13.&nbsp; Judge Cogburn explained that by the time the plaintiff in <i>Burrell</i> received her device, &ldquo;the FDA had the related information regarding the adverse event reports mentioned by plaintiff.&rdquo;&nbsp; <i>Id. </i>Thus, in addition to being a preempted claim, Judge Cogburn found that plaintiff &ldquo;failed to show that the failure-to-warn caused her injuries.&rdquo;&nbsp; <i>Id.</i></p> <p><b><u>Negligent Failure to Train Claims</u></b></p> <p>In addition to her negligent failure-to-warn claims, plaintiff also asserted claims that the Bayer Defendants failed to train the implanting physician about how &ldquo;to implant the device, deal with potential complications, and remove the device.&rdquo; <i>Id. </i>at *14.&nbsp; Judge Cogburn quickly dispensed with plaintiff&rsquo;s failure-to-train combination.&nbsp; Federal law preempted plaintiff&rsquo;s negligent training claim because plaintiff&rsquo;s claim &ldquo;imposes a duty that is beyond the confines of the MDA.&rdquo; <i>Id.</i>&nbsp; But on the downside, Judge Cogburn noted that such a claim could survive a preemption attack &ldquo;to the extent that the manufacturer failed to provide the training required by the MDA.&rdquo;&nbsp; <i>Id.</i> &nbsp;However, plaintiff&rsquo;s Complaint did &ldquo;not provide information as to how the training violated the FDA&rsquo;s requirements or how her physician was trained.&rdquo;&nbsp; <i>Id. </i>at *14-15.&nbsp; Due to lack of information on that point, federal law preempted the claim.</p> <p>As with the negligent warning claims, Judge Cogburn also found plaintiff failed to provide sufficient facts to establish that any training failure caused her injuries.&nbsp; Thus, in addition to being preempted, the negligent training claims failed for lack of causation.</p> <p><b><u>Manufacturing Defect Claims</u></b></p> <p>Judge Cogburn also knocked aside plaintiff&rsquo;s weak attempt at throwing a manufacturing defect punch.&nbsp; Although the plaintiff alleged her Essure was &ldquo;manufactured improperly,&rdquo; she did not link &ldquo;any manufacturing deficiency to the device that [she] received and how it caused the alleged injuries.&rdquo;&nbsp; <i>Id. </i>at *16.&nbsp; Thus, her manufacturing defect claim failed.</p> <p><b><u>Design Defect Claim</u></b></p> <p>Judge Cogburn parried plaintiff&rsquo;s product liability claim as well. To the extent plaintiff argued that Essure suffered from a design defect, federal law expressly preempted those claims.&nbsp; In brushing aside the design defect claim, Judge Cogburn simply noted that &ldquo;The FDA made its determination [about the] safety and effectiveness&rdquo; of the Essure and therefore &ldquo;these design defect claims are preempted.&rdquo;&nbsp; <i>Id. </i>at 17.</p> <p><b><u>Breach of Warranty Claims </u></b></p> <p>Judge Cogburn blasted the breach of warranty claims.&nbsp; The plaintiff alleged the Bayer defendants &ldquo;expressly warranted Essure to be safe for use by the general public, including Plaintiff&rdquo; and that the &ldquo;warranties and representations &lsquo;were untrue in that Essure was unsafe and unsuited for the use for which it was intended.&rsquo;&rdquo; <i>Id.</i> at *18.&nbsp; In short, Judge Cogburn noted that &ldquo;Congress provided the FDA with the authority to regulate the safety and effectiveness of Class III medical devices.&rdquo;&nbsp; So, he dismissed the breach of warranty claims.</p> <p><b><u>Fraud and Unfair Trade Practices Claims</u></b></p> <p>Finally, with all other claims against Bayer flat on the mat, Judge Cogburn crushed plaintiff&rsquo;s unfair and deceptive trade practices claims.&nbsp; Judge Cogburn noted that the &ldquo;allegations largely repackage the allegations&rdquo; he already dismissed and that &ldquo;several of the alleged misrepresentations are indistinguishable from FDA-approved labeling statements.&rdquo;&nbsp; <i>Id. </i>at *19-20.&nbsp; Plaintiff&rsquo;s allegations of &ldquo;deviations from the FDA-approved language&rdquo; were insufficient to &ldquo;support a claim based on fraudulent behavior or unfair trade practices.&rdquo;&nbsp; <i>Id. </i>at *20.&nbsp; Federal law preempted those claims.</p> <p><b><u>Medical Malpractice Claims</u></b></p> <p>After knocking out all of the plaintiff&rsquo;s claims against the Bayer defendants, Judge Cogburn came full circle and turned his attention to the medical malpractice claims against the local defendants.&nbsp; Plaintiff eventually got her wish &ndash; the case will not remain in federal court.&nbsp; Judge Cogburn declined to exercise supplemental jurisdiction over the medical malpractice claims and dismissed those claims pursuant to 28 U.S.C. &sect; 1367(c)(3) so plaintiff could reassert those claims in state court.</p> <p><b><u>Post Bout Summary</u></b></p> <p>Under <i>Riegel v. Medtronic, Inc., </i>552 U.S. 313, 128 S. Ct. 999 (2008), plaintiffs in Class III medical device cases have a &ldquo;narrow window&rdquo; through which they must plead when attempting to state &ldquo;parallel claims.&rdquo;&nbsp; Judge Cogburn&rsquo;s orders in this case provide great training roadmaps for knocking out claims in Class III medical device cases when plaintiffs allege violations of the FDCA or FDA regulations.&nbsp; Bayer used a great combination of federal question jurisdiction and preemption arguments to flatten plaintiff&rsquo;s claims in this Class III medical device case.&nbsp; Bayer made the arguments, and Judge Cogburn delivered the epic knockout.</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10Indiana Judge Relies on Bausch to Bounce Preemption Motionhttps://www.bscr-law.com/?t=40&an=65551&format=xml&p=5258&stylesheet=blog15 May 2017Drug / Device Law Blog<p>The old adage &ldquo;location, location, location&rdquo; applies as much for medical device preemption as it does for real estate. Despite acknowledging that the plaintiff&rsquo;s Amended Complaint &ldquo;would likely not survive a motion to dismiss if this case was pending in a court in the Eighth Circuit (or perhaps the Eastern District of New York),&rdquo; an Indiana federal judge recently denied Medtronic&rsquo;s motion to dismiss the Amended Complaint in <i>Cavender v. Medtronic, Inc. (Cavender II), </i>2017 U.S. Dist. LEXIS 57376 (N.D. Ind. Apr. 14, 2017).&nbsp;</p> <p>As frequently happens in cases involving pre-market approved medical devices, the court dismissed the initial complaint.&nbsp; He dismissed the initial Complaint because it was &ldquo;nothing more than the sort of &ldquo;unadorned, the-defendant-unlawfully-harmed-me accusation&rdquo; and was &ldquo;still in the &lsquo;assembly required&rsquo; stage.&rdquo; <i>Cavender v. Medtronic, Inc. (Cavender I), </i>2016 U.S. Dist. LEXIS 154540 *20-21 (N.D. Ind. Nov. 8, 2016).&nbsp; But, just as many other courts do, the judge in this case, Judge William C. Lee, granted the motion to dismiss <b>without prejudice</b> and gave the plaintiff another chance to try to plead a valid claim.</p> <p>In <i>Cavender I, </i>the plaintiff alleged that her implantable cardioverter defibrillator malfunctioned and injured her.&nbsp; She filed her initial complaint &ldquo;apparently asserting product liability, breach of warranty and negligence claims against Medtronic.&rdquo;&nbsp; <i>Cavender I</i>, at *2.&nbsp; Judge Lee&rsquo;s first task in <i>Cavender I</i> was to determine whether the Indiana Product Liability Act (IPLA) preempted and subsumed plaintiff&rsquo;s attempted product liability claims.&nbsp; Judge Lee concluded that the IPLA subsumed the negligence and product defect claims.&nbsp;</p> <p>However, plaintiff&rsquo;s complaint lacked specifics and was &ldquo;nothing more than the sort of &lsquo;unadorned, the-defendant-unlawfully-harmed-me accusation&rsquo;&rdquo; which was &ldquo;chock-full of keywords that imply&rdquo; that the plaintiff was &ldquo;attempting to assert various product liability claims.&rdquo; <i>Id. </i>at *20. &nbsp;Because the plaintiff&rsquo;s complaint &ldquo;need[ed] work&rdquo; and was &ldquo;still in the &lsquo;assembly required&rsquo; stage,&rdquo; Judge Lee gave plaintiff another chance to plead valid claims.&nbsp; <i>Id.</i> at *21-22 and 37.&nbsp;</p> <p>In his order in <i>Cavender I, </i>Judge Lee offered guidance for what plaintiff needed to do to plead valid claims.&nbsp; For example, in response to Medtronic&rsquo;s argument that federal law preempts plaintiff&rsquo;s claims, Judge Lee noted that the Complaint &ldquo;is completely devoid of any facts whatsoever that would even <i>imply</i> that she is alleging a violation of federal law.&rdquo;&nbsp; <i>Id. </i>at *28.&nbsp; Judge Lee advised the plaintiff that the &ldquo;amended complaint will clarify this issue also.&rdquo;&nbsp; <i>Id. </i>at 29.</p> <p>Rather than directly clarifying the issue as instructed by Judge Lee, in the Amended Complaint, the plaintiff switched which device she was claiming caused her injury.&nbsp; In the initial Complaint, she vaguely alleged that a defibrillator malfunctioned and injured her.&nbsp; <i>Id. </i>at *2.&nbsp; In the Amended Complaint, she copied allegations from the Master Consolidated Complaint in the <i>Sprint Fidelis Leads Prods. Liab. Litig. </i>MDL and alleged a separate device, a Sprint Fidelis lead, caused her injuries.&nbsp;&nbsp;</p> <p>Plaintiff copied the allegations from the <i>Sprint Fidelis Leads Prods. Liab. Litig.</i> MDL even though the MDL judge dismissed those claims <b>with prejudice</b> at the pleading stage. <i>See</i> <i>In re Medtronic, Inc. Sprint Fidelis Leads Prods. Liab. Litig., </i>592 F.Supp.2 1147 (D. Minn. 2009) (dismissing the Master Complaint because federal law preempted the negligence and strict liability claims) <i>aff&rsquo;d</i> <i>Bryant v. Medtronic, Inc. (In re: Medtronic, Inc., Sprint Fidelis Leads Prods. Liab. Litig, </i>623 F.3d 1200 (8<sup>th</sup> Cir. 2010).&nbsp;</p> <p>By copying the preexisting and previously dismissed complaint, the plaintiff added more detail than in her initial complaint.&nbsp; Judge Lee noted that:</p> <p style="margin-left: 40px;">[W]hile the claims contained in her original Complaint were barely discernible, they now jump vividly off the page in full regalia, all because they are clothed in language taken&mdash;largely verbatim&mdash;from another complaintfiled against Medtronic that was summarily dismissed by another district court eight years ago. <i>Id. </i>at *8-9.</p> <p>Despite the product switcheroo and the blatant copying of a previously dismissed complaint, in <i>Cavender II, </i>Judge Lee concluded that the Seventh Circuit&rsquo;s decision in <i>Bausch v. Stryker Corp., </i>630 F.3d 546 (7<sup>th</sup> Cir. 2010), &ldquo;precludes dismissal of Cavender&rsquo;s IPLA claim at this point and the motion to dismiss must be denied as to the issue of federal preemption of that claim.&rdquo;&nbsp; <i>Cavender </i>at *33.&nbsp;</p> <p>Judge Lee noted that the Seventh Circuit in <i>Bausch</i> agreed with the dissent in the Eighth&rsquo;s Circuit&rsquo;s decision affirming the dismissal of the Master Complaint in the <i>Sprint Fidelis Leads Prods. Liab. Litig.</i> MDL. In short, &ldquo;the Seventh Circuit took a decidedly different approach to the issue of MDA preemption as it applies to state law claims.&rdquo;&nbsp; <i>Cavender II</i> at *26-27.&nbsp; Thus, according to Judge Lee, &ldquo;the <a href="https://advance.lexis.com/api/document?collection=cases&amp;id=urn:contentItem:51SF-JNJ1-F04K-R0C1-00000-00&amp;context="><i>Bausch</i></a> decision mandates that [plaintiff] be permitted, at this juncture, to proceed with that claim notwithstanding the preemption clause in the MDA.&rdquo; <i>Id. </i>at *38.</p> <p>One other aspect of Judge Lee&rsquo;s order is noteworthy.&nbsp; The plaintiff argued that because preemption is an affirmative defense, that she should not have to &quot;defend&quot; against an affirmative defense at this stage, thus the Court should not consider the defense as a basis for dismissal.&rdquo;&nbsp; <i>Id. </i>at n.5 *21.&nbsp; Medtronic did not take issue with &ldquo;that statement of the law&rdquo; and Judge Lee declared that plaintiff was &ldquo;correct, of course.&rdquo;&nbsp; <i>Id. </i>Rather than take issue with the statement of law, Medtronic argued that because the plaintiff copied and pasted the very detailed, dismissed MDL complaint relating to this Lead[,]&quot; she has, &quot;[u]nder Seventh Circuit law . . . pled enough facts for the Court to consider the affirmative defense of preemption.&quot;&nbsp; <i>Id.</i> Because Judge Lee concluded that the <i>Bausch </i>decision precluded preemption at the pleading stage in this case, he determined that the issue was &ldquo;rendered irrelevant.&rdquo;&nbsp; <i>Id.</i>&nbsp;</p> <p>Judge Lee&rsquo;s order is yet another example of how the <i>Bausch</i> decision continues to cause problems for medical device makers at the motion to dismiss phase in cases in the Seventh Circuit.&nbsp; The plaintiff in <i>Cavender II</i> simply copied allegations the Eighth Circuit had already dismissed as preempted.&nbsp; But because of the overly permissive language of <i>Bausch,</i> those same claims survive the motion to dismiss in the Seventh Circuit.&nbsp; Medtronic&rsquo;s preemption argument may very well prevail at the summary judgment stage, but only after spending on unnecessary litigation expenses.</p>https://www.bscr-law.com?t=39&anc=367&format=xml&directive=0&stylesheet=rss&records=10