Atrium Health Patient Portal Pixel Settlement: $1.8M, in State Court
Atrium Health agreed to pay $1.8 million after tracking pixels on its websites and patient portals allegedly shared patients' information with third parties like Meta. What sets this case apart is where and how it was brought — a North Carolina state court, under HIPAA and state privacy law, with no CIPA in sight. It's proof the pixel theory doesn't need California to work.
Case snapshot
- Case
- Roberts, et al. v. The Charlotte-Mecklenburg Hospital Authority (Atrium Health)
- Court
- North Carolina state court
- Case number
- 25CV057073-590
- Legal theory
- Alleged violations of HIPAA and state privacy law — unauthorized disclosure of personal and health information through tracking technology for targeted advertising
- Tracking at issue
- Tracking pixels embedded in Atrium Health's website, alleged to disclose patients' private information to third parties including Meta
- Class (two groups)
- Group 1: portal access Jan 1, 2015 – Jul 31, 2019 · Group 2: portal accounts Jan 1, 2015 – Apr 10, 2024 (MyAtriumHealth / MyCarolinas)
- Settlement
- $1,800,000 · Group 1 pro rata from a $1.5M fund; Group 2 up to $10 from a $300K portion
- Key dates
- Preliminary approval May 22, 2026 · claims deadline Sep 28, 2026 · final approval hearing Sep 30, 2026
- Status
- Final approval stage No admission of wrongdoing; allegations unproven.
On this page
The Atrium Health pixel settlement matters less for its size than for its venue. Atrium Health — the Charlotte-Mecklenburg Hospital Authority, one of the largest health systems in the Southeast — agreed to pay $1.8 million after tracking pixels on its websites and patient portals allegedly disclosed patients' information to third parties including Meta. But this wasn't a CIPA case in a California federal court. It was brought in a North Carolina state court, under HIPAA and state privacy law. For any operator who has been quietly reassuring themselves that pixel litigation is a California phenomenon, or a federal-court phenomenon, Atrium Health is the case that closes both escape hatches.
What the case is about
In Roberts v. The Charlotte-Mecklenburg Hospital Authority, plaintiffs alleged that Atrium Health "surreptitiously embedded" tracking pixels into its website that disclosed patients' private information to third parties — including Meta — for targeted advertising, without patients' consent. The conduct centers on the MyAtriumHealth and MyCarolinas patient portals, the logged-in environments where patients manage their care.
The settlement, which received preliminary approval in May 2026, totals $1,800,000 and is split across two groups of patients defined by when they used the portals. It's structured so that one group shares a larger pro rata fund and a second, broader group receives smaller fixed payments. The case reached its final-approval stage at the end of September 2026.
The detail that makes it matter
Every operator looking for a reason this "doesn't apply to me" eventually lands on one of two: "that's a California (CIPA) problem" or "those are federal class actions." Atrium Health refutes both in a single filing. It was brought in state court, under state law and HIPAA theories, in North Carolina. No CIPA. No federal wiretap claim as the headline. Just state privacy law and health-information rules applied to the same conduct — a pixel on a patient portal sharing data without consent.
This is the quiet but crucial message of the healthcare pixel wave: the theory is venue-agnostic and statute-agnostic. California has CIPA; Pennsylvania has its wiretap act (WESCA, used in Penn Medicine); North Carolina has its own privacy law and HIPAA-based theories. A plaintiff doesn't need the "best" statute — they need a statute, and nearly every state supplies one. Defending against a single law while the same conduct is actionable under a dozen others is a strategy that only looks like protection.
There's a scale lesson hiding here too. Atrium Health is not a small, under-resourced clinic that didn't know better — it's one of the largest health systems in the Southeast, with a serious compliance function and the budget to run it. If a tracking pixel could sit on its patient portals long enough to produce a class action reaching back to 2015, the problem clearly isn't a lack of sophistication or resources. It's that this specific failure mode — a marketing tag quietly loading on a sensitive page — slips past exactly the governance that catches more obvious risks. It's small, technical, and invisible in a normal compliance review, which is precisely why it survives in organizations that are otherwise careful.
The conduct is the risk — wherever you are
A pixel on a patient-facing or logged-in page sharing data before consent is actionable in many states under many laws. ConsentPixel's free scanner shows what fires before consent on your site, so you can fix the conduct rather than bet on your jurisdiction.
Scan my site free →State court, HIPAA, no CIPA
The Atrium Health claims rest on HIPAA and state privacy law rather than California's CIPA or the federal Wiretap Act. A clarification worth making: individuals generally can't sue directly under HIPAA — there's no private right of action in the statute itself. What plaintiffs do is use HIPAA as the standard of care that state-law claims (negligence, invasion of privacy, breach of fiduciary duty, state consumer-protection statutes) borrow from. HIPAA defines what "protecting health information" should look like; state law provides the vehicle to sue when that standard allegedly wasn't met.
That mechanism is why these cases are so portable. Almost every state recognizes some privacy tort or consumer-protection claim, and HIPAA supplies a ready-made benchmark for health data. Stack them together and a plaintiff in North Carolina — or almost anywhere — has a workable path, no CIPA required.
It also carries a subtle disadvantage for defendants that's worth understanding. Because the claim borrows HIPAA's standard rather than suing under it, the defense can't simply argue "HIPAA doesn't give you the right to sue me" — that's true, but beside the point, because the plaintiff isn't suing under HIPAA. The negligence or privacy claim stands on its own state-law footing, with HIPAA brought in only to define what reasonable care looked like. That framing lets plaintiffs harness HIPAA's detailed, well-known rules about protecting health information without being limited by HIPAA's enforcement structure. For a health system, it means the familiar comfort of "HIPAA has no private right of action" offers far less protection than it sounds like it should.
The two-group class structure
Atrium Health's settlement is a useful illustration of how these classes actually get built, because it uses two tiers. Group 1 covers patients who accessed the portal in an earlier window (January 2015 to July 2019) and shares the larger portion of the fund on a pro rata basis. Group 2 is broader — anyone with a portal account across a longer window (through April 2024) — and receives smaller fixed payments of up to $10 from a separate portion.
Why structure it this way? Because exposure usually isn't uniform across time. An earlier period might involve different tracking configurations, more data, or a stronger claim, warranting a larger share; a later, broader group gets acknowledged with a modest payment. For an operator, the takeaway isn't the payout mechanics — it's what the class periods reveal. These windows stretch back to 2015, meaning the alleged tracking persisted, unexamined, for years. The settlements keep surfacing conduct that ran quietly for the better part of a decade because no one was checking what fired on the portal.
Part of the $100M pattern
Atrium Health is another entry in the healthcare pixel wave that now exceeds $100 million in aggregate settlements. The healthcare pixel settlement roundup covers the full list; here's how Atrium sits among its closest cousins.
| Case | Venue | Legal basis | Settlement |
|---|---|---|---|
| Penn Medicine | PA federal | State wiretap (WESCA) | $9.5M |
| Cone Health | NC federal | ECPA + PHI disclosure | $1.76M |
| Atrium Health | NC state | HIPAA + state privacy | $1.8M |
Read across that table and the message is hard to miss: federal or state, California or not, the conduct settles. Three different legal routes converge on the same behavior. The operator's defense can't be jurisdictional; it has to be about the conduct itself.
What this means for your site
Atrium Health reinforces the healthcare lessons and adds a jurisdictional one:
Related cases & reading
← CIPA Lawsuit Tracker — every tracked case Healthcare pixel settlement roundup → the $100M pattern Cone Health ($1.76M) → the MyChart portal caseKey takeaways
- $1.8M, in state court. Atrium Health settled over pixels on its websites and patient portals that allegedly shared data with third parties including Meta.
- No CIPA, no federal wiretap headline. The case ran on HIPAA-informed state privacy law in North Carolina — proof the theory travels.
- HIPAA as the standard, state law as the vehicle. You can't usually sue under HIPAA directly, but it sets the benchmark state claims borrow.
- Two-tier class, class periods to 2015. The alleged tracking ran for years unexamined — audit history, not just the present.
- Geography isn't a defense. The conduct is actionable in many venues under many laws; fix the conduct.
Frequently asked questions
What is the Atrium Health pixel settlement about?
Roberts v. The Charlotte-Mecklenburg Hospital Authority alleges that Atrium Health embedded tracking pixels in its website that disclosed patients' private information to third parties, including Meta, for targeted advertising without consent — focused on the MyAtriumHealth and MyCarolinas patient portals. Atrium Health agreed to an $1,800,000 settlement, which received preliminary approval in May 2026 and reached final-approval stage at the end of September 2026. No court ruled on the merits and there is no admission of wrongdoing.
Is this a CIPA case?
No. It was brought in North Carolina state court under HIPAA and state privacy law — not California's CIPA, and not as a federal wiretap case. We include it on the CIPA tracker because the underlying conduct is identical to the CIPA cases, and because it demonstrates that pixel claims succeed well outside California, under entirely different statutes.
Can patients sue under HIPAA directly?
Generally no — HIPAA does not provide a private right of action, so individuals can't sue under it directly. Instead, plaintiffs use HIPAA as the standard of care for state-law claims such as negligence, invasion of privacy, or consumer protection. HIPAA defines what protecting health information should look like; state law supplies the mechanism to sue when that standard allegedly wasn't met. That combination is what powers cases like Atrium Health.
Why are there two groups in the settlement?
Because exposure isn't uniform over time. Group 1 (portal access January 2015 to July 2019) shares the larger portion of the fund on a pro rata basis, reflecting a stronger or earlier-period claim; Group 2 (anyone with a portal account through April 2024) is broader and receives smaller fixed payments of up to $10 from a separate portion. Tiered classes let a settlement acknowledge different levels of alleged exposure across different time windows.
I'm not in California or in healthcare — does this apply to me?
The jurisdictional lesson applies to everyone: pixel claims succeed in state courts under state privacy and consumer-protection laws nationwide, not just under CIPA in California. The healthcare specifics (HIPAA as a standard) apply if you handle health data, but any business sharing user data via trackers before consent faces analogous state-law exposure. The conduct, not the location, is the risk.
What should I check on my own site?
Check what fires before consent, with special attention to logged-in and sensitive pages like account portals and forms. Because class periods in these cases stretch back years, it's also worth understanding what has been firing historically, not just what fires today. A privacy scan surfaces the current trackers and firing order quickly; historical exposure may require reviewing past tag-manager configurations.
The bottom line
Atrium Health is the case that takes away the map. There's no state line you can stand behind, no "we're not in California," no "those are federal cases." The same pixel-on-a-portal conduct settled in North Carolina state court under HIPAA-informed state law — and it would find a workable statute in nearly any state.
That leaves exactly one durable defense, which is also the simplest: don't let third-party trackers fire on your sensitive and logged-in pages without consent, and verify that they don't. It's the one thing that holds up regardless of where a plaintiff files.
Fix the conduct, not the jurisdiction
Scan your site and see what fires before consent — including the portal and logged-in pages these settlements turn on. One check, every jurisdiction.
Scan my site free →ConsentPixel Team
ConsentPixel tracks website-tracking litigation across jurisdictions and helps operators fix the pre-consent data sharing that settles under CIPA, state law, and federal statutes alike.