· Court ruling
Sweat v. Houston Methodist Hospital
U.S. District Court for the Southern District of Texas, No. 4:24-cv-00775, ECF No. 63
Primary source: Memorandum and opinion. Checked on November 10, 2026.
On summary judgment, a Texas federal court held a hospital's Facebook Pixel use fell outside the crime-tort exception because the evidence showed it did not know it was disclosing identifiable health information.
What happened
Edward and Marie Sweat sued Houston Methodist Hospital in Texas state court in 2024, seeking to represent a class of people whose health information was allegedly disclosed through a Facebook tracking Pixel on the hospital's website, and the hospital removed the case to federal court. An earlier order dismissed the state-law invasion of privacy claim with prejudice and let the Wiretap Act and unjust enrichment claims proceed, and the court then split discovery so that liability came before class issues. (ECF No. 63 at 1, 5.)
The summary judgment record, viewed in the light most favorable to the plaintiffs, showed that the hospital first installed the Pixel on public-facing pages of its website in 2017, on the advice of a digital advertising agency. Its stated purpose was to learn whether its outreach campaigns drew people to the site and led them to take further steps, such as clicking a button indicating they would schedule an appointment. It did not embed the Pixel in MyChart, its patient portal, and it stated that both of its advertising agencies advised it the Pixel was safe to use. (ECF No. 63 at 2-3, 5-6.)
The reports the hospital received from its agency were based on aggregated Pixel data, such as the number of times a post was displayed and the number of actions, like scheduling an appointment, taken on the site in response, and they did not identify the individuals seeking care. Hospital employees testified that they believed the Pixel did not collect individually identifiable health information. (ECF No. 63 at 3, 11.)
After a reporter from The Markup asked about the Pixel on May 18, 2022, the hospital asked its agency and Meta what the Pixel collected and filtered. The agency's privacy officer said the Pixel captured IP addresses but that health information was filtered out and the data hashed; Meta could not confirm whether it was receiving certain health information, such as the names of patients making appointments with particular doctors. The hospital removed the Pixel just before The Markup published its article on June 16, 2022. (ECF No. 63 at 3-4.)
What the court held
The court framed the summary judgment question as whether the evidence raised a genuine dispute that the hospital used the Pixel for the purpose of committing a criminal or tortious act. The plaintiffs relied only on HIPAA's crime of knowingly disclosing individually identifiable health information, and the court said the threshold issue was not whether the hospital violated HIPAA but whether it acted with the purpose of violating HIPAA. (ECF No. 63 at 7-8 & n.4)
the threshold issue is not whether Methodist violated HIPAA, but whether it acted with the purpose of violating HIPAA
ECF No. 63 at 8 Courts take different approaches to the exception, asking whether the crime or tort is independent of the interception, whether it was the primary motivation, or both. Under any approach, the court said, a plaintiff at summary judgment must present evidence of a factual dispute about whether the defendant intended to commit a crime or tort. (ECF No. 63 at 9-10)
But to find liability under any of these approaches, the plaintiff must plead or, on summary judgment, present evidence raising a factual dispute as to whether the defendant intended to commit a crime or tort.
ECF No. 63 at 10 The court found no evidence that the hospital acted with the purpose of violating HIPAA, because the evidence showed it did not know it was disclosing individually identifiable health information. It relied on the aggregated, anonymous reports the hospital received, the employees' consistent testimony, testimony that its agency worked with other large health systems on the common practice of using the Pixel (a third of the nation's top 100 hospitals used it), and the hospital's prompt questions to its agency and Meta after the reporter's inquiry. (ECF No. 63 at 10-11)
there is no evidence that Methodist acted with the purpose of violating HIPAA by disclosing individually identifiable health information; the evidence shows that it did not know it was doing so
ECF No. 63 at 10 The plaintiffs' arguments, that aggregate data must come from individual data, that a sentence in the hospital's privacy policy and Meta's filter disclosure showed knowledge, and that the hospital failed to take basic precautions, did not create a triable issue of knowledge or willful blindness. The plaintiffs offered no evidence contradicting the employees' testimony, and at most the record suggested negligence, which does not show the required purpose. (ECF No. 63 at 11-13 & nn.6-7)
these assertions essentially accuse Methodist of being negligent in its use of the Pixel, which is clearly insufficient to show that Methodist acted with the purpose of violating HIPAA
ECF No. 63 at 12 The court held that the hospital's only purpose shown by the record, improving its marketing and outreach, was not an intent to commit a crime or tort. It did not decide whether the exception applies when a medical provider's primary purpose is commercial, an open question in the Fifth Circuit, because a commercial purpose must still be tied to a criminal or tortious purpose. (ECF No. 63 at 10, 13-14)
the court need not reach this question because a commercial purpose must still be tethered to a criminal or tortious purpose
ECF No. 63 at 13 The court rejected the argument that the hospital's commercial purpose was itself a HIPAA crime. It read 42 U.S.C. § 1320d-6 to punish knowingly disclosing individually identifiable health information and to increase the penalty when the offense is committed with intent to use the information for commercial advantage, not to make a disclosure with a commercial purpose a crime by itself. (ECF No. 63 at 14)
The disclosure of what was not known to be personally identifiable health information, but instead believed to be aggregate data, for a commercial purpose, is not a crime or a tort.
ECF No. 63 at 14 Construing the purpose requirement narrowly, so that it reaches only conduct undertaken with a specific intent at the time to commit a crime or tort, the court held that the plaintiffs had not shown that intent and granted summary judgment on the Wiretap Act claim. (ECF No. 63 at 14-15)
Summary judgment was also granted on the unjust enrichment claim, which the plaintiffs dropped because they did not dispute that the hospital did not sell the information for profit, and final judgment was entered by separate order. (ECF No. 63 at 15-16)
What it did not decide
- Whether the alleged HIPAA disclosure was independent of the interception. The hospital argued it was not and that the Wiretap Act should not become a back door to private HIPAA litigation; the court said there was merit to the argument but did not need to consider it (ECF No. 63 at 9 n.5).
- Whether the Pixel in fact sent individually identifiable health information to Facebook. The hospital raised that point only in a footnote, which the court noted may be disregarded, and the court decided the motion on purpose (ECF No. 63 at 8 n.3, 10).
- Whether the crime-tort exception applies when a medical provider's primary purpose in disclosing information is commercial; the court noted that the Fifth Circuit had not yet ruled on that question and did not reach it (ECF No. 63 at 13).
- The two Texas statutes pleaded earlier as predicates; at summary judgment the plaintiffs relied only on HIPAA, and the court reviewed only that predicate (ECF No. 63 at 8 n.4).
- Class certification, Article III standing, contents and statutory damages under 18 U.S.C. § 2520; the opinion does not discuss them, and class discovery had been deferred until after liability (ECF No. 63 at 5).
The tracking involved
Tools
- Facebook (Meta) Pixel on public-facing pages of the hospital's website
Data
- visits to and actions on public-facing pages, including pages and buttons indicating that a visitor was going to schedule an appointment
- IP addresses, according to the advertising agency's privacy officer
How it bears on website tracking claims
Supports: strengthens a website tracking claim on this issue. Limits: narrows or defeats a website tracking claim on this issue. Context: bears on the issue without deciding it either way.
Limits: Crime-tort exception
Whether a communication was intercepted for the purpose of a criminal or tortious act, which removes the party exception.
This ruling came at summary judgment after liability discovery, and it shows what the exception can require once evidence is in: evidence that the operator intended to commit the predicate crime or tort when it used the tracking code. The court found no such evidence where employees consistently testified they believed the Pixel collected no identifiable health information, the hospital received only aggregated reports, and it questioned its agency and Meta promptly after a reporter's inquiry; arguable negligence was not enough. It is one district court's decision on its own record, and other courts read the purpose requirement differently, as the Northern District of Illinois noted in Stein v. Edward-Elmhurst Health when it certified the question to the Seventh Circuit.
Limits: HIPAA
How HIPAA, its criminal provision at 42 U.S.C. § 1320d-6 and HHS guidance bear on tracking.
The court read 42 U.S.C. § 1320d-6 to require a knowing disclosure of individually identifiable health information, with the commercial-advantage language raising the penalty rather than defining a separate crime. On that reading, at summary judgment a HIPAA-based crime-tort theory needs evidence that the operator knew, or was willfully blind to the fact, that its tracking code disclosed such information, and a marketing purpose alone does not supply it. The court did not decide whether the Pixel actually disclosed individually identifiable health information.
Context: Party exception
Whether the website, as a party to the visit, could consent to the tracking under 18 U.S.C. § 2511(2)(d).
The court described 18 U.S.C. § 2511(2)(d), under which a party to a communication is ordinarily not liable unless the crime-tort exception applies, and decided the Wiretap Act claim on that exception. The opinion does not discuss any dispute about whether the hospital was a party.
Context: Health information
What counts as individually identifiable health information when it is sent through tracking tools.
In a footnote, the court observed that courts have had difficulty deciding what allegations show a disclosure of individually identifiable health information, citing Castillo v. Costco Wholesale Corp., and that the decision in American Hospital Association v. Becerra vacating HHS guidance made the definition more complicated. It did not apply the definition to the data in this case (ECF No. 63 at 15 n.8).
Arguments it addresses
- The company did not know its tags were sending health information
- On this record the court agreed that the hospital lacked the required purpose: it found no evidence the hospital knew it was disclosing individually identifiable health information and no triable issue of willful blindness (ECF No. 63 at 10-13).
- The purpose was marketing, not a crime
- The court held that a purpose limited to improving marketing and outreach, without an intent to commit a crime or tort, does not trigger the exception, but it did not decide whether the exception applies when a medical provider's primary purpose in disclosing information is commercial, which it said the Fifth Circuit had not yet decided (ECF No. 63 at 10, 13-14).
- The data was aggregated or de-identified
- The court held that receiving aggregated reports did not show the hospital knew it was disclosing identifiable health information, because aggregate data can be built from data anonymized at the input level; it did not decide what the Pixel actually sent (ECF No. 63 at 8 n.3, 12).
- A vendor said health data was filtered or hashed
- The court treated the hospital's questions to its agency and Meta, and Meta's statement that its filter was designed to keep sensitive health data out of its ads systems, as supporting the employees' testimony, and held that the filter disclosure, which did not make clear whether the filter rejected sensitive health data, at most suggested the hospital should have looked more closely (ECF No. 63 at 11-13).
- The disclosure is the same act as the interception
- The hospital made this independent-act argument, and the court said it had merit but did not need to decide it (ECF No. 63 at 9 n.5).
- The website was a party to the communication
- The opinion does not discuss party status; it decided the claim under the crime-tort exception to the party exception and held that the plaintiffs lacked evidence of the required purpose (ECF No. 63 at 7-10).
For a company that received a letter
- This was a summary judgment ruling after liability discovery, so it turned on testimony and documents about what the hospital knew and intended rather than on the complaint's allegations.
- The court did not decide whether the Pixel sent individually identifiable health information, and it found merit in, but did not decide, the argument that a HIPAA disclosure is not independent of the interception.
- At summary judgment the plaintiffs relied only on HIPAA as the predicate crime or tort, so the ruling does not address other predicates such as state statutes.
- Courts are divided on how to read the exception's purpose requirement, and a later Illinois decision that lists this ruling on one side of that split certified the question to the Seventh Circuit, where the appeal is pending.
What to check on your own site
- Check what your tags send from appointment and scheduling pages, not only what your aggregated campaign reports show.
- Check whether a vendor's statement that health data is filtered or hashed has been confirmed against what your pages actually transmit.
- Check whether any tracking code runs inside your patient portal or only on public pages.
Later history
The court entered final judgment dismissing the case with prejudice the same day (ECF No. 64). The CourtListener docket, read on November 10, 2026, shows the case closed on September 22, 2025 and no filing after the final judgment.
Related rulings
Published by Privacy Resolve from public records. It does not cover our own matters.
General information only, not legal advice, and not a substitute for the advice of an attorney. Laws, deadlines, defenses and outcomes vary by jurisdiction and facts.