Alfasigma USA, Inc. v. First Databank, Inc.

CourtDistrict Court, N.D. California
DecidedMarch 28, 2022
Docket4:18-cv-06924
StatusUnknown

This text of Alfasigma USA, Inc. v. First Databank, Inc. (Alfasigma USA, Inc. v. First Databank, Inc.) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Alfasigma USA, Inc. v. First Databank, Inc., (N.D. Cal. 2022).

Opinion

1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 ALFASIGMA USA, INC., Case No. 18-cv-06924-HSG 8 Plaintiff, ORDER GRANTING MOTION TO DISMISS 9 v. Re: Dkt. No. 81 10 FIRST DATABANK, INC., 11 Defendant. 12 13 Pending before the Court is Defendant First Databank Inc.’s motion to dismiss the second 14 amended complaint. The Court held a hearing on the motion. For the reasons detailed below, the 15 Court GRANTS the motion. 16 I. BACKGROUND 17 The parties are familiar with the claims in this case. The Court therefore only briefly 18 summarizes the alleged facts as relevant to this motion. 19 A. Allegations 20 Plaintiff Alfasigma USA, Inc. is a pharmaceutical company that develops, manufactures, 21 sells, and distributes medical foods. See Dkt. No. 79 (“SAC”) at ¶¶ 12, 17–21. Plaintiff 22 emphasizes that its three products, which must be used under the supervision of a physician, 23 cannot be accurately described as “over-the-counter.” See id. at ¶¶ 2–4, 12, 18, 22, 42 (citing 21 24 U.S.C. § 360ee(b)(3)). 25 First Databank publishes and sells a “pharmaceutical information database” called 26 MedKnowledge, which contains information about “key characteristics” of pharmaceutical 27 products, such as formulation and pricing. See id. at ¶¶ 13, 30, 36, 41. According to Plaintiff, 1 patients. See id. at ¶¶ 28, 37. Pharmacy benefit managers (“PBMs”) and insurance companies use 2 the database to determine whether products are covered by insurance plans and are eligible for 3 reimbursement. See id. at ¶¶ 28, 39, 50. And pharmaceutical wholesalers, distributors, and retail 4 pharmacies also use the database to determine which products to stock and dispense. See id. at 5 ¶¶ 28, 38. Various third-parties therefore use the database “to make decisions about which 6 products to prescribe, purchase, dispense, and reimburse.” See id. at ¶ 28. 7 At issue in this case is the “class” field in the database. See id. at ¶¶ 35, 43. “Historically,” 8 the database assigned Plaintiff’s products to the “F” class, id. at ¶ 3, which was defined as the 9 “[p]roduct labeling indicates prescription or physician supervision required for use,” id. ¶¶ 43, 44. 10 According to Plaintiff, the “O” class signified “over-the-counter” products, for which “[a] 11 prescription is not required per the product labeling.” See, e.g., id. at ¶ 43 (emphasis omitted). 12 Plaintiff alleges that under this system, the cost of its products was “often covered by insurance 13 plans that limit coverage to prescription products requiring physician supervision,” and was 14 therefore more likely to be reimbursed by PBMs. See id. at ¶¶ 46–47, 52. 15 Starting in 2016, First Databank redefined the “F” class to mean “products that require a 16 prescription,” without reference to whether physician supervision is needed. Id. at ¶ 55 (emphasis 17 added). Because Plaintiff’s medical foods can legally be obtained without a prescription but are 18 used with physician supervision, First Databank assigned Plaintiff’s medical foods to the “O” 19 code, id. at ¶ 3, redefined as “a prescription is not required per the product labeling,” id. at ¶ 43 20 (emphasis omitted).1 However, Plaintiff asserts that even after these changes, “the Healthcare 21 Marketplace universally understood . . . that a product designated ‘O’ is an OTC drug, available 22 over-the-counter and without physician supervision.” See id. at ¶ 44. And many payors would 23 reject claims to reimburse for any product classified as “O.” See id. at ¶ 50. In October 2019, 24 First Databank created a new code—“Q”—which indicates that “[p]roducts that are neither drugs 25 nor devices.” Id. at ¶¶ 9, 94. First Databank has assigned Plaintiff’s medical foods to this “Q” 26 1 Plaintiff acknowledges that federal law does not prohibit medical foods—including Plaintiff’s 27 products—from being dispensed without a prescription. See, e.g., Dkt. No. 95 (“Hrg. Tr.”) at 1 code ever since. Id. at ¶ 9. 2 Plaintiff acknowledges that First Databank “makes coding decisions that comply with 3 customer preferences.” See id. at ¶ 51. Plaintiff alleges that First Databank made these specific 4 changes at the request of certain PBMs who no longer wanted to reimburse for medical food 5 prescriptions. See, e.g., id. at ¶¶ 23, 50–52. By making these changes, First Databank was making 6 its MedKnowledge database “more attractive to customers,” and thus increasing the likelihood that 7 the customers would continue to subscribe to MedKnowledge. See id. at ¶¶ 6, 56. 8 Plaintiff also alleges that the majority of other MedKnowledge customers—who did not 9 request changes to the coding of medical foods—were actually misled by these changes, and 10 began improperly treating Plaintiff’s medical foods “as OTC drugs,” despite the fact that they 11 required doctor supervision. See id. at ¶¶ 7–8, 57, 77–78. These customers, Plaintiff suggests, 12 relied on First Databank’s advertising that its database was accurate and reliable. See id. at ¶¶ 5, 13 30–35, 57–61, 100. Specifically, First Databank circulated “Editorial Highlights” as part of the 14 weekly publications to its existing customers regarding changes to MedKnowledge. Id. at ¶¶ 59– 15 61. In December 2015, the Editorial Highlights explained that First Databank was changing the 16 designation for medical foods from “F” to “O”: 17 While certain medical food labels bear an “Rx” or prescription 18 dispending limitations, FDA regulations limit such designations to drugs and expressly prohibit their application to medical foods. 19 . . . Consequently, since [First Databank’s] “F” Class value identifies 20 products that require a prescription, it cannot be correctly applied to medical foods. 21 Accordingly, [First Databank] will be applying an “O” Class value to 22 all newly added medical food products and will commence a review of existing medical food products on the database to ensure that they 23 are in alignment with these FDA standards. FDB will preannounce any products that undergo a resulting change in their Class value 24 during the next several months. 25 26 Id. at ¶ 60. 27 According to Plaintiff, First Databank reiterated that it was “chang[ing] the coding of 1 be ‘in alignment with’ FDA’s ‘standards.’” See id. at ¶ 61. Plaintiff alleges that these 2 notifications misled MedKnowledge customers to believe that the FDA required the coding 3 change, and that the FDA had indicated that Plaintiff’s medical foods were over-the-counter drugs. 4 See, e.g., id. at ¶¶ 62–74, 76–78, 90, 100, 112. Plaintiff also cites instances of payors announcing 5 that medical foods were not “Rx only,” and therefore would be considered “over-the-counter” 6 instead. See id. at ¶¶ 80–82, 113. As a result of the coding change, Plaintiff asserts that fewer 7 payors reimbursed for them. Id. at ¶¶ 81–82, 84. This, in turn, led to fewer doctors prescribing 8 Plaintiff’s medical foods and fewer wholesalers and pharmacies stocking them. See id. at 86–87. 9 Plaintiff then lost sales as fewer patients purchased its products. See id. at ¶ 85. 10 B. Procedural History 11 Plaintiff filed this action in November 2018. See Dkt. No. 1. Plaintiff initially brought 12 false advertising claims under the Lanham Act; California’s False Advertising Law; California’s 13 Unfair Competition Law; and common law unfair competition. See id. at ¶¶ 59–106. The Court 14 denied Defendant’s motion to strike the state law claims in the original complaint under 15 California’s anti-SLAPP statute and granted in part and denied in part Defendant’s motion to 16 dismiss the Lanham Act claims under Federal Rule of Civil Procedure 12(b)(6). See Dkt. No. 41. 17 Plaintiff then filed its first amended complaint. See Dkt. No. 46 (“FAC”). In the FAC, Plaintiff 18 alleged two theories of liability.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
United States v. Corinthian Colleges
655 F.3d 984 (Ninth Circuit, 2011)
Kwan v. SanMedica International
854 F.3d 1088 (Ninth Circuit, 2017)
City of Oakland v. Wells Fargo & Company
14 F.4th 1030 (Ninth Circuit, 2021)
Sprewell v. Golden State Warriors
266 F.3d 979 (Ninth Circuit, 2001)
Sprewell v. Golden State Warriors
275 F.3d 1187 (Ninth Circuit, 2001)
In re Syngenta AG MIR 162 Corn Litigation
131 F. Supp. 3d 1177 (D. Kansas, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Alfasigma USA, Inc. v. First Databank, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/alfasigma-usa-inc-v-first-databank-inc-cand-2022.