A hospital sued over the Meta Pixel usually answers that it was a party to its patients' communications and acted to make money, not to commit a tort. In Mekhail v. North Memorial Health Care, a Minnesota federal court let a former patient's wiretap claims proceed past both answers.
The case at a glance
Mekhail v. North Memorial Health Care, No. 23-cv-00440 (KMM/TNL), ECF No. 54 (D. Minn. Mar. 28, 2024). Decided March 28, 2024, by the United States District Court for the District of Minnesota (Judge Menendez), which granted the motion to dismiss in part: the federal and Minnesota wiretap, deceptive trade practices, health records and unjust enrichment counts survived, and the consumer fraud and invasion of privacy counts were dismissed without prejudice.
A public website, a patient portal and the Pixel
North Memorial is a Minnesota health care provider, and the plaintiff is a former patient. She alleged that it embedded the Meta Pixel in the source code of its public website, which offers information about medical issues, and of its password-protected patient portal, at a MyChart medical-records address, which holds records, appointment booking and test results (ECF No. 54 at 2-3). She also alleged that the hospital urged her to use both and promised to protect users' health data, while the Pixel sent Meta her page views, clicks and search terms, with details about appointments, conditions and treatments, for targeted advertising (ECF No. 54 at 3, 9). Meta was not a defendant.
What the court held
Procurement and interception were plausibly alleged. The patient's counsel disavowed the theory that the hospital intercepted anything itself, relying on its procurement or use of Meta's interceptions (ECF No. 54 at 7). The court held: "Here, Ms. Mekhail has alleged that North procured Meta to embed the Pixel within the source code of North's Websites, and likewise has plausibly alleged that an interception occurred." (ECF No. 54 at 8.)
The crime-tort exception was adequately pleaded. The court found the hospital a party to the communications and assumed, without deciding, that a party accused of procuring or using another's interception can invoke the party exception, an assumption that did not change the outcome (ECF No. 54 at 10-12). The allegation that the Pixel gave Meta access to the patient's health data, for the purpose of monetizing it, was enough to plead a violation of Minnesota's health records law and a claim for unjust enrichment, and the complaint also invoked HIPAA. "As such, Ms. Mekhail's allegations sufficiently plead an interception made with the purpose of violating one or more laws, independent from the act of interception itself." (ECF No. 54 at 14.)
A profit motive is no defense on the pleadings. Footnote 4 answers the hospital's money-motive argument: "The Court will not follow such a bright-line rule in deciding the pending motion. Setting aside that a nuanced and factual differentiation of intent is improper at the pleading stage, the Court has serious doubts that a pecuniary purpose and an injurious purpose can always be so clearly distinguished. And it defies common sense that a clearly harmful act could escape liability as long as it was done for profit." (ECF No. 54 at 14 n.4.) Footnote 3 notes that the primary-motivation test some courts apply is not in the statute: "Nor does the test appear in any authority binding on this Court." (ECF No. 54 at 13 n.3.)
The health records claim survived. Minnesota's Health Records Act bars providers from releasing health records without consent or specific authorization in law, and defines them broadly (ECF No. 54 at 28). The alleged disclosures, above all from the portal, of appointment types and procedures, providers, patient communications, insurance status, and gender and sexual orientation were enough to plead a release without consent (ECF No. 54 at 30-31).
Two more claims survived, and two did not. Deceptive trade practices survived on sufficiently particular allegations about the hospital's privacy promises and a pleaded likelihood of future harm (ECF No. 54 at 17-28), and unjust enrichment on allegations that the hospital monetized the patient's data without compensating her (ECF No. 54 at 33-37). Consumer fraud failed because the alleged misrepresentation concerned data privacy, not the medical services the hospital sells (ECF No. 54 at 15-17). Invasion of privacy failed because the patient dropped the publication theory and, having disavowed that the hospital intercepted, could not plausibly allege that it intruded (ECF No. 54 at 32-33).
Why it matters for hospital and clinic websites and patient portals
On the health records claim, the court rejected the hospital's view that merely inferable health information is never a health record, then called the explicit portal information more critical. Even the Pixel's alleged report of a log-in attempt arguably revealed more than an inference that she was a patient (ECF No. 54 at 30). For a hospital or clinic, the portal's sign-in page and every page behind it are the first places to check for third-party tags.
Nor did the hospital have to intercept anything itself: the wiretap claims rested on its alleged procurement of Meta to embed the Pixel in its code. The unlawful purpose came partly from a state law barring providers from releasing health records without consent, and other states have similar medical confidentiality laws. The crime-tort exception guide collects the predicates courts have accepted.
A past disclosure also stays live: for the deceptive trade practices claim, the court found a likelihood of future harm in the allegation that data already collected remains beyond the patient's control (ECF No. 54 at 25-26). See why fixing a website does not resolve a past visit.
What the hospital argued, and how the court answered
No contents. Citing the Ninth Circuit's In re Zynga Privacy Litigation, the hospital argued that names, Facebook IDs and webpage addresses are not contents. The court answered that "Zynga is not binding on this Court" (ECF No. 54 at 8) and that the decision itself left open that search queries revealed in URLs could be contents in some circumstances. The complaint, alleging details of appointments, conditions and treatments, pleaded contents in any event (ECF No. 54 at 8-9).
Party status. The hospital invoked the party exception. The court's assumption that it could apply is not a ruling, footnote 2 says, and nothing prevented the patient from renewing her argument that it does not cover a party that procures or uses another's interception (ECF No. 54 at 12 n.2).
The privacy policy. The hospital cited its policy, which allegedly says it may disclose information to third parties acting on its behalf. The court would not decide the policy's meaning or effect on the pleadings, leaving that for discovery (ECF No. 54 at 20-21, 35-37).
Subsequent history
The case was later recaptioned Kaliher v. North Memorial Health Care. On July 13, 2026, the parties filed a joint stipulation dismissing the action without prejudice (ECF No. 181), and the federal docket closed on July 15, 2026. No appeal was taken, and the March 28, 2024 ruling was never reversed or vacated. Like any ruling on a motion to dismiss, it accepts the complaint's allegations as true, and it binds no other court.
Read the opinion
Related case notes: Stein v. Edward-Elmhurst Health, Doe v. Baystate Health System, In re Allstate and Arity Consumer Privacy Litigation, M.C. 1 v. Curriculum Associates and Garcia v. Truist.
Checked on November 18, 2026.
Privacy Resolve is not a law firm, and this is not legal advice.