throbber
Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 1 of 10
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF MASSACHUSETTS
`
`TEVA PHARMACEUTICALS
`INTERNATIONAL GMBH and
`TEVA PHARMACEUTICALS USA, INC.,
`
`Plaintiffs,
`
`v.
`
`ELI LILLY AND COMPANY,
`
`Defendant.
`
`FILED UNDER SEAL
`LEAVE TO FILE GRANTED
`9/18/2021 (ECF NO. 160)
`
`)
`) Case No. 1:18-cv-12029-ADB
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`
`DEFENDANT ELI LILLY AND COMPANY’S SUR-REPLY TO PLAINTIFFS’
`MOTION FOR SANCTIONS PURSUANT TO FED. R. CIV. P. 37(B)
`
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 2 of 10
`
`TABLE OF CONTENTS
`Introduction ......................................................................................................................... 1
`
`The Requirement That Lilly Violated a Court Order Is Not Met ....................................... 1
`
`A.
`
`B.
`
`The Court Ordered Lilly to Search “Code Names Used By Lilly” ............. 1
`
`Teva Cannot Rewrite the Court’s Order, or the Underlying Facts ............. 2
`
`1.
`
`2.
`
`
`“Teva’s Interpretation” of the Court’s Order Is Irrelevant ......................... 2
`
`Teva’s Attempts to Muddy the Record Do Not Change That Lilly
`Acted in Good Faith .................................................................................... 3
`
`
`
`I.
`
`II.
`
`
`
`III.
`
`Teva’s Sanctions Analysis Is Contrary to Law and Fact .................................................... 4
`
`A.
`
`B.
`
`Teva Has No Answer to Governing Case Law ........................................... 4
`
`The Facts Do Not Warrant Any of Teva’s Proposed Sanctions ................. 4
`
`IV.
`
`Conclusion .......................................................................................................................... 5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 3 of 10
`
`
`
`
`
`Federal Cases
`
`TABLE OF AUTHORITIES
`
`Ins. Recovery Grp., Inc. v. Connolly,
`977 F. Supp. 2d 16 (D. Mass. 2013) ..........................................................................................2
`
`Lawes v. CSA Architects and Eng’rs LLP,
`963 F.3d 72 (1st Cir. 2020) ........................................................................................................5
`
`Pascale v. G.D. Searle & Co.,
`90 F.R.D. 55 (D.R.I. 1981) ........................................................................................................2
`
`R.W. Int’l Corp. v. Welch Foods, Inc.,
`937 F.2d 11 (1st Cir. 1991) ........................................................................................................4
`
`Syntel Sterling Best Shores Mauritius Ltd. v. TriZetto Grp.,
`328 F.R.D. 100 (S.D.N.Y. 2018) ...............................................................................................4
`
`Federal Statutes
`
`35 U.S.C. § 112 ................................................................................................................................4
`
`Rules
`
`Fed. R. Civ. P. 37(b) ....................................................................................................................1, 4
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 4 of 10
`
`
`
`I.
`
`Introduction
`
`At best, Teva’s sanctions motion reflects a good faith dispute between the parties over the
`
`scope of the Court’s March 8th Order. That dispute is not sanctionable. At worst, Teva’s
`
`sanctions motion is an attempt to circumvent this Court and a Massachusetts jury by removing
`
`causes of action from the case without ever addressing substance. Regardless, Teva’s reply (ECF
`
`No. 161)—rife with vitriol and speculation—comes no closer than its opening brief to carrying
`
`its heavy burden to prove that its requested Rule 37(b) sanctions are warranted. Instead, Teva’s
`
`reply tries to muddy the waters while ignoring the case law in Lilly’s opposition (ECF No. 151)
`
`that is solidly in Lilly’s favor. Teva’s motion should be denied.
`
`II.
`
`
`The Requirement That Lilly Violated a Court Order Is Not Met
`
`Lilly believes that the March 8th Order was clear: “[P]erform a search using the phrase
`
`“galca,” as described in Teva’s letter/request.” ECF No. 104. Lilly ran a search “as described in
`
`Teva’s letter/request,” namely, Search Term 1 on page 1 of Teva’s letter, right below the phrase
`
`“Teva seeks an order compelling Lilly to use the following two search terms[.]” ECF No. 99
`
`(“Teva’s letter”) at 1. Search Term 1 required Lilly to search for “any internal project of [sic]
`
`code names used by Lilly.” Id. The Court did not order Lilly to run a search containing the terms
`
` which are not internal project or code names used by Lilly,
`
`and Teva did not seek such an order in February 2021. That Teva sought to recast the March 8th
`
`Order to manufacture the present dispute in late July, five months later, has no bearing on Lilly’s
`
`compliance with the Court’s March 8th Order.
`
`A.
`
`The Court Ordered Lilly to Search “Code Names Used By Lilly”
`
`There is no dispute that Lilly promptly produced more than 14,000 documents responsive
`
`to “Search Term 1” that the Court ordered. Lilly ran thirteen code names for the project that later
`
`led to galcanezumab, comprising “galca*,” the seven terms expressly listed in the search string
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 5 of 10
`
`
`
`from Teva’s letter, and five additional project or code names not identified by
`
`
`
` Teva’s reply again insists that other code names
`
`were “used by Lilly” and thus Lilly was bound by the Court’s Order to run those names. But this
`
`self-serving and unsupported speculation is inconsistent with the deposition testimony elicited by
`
`Teva. Indeed, Lilly’s scientists repeatedly testified what the project code name actually was:
`
` See ECF No. 151 at 9. Generic terms like “drug,” “CGRP,” “antibody,” or even
`
` that might appear as nouns in some text relating to the project are not specific
`
`to the project and were entirely unsuited for use as a confidential code name. Acknowledging the
`
`possibility of “colloquial” use of such terms does not convert those words into project or code
`
`names. In the face of this clear testimony, Teva alternately claims that Lilly “agreed” to run the
`
`disputed
`
` and
`
` terms (Lilly did not), that Lilly “did not object” to
`
`running them (again, false), or that Lilly has “waived” arguments against imposing sanctions
`
`because it should have known Teva’s position “in February.” Lilly could not have waived in
`
`February an argument Teva did not raise until July 30, 2021.
`
`B.
`
`Teva Cannot Rewrite the Court’s Order, or the Underlying Facts
`1.
`
`“Teva’s Interpretation” of the Court’s Order Is Irrelevant
`
`Teva’s briefs rest on the premise that Teva can redefine the scope of a Court order. But if
`
`
`
`there is ambiguity in the scope of the order Teva secured, that ambiguity should be construed
`
`against Teva, not Lilly. See, e.g., Ins. Recovery Grp., Inc. v. Connolly, 977 F. Supp. 2d 16, 26 (D.
`
`Mass. 2013) (“Courts have found unjust the imposition of sanctions on the basis of the violation
`
`of a discovery order that is subject to more than one reasonable interpretation.”) (citing Pascale
`
`v. G.D. Searle & Co., 90 F.R.D. 55, 59 (D.R.I. 1981)). If Teva wanted the specific terms
`
`
`
` to be run in a search term ordered by the Court, all it had to do was
`
`expressly list them in the requested search string, as Teva did with eight other names for Lilly’s
`2
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 6 of 10
`
`
`
`antibody project. ECF No. 99 at 1. Lilly would have run those terms, if ordered. In the absence
`
`of that clarity, Teva’s reply simply states ipse dixit that “there cannot be any meaningful dispute”
`
`that the Court’s March 8th Order adopted and incorporated the entirety of Teva’s February 18th
`
`six-page letter request—and accordingly, “Teva’s interpretation” and “Teva’s position” govern
`
`Lilly’s compliance with the Order.1 But the briefing on this issue makes clear that there is a
`
`meaningful dispute with Teva and Lilly having diametrically opposite interpretations.
`
`2.
`Teva’s Attempts to Muddy the Record Do Not Change That Lilly
` Acted in Good Faith
`
`
`Teva’s reply is replete with overheated rhetoric seemingly calculated to justify an
`
`unearned summary judgment victory. At various times, Teva wrongly accuses Lilly of
`
`“resort[ing] to indefensible falsehoods,” “continued use of deception,” and a “willingness to
`
`misrepresent the facts.” ECF No. 161 at 5-6. As previously explained, that is simply not the
`
`case—Lilly believed it was complying with the Court’s March 8th Order. ECF No. 151 at 11-16.
`
`Lilly’s confirmation that it ran the iterations of the ‘code’ names identified in Teva’s June 30
`
`email, which Teva references in its reply (ECF No. 161 at 5), supports that Lilly did not
`
`understand
`
` to be a code name or a term ordered by the Court.
`
`Teva claims in its reply that it “explicitly stated its intent to bring a sanctions motion and
`
`the parties discussed that issue at length.” ECF No. 161 at 5; ECF No. 162 at ¶¶3-4. Teva claims
`
`Lilly ratified this by noting in a post-conference email that Teva stated that it “could” seek
`
`sanctions. But Teva did not “state its intent” to bring a sanctions motion on July 30th. Gabranski
`
`Decl. at ¶¶2-4. Moreover, the parties could not have been at an impasse justifying this motion on
`
`
`1 Even the footnote in Teva’s letter brief now relied on by Teva only stated that certain
`documents “indicate” that
` were project names used by Lilly.
`ECF No. 99 at 3 n.3. Subsequent deposition testimony confirmed that they were not. See ECF
`No. 151 at 9.
`
`3
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 7 of 10
`
`
`
`July 30th, as that was the first time that Teva argued that Lilly had violated the Court’s Order by
`
`not running
`
` as search terms. Indeed, as Teva’s motion
`
`states, the parties continued to discuss the issue in various emails between August 5-16, 2021.
`
`None of those emails, however, stated that Teva was filing a Rule 37(b) sanctions motion, even
`
`the August 15, 2021 email seeking Lilly’s assent to Teva’s motion to seal for the same motion.
`
`ECF Nos. 152-14 to 152-16. While two Teva attorneys have now sworn to the Court that Teva
`
`adequately advised Lilly of this motion, the facts instead support Lilly’s contrary perception.
`
`III. Teva’s Sanctions Analysis Is Contrary to Law and Fact
`A.
`
`Teva Has No Answer to Governing Case Law
`
`Teva’s reply fails to address the array of governing case law from the First Circuit and
`
`this District cited in Lilly’s Opposition. Those factors, which favor Lilly, cannot be ignored. And
`
`the First Circuit is clear that when a party is accused of violating a court order on the scope of
`
`document production, the proper sanction is an order to produce documents, not to end the case
`
`or important issues in it. R.W. Int’l Corp. v. Welch Foods, Inc., 937 F.2d 11, 17 (1st Cir. 1991).
`
`Teva’s reply does not mention, let alone analyze, any of the cases Lilly presented. Even Teva’s
`
`out-of-circuit Syntel case argues against Teva’s overreach. The New York district court found
`
`that defendant’s proposed sanctions of “findings of fact, preclusion, or adverse inferences” were
`
`“not commensurate with the failure to comply.” Syntel Sterling Best Shores Mauritius Ltd. v.
`
`TriZetto Grp., 328 F.R.D. 100, 123 (S.D.N.Y. 2018). The court further found that the sanctions
`
`sought were not “congruous with the misconduct at issue.” Id. The facts here are even more
`
`stark. Lilly has produced over 14,000 documents directly responsive to Search Term 1.
`
`B.
`
`The Facts Do Not Warrant Any of Teva’s Proposed Sanctions
`
`Teva argues that precluding Lilly from arguing its 35 U.S.C. ¶ 112 and doctrine of
`
`equivalents defenses is warranted because the understanding of “Lilly’s scientists” “could have a
`
`4
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 8 of 10
`
`
`
`significant bearing” on both issues. ECF No. 161 at 9-10. But Teva deposed each of those
`
`scientists for a full day on the record, has thousands of documents from those scientists’ files,
`
`and presumably will present expert testimony on those issues. That some other theoretical
`
`document “could” exist that might contradict others is a fishing expedition, not a reason for
`
`terminating sanctions. Teva also assumes, without evidence, that Lilly is withholding documents
`
`that hit on the terms
`
` because they “likely are” “highly
`
`relevant.” Id. at 9. But this is pure conjecture and plainly false. Lilly did not, as Teva contends,
`
`base its decision regarding
`
` on a desire to withhold “highly
`
`responsive” or conceal “unfavorable” documents. To the contrary, and consistent with Lilly’s
`
`position, Lilly did not run these searches before or in response to the Court’s March 8th Order
`
`because it did not understand the Order to require that. Gabranski Decl. at ¶¶5-7. Throughout this
`
`litigation, Lilly has engaged in good faith negotiations on discovery with Teva—producing
`
`additional documents at Teva’s request from Lilly custodians
`
`
`
` as well as from non-custodial sources. In the context of this recent dispute on the
`
`terms
`
` Lilly was trying to do the same, and queried Teva for
`
`“specific documents or categories of documents it has not received.” ECF No. 151-14 at 1. But
`
`Teva ignored this query and instead responded with a sanctions motion.
`
`Teva should not be permitted to sidestep major weaknesses in its case through unjust
`
`imposition of unwarranted sanctions. Instead, Lilly respectfully requests that the Court honor and
`
`enforce the First Circuit’s “strong policy favoring the disposition of cases on the merits,” and
`
`allow Lilly to present its defenses unencumbered by Teva’s attempted circumvention. Lawes v.
`
`CSA Architects and Eng’rs LLP, 963 F.3d 72, 91 (1st Cir. 2020) (quotation omitted).
`
`IV. Conclusion
`
`
`
`For the reasons above and of record, Teva’s motion should be denied.
`5
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 9 of 10
`
`
`
`
`
`Dated: September 23, 2021
`
`
`
`
`
`
`
`William B. Raich
`Danielle A. Duszczyszyn
`Denise Main
`Pier D. DeRoo
`Daniel F. Roland
`Matthew Luneack
`Yoonjin Lee
`Amana Abdulwakeel
`FINNEGAN, HENDERSON, FARABOW,
`GARRETT & DUNNER, LLP
`901 New York Avenue, NW
`Washington, DC 20001-4413
`William.Raich@finnegan.com
`Danielle.Duszczyszyn@finnegan.com
`Denise.Main@finnegan.com
`Pier.DeRoo@finnegan.com
`Daniel.Roland@finnegan.com
`Matthew.Luneack@finnegan.com
`Yoonjin.Lee@finnegan.com
`Amana.Abdulwakeel@finnegan.com
`
`
`
`
`
`
`
` /s/ Andrea L. Martin
`Andrea L. Martin (BBO 666117)
`BURNS & LEVINSON LLP
`125 High Street
`Boston, MA 02110-1624
`(617) 345-3000
`amartin@burnslev.com
`
`Charles E. Lipsey
`Ryan O’Quinn
`FINNEGAN, HENDERSON, FARABOW,
`GARRETT & DUNNER, LLP
`1875 Explorer Street
`Suite 800
`Reston, VA 20190-6023
`Charles.Lipsey@finnegan.com
`Oquinnr@finnegan.com
`
`Emily R. Gabranski (BBO 694417)
`Marta Garcia Daneshvar
`Lulu Wang (BBO 704042)
`FINNEGAN, HENDERSON, FARABOW,
`GARRETT & DUNNER, LLP
`2 Seaport Lane
`Boston, MA 02210-2001
`Emily.Gabranski@finnegan.com
`Marta.Garcia@finnegan.com
`Lulu.Wang@finnegan.com
`
`Attorneys for Defendant
`Eli Lilly and Company
`
`6
`
`
`
`
`
`
`

`

`Case 1:18-cv-12029-ADB Document 172 Filed 10/04/21 Page 10 of 10
`
`
`
`CERTIFICATE OF SERVICE
`
`I, Andrea L. Martin, hereby certify that on September 23, 2021, a copy of the foregoing
`document was served on all outside counsel of record via email.
`
`
`
`
`
`/s/ Andrea L. Martin
`Andrea L. Martin
`
`
`
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket