{"id":3857,"date":"2024-06-17T15:05:37","date_gmt":"2024-06-17T20:05:37","guid":{"rendered":"https:\/\/patents.harnessip.com\/?p=3857"},"modified":"2024-07-07T11:26:56","modified_gmt":"2024-07-07T16:26:56","slug":"plaintiff-failed-to-show-it-was-entitled-to-a-preliminary-injunction-to-protect-its-trade-secrets","status":"publish","type":"post","link":"https:\/\/patents.harnessip.com\/?p=3857","title":{"rendered":"Plaintiff Failed to Show It was Entitled to a Preliminary Injunction to Protect its Trade Secrets"},"content":{"rendered":"\n

In Insulet Corp. v. Eoflow, Co, Ltd.<\/a>, [2024-1137] (June 17, 2024), the Federal Circuit reversed a preliminary injunction against manufacturing, marketing, or selling any
product that was designed, developed, or manufactured, in whole or in part, using or relying on alleged trade secrets of Insulet.<\/p>\n\n\n\n

Insulet and EOFlow are medical device manufacturers that make insulin pump patches. Insulet began developing the wearable insulin pump OmniPod\u00ae in the early 2000s. The FDA approved the first OmniPod product in 2005, and a next-generation product, the OPI-2, came onto the market soon thereafter in 2007. Insulet then began work on its next-generation Eros product, which obtained FDA approval in 2012 and commercially launched in 2013.<\/p>\n\n\n\n

EOFlow began developing its own flagship product, an insulin pump patch called the EOPatch\u00ae, soon after the company\u2019s founding in 2011. The EOPatch received regulatory approval in South Korea in 2017, after which EOFlow began developing its next-generation
EOPatch 2. Around that time, four former Insulet employees joined EOFlow. In 2019 and 2022, respectively, the EOFlow 2 received regulatory approval in South Korea and
Europe, after which it began commercial distribution in those select geographic markets.<\/p>\n\n\n\n

After reports surfaced that Medtronic had started a diligence process to acquire EOFlow. Insulet sued EOFlow for violations of the Defend Trade Secrets Act. (\u201cDTSA\u201d), seeking to enjoin all technical communications between EOFlow and Medtronic in view of its trade secrets claims. The district court temporarily restrained EOFlow from \u201cdisclosing products or manufacturing technical information related to the EOPatch or Omni[P]od products,\u201d and then granted Insulet\u2019s request for a preliminary injunction.<\/p>\n\n\n\n

The Federal Circuit began by noting that trade secrets are an important form of intellectual property that both Congress and the states have deemed worthy of protection. The Founders also recognized the value, as well as the volatility, of an idea kept as a secret. However in evaluating Insulet’s likelihood of confusion, the Federal Circuit noted that the court did not assess the statute of limitations in the context of evaluating Insulet\u2019s likelihood
of success on the merits, the court thus ignored a material factor deserving significant weight, which constitutes an abuse of discretion. If the three-year statute of limitations for filing a DTSA claim had expired, Insulet\u2019s claims would be timebarred and therefore would have no chance of success.<\/p>\n\n\n\n

Further, even if the district court had adequately dealt with the statute of limitations issue, that would have been insufficient to support the October 24, 2023 order. As EOFlow further contends, the district court also abused its discretion in its consideration of what constitutes a trade secret. The Federal Circuit quoted the definition of trade secret in the DTSA, and noted that the definition used in the district court’s order was severely overbroad, including \u201cany and all Confidential Information of Insulet\u201d and \u201cany information that contains, derives from, or incorporates such Confidential Information.\u201d<\/p>\n\n\n\n

The Federal Circuit also disagreed with the district court’s assessment that \u201cit would be unfair to require at this stage perfection as to the precise number and contours of the trade secrets at issue.\u201d<\/p>\n\n\n\n

In order to secure a preliminary injunction, Insulet had to establish the likelihood of its success on the merits for at least one, specifically defined, trade secret. It did not do so. Rather, it advanced a hazy grouping of information that the court did not probe with particularity to determine what, if anything, was deserving of trade secret protection.<\/p>\n\n\n\n

Finding that Insulet took measures to protect some unidentified \u201cset of information\u201d is not the same as finding that Insulet took reasonable measures to protect specific information alleged to be a trade secret, such as particular \u201cdesign drawings and specifications for each physical component and subassembly,\u201d as the DTSA requires.<\/p>\n\n\n\n

The Federal Circuit found that because the district court failed to identify any trade secret with sufficient particularity, its analysis of misappropriation necessarily also fails as well.<\/p>\n\n\n\n

The Federal Circuit concluded that in view of the failure to address the statute of limitations,
the lack of a tailored analysis as to what specific information actually constituted a trade secret, as well as the finding that it was \u201chard to tell\u201d what subset of that information
was likely to have been misappropriated by EOFlow, we find that the district court abused its discretion in granting the preliminary injunction.<\/p>\n\n\n\n

The Federal Circuit also agreed with EOFlow that the district court’s analysis of irreparable harm and public interest were flawed. The Federal Circuit made a point of stating that it was not deciding that Insulet has failed to adequately allege misappropriation of trade secrets or that it cannot succeed on the merits of its claims, only that Insulet has not proven it was entitled to a preliminary injunction.<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

In Insulet Corp. v. Eoflow, Co, Ltd., [2024-1137] (June 17, 2024), the Federal Circuit reversed a preliminary injunction against manufacturing, marketing, or selling anyproduct that was designed, developed, or manufactured, in whole or in part, using or relying on alleged … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3857","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3857","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3857"}],"version-history":[{"count":2,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3857\/revisions"}],"predecessor-version":[{"id":3860,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=\/wp\/v2\/posts\/3857\/revisions\/3860"}],"wp:attachment":[{"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3857"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3857"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/patents.harnessip.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3857"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}