Sweat v. Houston Methodist Hospital

CourtDistrict Court, S.D. Texas
DecidedSeptember 22, 2025
Docket4:24-cv-00775
StatusUnknown

This text of Sweat v. Houston Methodist Hospital (Sweat v. Houston Methodist Hospital) is published on Counsel Stack Legal Research, covering District Court, S.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Sweat v. Houston Methodist Hospital, (S.D. Tex. 2025).

Opinion

IN THE UNITED STATES DISTRICT COURT September 22, 2025 FOR THE SOUTHERN DISTRICT OF TEXAS Nathan Ochsner, Clerk HOUSTON DIVISION

EDWARD SWEAT, et al., individually and § on behalf of a class of similarly situated § individuals, § § CIVIL ACTION NO. H-24-775 Plaintiffs, § v. § § HOUSTON METHODIST HOSPITAL, § § Defendant. §

MEMORANDUM AND OPINION Edward and Marie Sweat sued Houston Methodist Hospital, seeking to represent a class of individuals who had their personal health information disclosed by a tracking Pixel installed on Methodist’s website. (Docket Entry No. 1-1). The court granted Methodist’s motion to dismiss the state-law claim for invasion of privacy. (Docket Entry No. 28). The remaining claims allege that Methodist is liable for violating the Wiretap Act, 18 U.S.C. §§ 2510-2523, and for state-law unjust enrichment. (Id.). The parties conducted discovery. Methodist now moves for summary judgment on the remaining claims, arguing that its actions do not satisfy the Wiretap Act’s crime- tort exception because it did not know that it was disclosing individually identifiable health information and because its only purpose in using the Pixel was to improve the effectiveness of its advertising and public health communications. (Docket Entry No. 52). The Sweats have responded to the motion, arguing that Methodist’s acts in disclosing the information obtained by the Pixel are sufficient for liability. (Docket Entry No. 58). Based on the pleadings, the motion and response, the record, and the applicable law, this court grants Methodist’s motion for summary judgment. Final judgment is separately entered. The reasons are set out below. I. Background Methodist is a nonprofit hospital serving the greater Houston area. (Docket Entry No. 52- 6 at 8). To connect patients with doctors for medical care, its marketing department conducts community outreach, including advertising and public health campaigns. (Id. at 8–9). To track the performance of these outreach efforts, Methodist installed a Facebook tracking Pixel on public-

facing pages of its website.1 (Id. at 9; Docket Entry No. 52-10 at 8, 10). Methodist was hardly the only hospital to use the Pixel; fully one-third of the nation’s top 100 hospitals did so. (Docket Entry No. 52-19 at 2). Methodist’s stated purpose in implementing the Pixel was to learn if its outreach campaigns were accomplishing its goal of attracting people to its website and taking further “intent” actions, such as clicking a button on the site indicating that the person was going to schedule an appointment. (Docket Entry No. 52-6 at 9; Docket Entry No. 58-7 at 4, 5). Methodist first implemented the Pixel in 2017, on the advice of Rise Interactive, a digital advertising agency. (Docket Entry No. 52-16). Methodist states that Rise Interactive advised the hospital that the Pixel was “safe” to use. (Docket Entry No. 52-11 at 8). Methodist later changed

its advertising agency from Rise Interactive to Fathom SEO, a choice driven in part by Fathom’s experience in healthcare marketing. (Docket Entry No. 52-10 at 12). Methodist states that Fathom also advised the hospital that the Pixel was safe to use. (Docket Entry No. 52-11 at 8). Fathom’s agreement with Methodist stated that Fathom would provide services “in accordance with all applicable law, industry standards, and professional requirements.” (Docket Entry No. 52-4).

1 The parties generally—but not always—refer to “Facebook” instead of “Meta” when identifying the company that created the Pixel and received the sensitive information. (See generally Docket Entry Nos. 52, 58). In the first amended complaint, the Sweats stated that their information was improperly disclosed to “Meta Platforms, Inc. d/b/a Meta (“Facebook”).” (Docket Entry No. 6 at 2). In line with the parties’ use, the court generally refers to Facebook but refers to Meta when the underlying source (for example, a privacy policy or email chain) identifies the company as Meta. 2 As part of Fathom’s services, Methodist received reports based on aggregated data gathered from the Pixel on the performance of its advertising and public health campaigns. (Docket Entry No. 52-9). The data provided Methodist with information, including the number of impressions on a social media post—the number of times its content was displayed on a user’s screen, regardless of whether the user engaged with it or not—and the number of “lead actions” (such as

scheduling an appointment) taken on Methodist’s website in response to the advertised activity. (Id.). Methodist points to an example in one report showing that 2,078 users saw its “monthly reminder” on Facebook to schedule a mammogram and that 374 visited Methodist’s website to do so. (Docket Entry No. 52 at 19) (citing Docket Entry No. 52-9). The aggregated data that Methodist received did not include information identifying the individuals who were seeking or obtaining healthcare services at Methodist. (Docket Entry No. 54-3). Methodist employees all testified that they believed that the Pixel data did not collect individually identifiable health information. (See, e.g., Docket Entry No. 52-6 at 9; Docket Entry No. 52-8 at 16; Docket Entry No. 52-10 at 7). Methodist did not embed the Pixel within MyChart, the individual patient portal.

(Docket Entry No. 52-8 at 17; Docket Entry No. 52-10 at 10; Docket Entry No. 58-3 at 4). On May 18, 2022, a reporter from The Markup, a nonprofit newsroom covering the technology industry, emailed Methodist for comment about its use of the Pixel. (Docket Entry No. 52-18). The reporter explained that the Markup had conducted tests of the Pixel on Methodist’s website and the websites of other hospitals, and that these tests showed that the Pixel was potentially capturing sensitive health information in violation of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), 42 U.S.C. §§ 1320d-1320d-9. (Id.). After receiving this email, Methodist promptly contacted Fathom for more information about how the Pixel’s data filter worked. (Docket Entry No. 52-12). Fathom’s privacy officer stated that the

3 Pixel captured IP addresses but that “[s]ince health information is filtered out, and all data is hashed and randomized (meaning it can no longer be used to identify an individual,) Meta isn’t collecting” protected health information. (Id.). The privacy officer added that Meta’s systems were designed to filter out sensitive health information and that such information was “not collected.” (Id.). On May 23, 2022, following its discussion with Fathom, Methodist reached out to Meta

for more information about what information the Pixel filtered out and what data it collected. (Docket Entry No. 52-20). In response, Meta “delivered highly sanitized non-answers.” (Docket Entry No. 52 at 13). Meta’s responses emphasized that personally identifying information should be “hashed before transmission” and that healthcare organizations should be “especially mindful” to configure Meta’s tools so as to not send personal health information. Meta also stated that it had a filtering mechanism to “prevent [potentially sensitive health-related data] from being ingested into our ads ranking and optimization systems,” and that if Meta’s filter detected such data, it would send an email alerting the organization of the issue. (Docket Entry No. 52-21 at 12– 15). Meta could not confirm if it was receiving certain health information, such as the names of

patients making appointments with particular doctors. (Id. at 12). Just before the June 16, 2022, publication of The Markup’s article on hospitals’ use of the Pixel, Methodist removed the Pixel from its website. (Docket Entry No. 52-19 at 6).

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

Related

Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
Caro v. Weintraub
618 F.3d 94 (Second Circuit, 2010)
Todd Ion v. Chevron USA, Inc.
731 F.3d 379 (Fifth Circuit, 2013)
Payne v. Norwest Corp.
911 F. Supp. 1299 (D. Montana, 1995)
In Re DoubleClick Inc. Privacy Litigation
154 F. Supp. 2d 497 (S.D. New York, 2001)
Travis Thomas v. Michael Tregre
913 F.3d 458 (Fifth Circuit, 2019)
Nichole Sanchez v. Young County, Texas, et
956 F.3d 785 (Fifth Circuit, 2020)
United States v. Chia Lee
966 F.3d 310 (Fifth Circuit, 2020)
Shah v. VHS San Antonio Partners
985 F.3d 450 (Fifth Circuit, 2021)
Jones v. Gulf Coast Restaurant
8 F.4th 363 (Fifth Circuit, 2021)
Houston v. TX Dept of Agri
17 F.4th 576 (Fifth Circuit, 2021)
MDK Sociedad v. Proplant
25 F.4th 360 (Fifth Circuit, 2022)
Springboards to Educ v. Pharr San Juan
33 F.4th 747 (Fifth Circuit, 2022)
Sussman v. American Broadcasting Companies, Inc.
186 F.3d 1200 (Ninth Circuit, 1999)
Gate Guard Services L.P. v. Perez
14 F. Supp. 3d 825 (S.D. Texas, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Sweat v. Houston Methodist Hospital, Counsel Stack Legal Research, https://law.counselstack.com/opinion/sweat-v-houston-methodist-hospital-txsd-2025.