Silvers v. HCA Healthcare, Inc.

CourtDistrict Court, M.D. Tennessee
DecidedAugust 15, 2024
Docket3:23-cv-00684
StatusUnknown

This text of Silvers v. HCA Healthcare, Inc. (Silvers v. HCA Healthcare, Inc.) is published on Counsel Stack Legal Research, covering District Court, M.D. Tennessee primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Silvers v. HCA Healthcare, Inc., (M.D. Tenn. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE MIDDLE DISTRICT OF TENNESSEE NASHVILLE DIVISION

IN RE: HCA HEALTHCARE, INC. Case No. 3:23 CV 684 DATA SECURITY LITIGATION MEMORANDUM OPINION

JUDGE JACK ZOUHARY

INTRODUCTION Defendant HCA Healthcare experienced a cyberattack, later advising patients that hackers may have accessed personal and health information. Plaintiffs bring this putative class action. Plaintiffs jointly allege multiple theories of fault against Defendant, along with violations of various state consumer-protection statues (Doc. 120). Defendant moves to dismiss the Complaint under Federal Civil Rule 12(b)(6) (Docs. 127–28, 139). Plaintiffs oppose (Doc. 135). BACKGROUND Defendant is a large healthcare company comprised of 182 hospitals and over 2,300 care centers throughout the United States and the United Kingdom (Doc. 120 at ¶ 2). On July 5, 2023, Defendant discovered a cyberattack on its computer system (id. at ¶ 3). An unauthorized third party obtained Plaintiffs’ and Class Members’ personal identifiable information (PII) and protected health information (PHI) by hacking an external storage location -- used by Defendant for marketing email communications with patients (id. at ¶ 192). This data breach (Breach) included patient name, city, state, zip code, email, telephone number, date of birth, gender, patient service date, location of appointment, and date of next appointment (id. at ¶ 4). The hacker posted the stolen data dump consisting of 17 files and 27.7 million database records on a dark-web forum (id. at ¶¶ 193–94). The hacker also included a ransom demand to Defendant, with a five-day deadline of July 10, 2023 (id.). After that date had passed, the hacker released the full database for sale (id.). While Defendant claims the information did not include any clinical, payment, or sensitive information, the dark web forum advertised that the data included “emails with health diagnosis that corresponds to a [C]lientID” (id. at ¶ 196). On the deadline day, Defendant announced the cyberattack to the public through a posting on its website (id. at ¶ 195). Four days later, Defendant emailed some of the patients affected by the Breach (id.). In August 2023, Defendant sent out formal notices to affected patients to inform them of the Breach (id.). Defendant offered these patients free credit monitoring and identity-protection

services for two years (id. at ¶ 197). Defendant claims that after discovering the attack, it “promptly disabled access to the external storage location [and] reported the crime to law enforcement” (Doc. 128 at 16). ALLEGATIONS Plaintiffs allege that the Breach resulted in increased spam calls and texts, unauthorized charges on their financial accounts, and fraudulent accounts opened in their names (Doc. 120 at ¶¶ 17–184). Plaintiffs also allege they have suffered lost time, annoyance, and money from monitoring and mitigating the impacts of the Breach (id. at ¶ 11). Their mitigation efforts include costs of identity-theft insurance, credit freezes/unfreezes, lost work time, fraud alerts, and decreased

credit scores (id.). Plaintiffs assert claims for negligence (Count I), negligence per se (Count II), breach of implied contract (Count III), breach of implied covenant of good faith and fair dealing (Count IV), breach of confidence (Count V), unjust enrichment (Count VI), and breach of fiduciary duty (Count VII). Plaintiffs also seek a declaratory judgment that Defendant failed to employ reasonable security measures, and asks that Defendant implement industry-standard measures (Count VIII). Lastly, Plaintiffs assert statutory claims for the subclasses of individuals living in California, Florida, Kansas, Kentucky, Tennessee, and Virginia (Counts IX–XVI). (The Amended Complaint contains 16 counts. Count XV, brought under the Texas Deceptive Trade Practices - Consumer Protection Act, was voluntarily dismissed without prejudice (Doc. 129)). LEGAL STANDARD Under Federal Rule of Civil Procedure 12(b)(6), Defendant can move to dismiss a complaint for “failure to state a claim upon which relief can be granted.” “To survive a motion to dismiss, a complaint must contain sufficient factual matter, accepted as true, to ‘state a claim to relief that is

plausible on its face.’” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atlantic Corp. v. Twombly, 550 U.S. 544, 570 (2007)). “A claim has facial plausibility when [] plaintiff pleads factual content that allows the court to draw the reasonable inference that the defendant is liable for the misconduct alleged.” Id. Determining plausibility is “a context-specific task that requires the reviewing court to draw on its judicial experience and common sense.” Id. at 679. ANALYSIS Defendant argues the Complaint contains three deficiencies that warrant dismissal across the board:

 Plaintiffs’ alleged injuries are not legally cognizable.  Plaintiffs fail to plausibly allege any wrongdoing.  Defendant had no legal duty to control attacks perpetrated by criminal hackers.

Each of these arguments is addressed next. SUFFICIENCY IN PLEADING - GENERAL Cognizable Injury Plaintiffs plead several purported injuries, but the primary one is identity theft. Defendant acknowledges Plaintiffs’ express allegation, but argues that no particularly sensitive information, such as “account numbers, social security numbers, driver’s license numbers, or passwords,” was stolen such that it could plausibly cause the alleged injury (Doc. 128 at 22). Although the severity of the Breach has yet to be determined, it is undisputed that -- at the very least -- PII such as names, birthdates, city, state, zip codes, and contact information were leaked (Doc. 128 at 46). “Where a data breach targets personal information, a reasonable inference can be

drawn that the hackers will use the victims’ data for the fraudulent purposes alleged in Plaintiffs’ complaints.” Galaria v. Nationwide Mut. Ins. Co., 663 F. App’x 384, 388 (6th Cir. 2016). Plaintiffs do not need to be “literally certain” that their data will be misused, at least at this stage. Clapper v. Amnesty Int’l USA, 568 U.S. 398, 415 n.5 (2013). The Sixth Circuit has not weighed in on the type of data necessary to find injury, but other circuits have found that even if a breach did not expose all the data necessary to inflict the alleged harms, leaked personal information “very well could have been enough to aid therein.” Resnick v. AvMed, Inc., 693 F.3d 1317, 1324 (11th Cir. 2012). At this stage, there is a sufficiently alleged substantial risk of harm -- mitigation costs resulting from the Breach. Galaria, 663 F. App’x at 388. This risk of harm due to the Breach, “coupled with

reasonably incurred mitigation costs,” is sufficient to establish cognizable injury. Id. For example, one Plaintiff alleges he has experienced identity theft since the Breach, citing incidents of fraudulent charges made on his financial and credit accounts (Doc. 120 at ¶ 22). Another Plaintiff alleges she was informed by her bank that her bank account attached to Defendant was subject to an attempted fraudulent purchase (id. at ¶ 69). Others recount credit cards opened in their names that they did not personally open (id. at ¶ 89). These and other examples are sufficient to satisfy an increased risk of fraud and identity theft damages. See In re Mednax Servs., Inc., Customer Data Sec. Breach Litig, 603 F. Supp. 3d 1183, 1206 (S.D. Fla.

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

Related

Klaxon Co. v. Stentor Electric Manufacturing Co.
313 U.S. 487 (Supreme Court, 1941)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
MedImmune, Inc. v. Genentech, Inc.
549 U.S. 118 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Jean Resnick v. AvMed, Inc.
693 F.3d 1317 (Eleventh Circuit, 2012)
Clapper v. Amnesty International USA
133 S. Ct. 1138 (Supreme Court, 2013)
Biscan v. Brown
160 S.W.3d 462 (Tennessee Supreme Court, 2005)
Regents of University v. Superior Court
220 Cal. App. 4th 549 (California Court of Appeal, 2013)
United States v. Stevens
994 So. 2d 1062 (Supreme Court of Florida, 2008)
Bradshaw v. Daniel
854 S.W.2d 865 (Tennessee Supreme Court, 1993)
Cloud Nine, LLC v. Whaley
650 F. Supp. 2d 789 (E.D. Tennessee, 2009)
Rains v. Bend of the River
124 S.W.3d 580 (Court of Appeals of Tennessee, 2003)
GuestHouse International, LLC v. Shoney's North America Corp.
330 S.W.3d 166 (Court of Appeals of Tennessee, 2010)
Dawson Wise v. Zwicker & Associates PC
780 F.3d 710 (Sixth Circuit, 2015)
James Heflin v. Iberiabank Corporation
571 S.W.3d 727 (Court of Appeals of Tennessee, 2018)
Richard Faber v. Ciox Health, LLC
944 F.3d 593 (Sixth Circuit, 2019)
Saginaw Cty. v. STAT Emergency Med. Servs.
946 F.3d 951 (Sixth Circuit, 2020)
Jackson Hewitt, Inc. v. Kaman
100 So. 3d 19 (District Court of Appeal of Florida, 2011)
Troy v. RFD-TV The Theater, LLC
498 S.W.3d 550 (Court of Appeals of Tennessee, 2016)
M.T. v. Saum
7 F. Supp. 3d 701 (W.D. Kentucky, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Silvers v. HCA Healthcare, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/silvers-v-hca-healthcare-inc-tnmd-2024.