[Enforcement library](/enforcement)

# Ortega v. Emanate Health: $777,000 pixel settlement over Meta Pixel and analytics on a hospital site

Patients alleged Emanate Health Medical Center disclosed personal and protected health information to Meta, Google and other third parties through analytics tools such as the Meta Pixel on its public website and patient portal. The Los Angeles Superior Court set a $777,000 class settlement for final approval on November 19, 2026. Claims closed September 29, 2026. Emanate denies wrongdoing.

## Key facts

- **Regulator or court:** Superior Court of California, County of Los Angeles
- **Jurisdiction:** California, US
- **Framework:** CIPA; California Confidentiality of Medical Information Act (CMIA); California Constitution privacy; intrusion upon seclusion
- **Record date:** 2026-11-19
- **Procedural status:** Settlement preliminarily approved; final approval hearing 19 November 2026

A California hospital system put Meta Pixel and other analytics on pages where patients log into a portal, submit forms or book appointments. The proposed $777,000 settlement pays claiming class members a pro rata share after fees and costs.

[Start a free scan](/run-free-codebase-scan)

- **Court**: Superior Court of California, County of Los Angeles (Hon. Carolyn Kuhl, Department 012)
- **Case number**: Lead Case No. 22STCV28142
- **Parties**: Jamie Ortega, Sally Shively, Betsy Vergara, Patsyann Sutton, Mary Perez and Stefanie Diamond v. Emanate Health Medical Center
- **Laws**: CIPA; CMIA; California Constitution privacy; intrusion upon seclusion
- **Stage**: Preliminary approval (order dated 1 June 2026 on the filled form); final approval hearing 19 November 2026, 10:30 a.m.
- **Amount**: $777,000 gross settlement fund; estimated net about $433,709 for pro rata claims
- **Source review**: 6 November 2026

## The problem

The lawsuit claims Emanate was responsible for a "Pixel Disclosure": use of website analytics tools such as the Meta Pixel that allegedly shared personal identifying information and/or protected health information of people who used Emanate's site. The claims are CIPA, CMIA, invasion of privacy under the California Constitution, and intrusion upon seclusion ([FAQ](https://www.emanateprivacysettlement.com/faqs/); [settlement website](https://www.emanateprivacysettlement.com/)). Emanate denies the allegations and any wrongdoing.

## What the settlement covers

| Issue | Term |
| --- | --- |
| Class | Identifiable individuals who logged into the Emanate patient portal, and/or submitted an online form, and/or scheduled an appointment on https://www.emanatehealth.org/, from 30 August 2019 to 30 April 2024 |
| Gross fund | $777,000 |
| Estimated deductions | Administration about $54,291; service awards $2,500 x 4 ($10,000); attorneys' costs not to exceed $20,000; attorneys' fees not more than 33% ($259,000), subject to court approval |
| Estimated net | About $433,709, paid pro rata to valid claimants (about $11 if every class member claims; about $55 at a 20% claims rate, per the FAQ) |
| Cy pres | Electronic Frontier Foundation for any remaining net funds after distribution |
| Released tools (release language) | Analytics tools such as the Meta Pixel or Google Analytics on the Website |

Sources: [FAQ](https://www.emanateprivacysettlement.com/faqs/); [preliminary approval order PDF](https://www.emanateprivacysettlement.com/wp-content/uploads/2026/06/Order-Granting-Motion-for-Preliminary-Approval.pdf).

## Technical issue

- **Where the data came from:** Emanate's public website and patient portal, including portal login, online forms and appointment scheduling.
- **Who received it (alleged):** third parties such as Meta and Google through analytics tools including the Meta Pixel and Google Analytics.
- **Why it is sensitive:** plaintiffs say the shared information included personal identifying information and/or protected health information.

**Inth's technical interpretation:** portal entry, forms and appointment booking are sensitive routes. Advertising and analytics tags that can read form fields, query strings or login state should not load there.

Sample:

```ts
// Marketing analytics load on portal and form routes
loadTag('meta-pixel');
loadTag('google-analytics');

// Keep ads and cross-site analytics off sensitive hospital routes
const sensitive = ['/portal', '/forms', '/appointments', '/schedule'];
if (!sensitive.some(p => location.pathname.includes(p)) && consent.has('analytics')) {
  loadTag('analytics');
}
```

## Timeline

| Date | Event |
| --- | --- |
| 2022 | Lead case filed (Case No. 22STCV28142) |
| 1 June 2026 | Preliminary approval order date filled on the order form |
| 31 August 2026 | Opt-out and objection deadline |
| 29 September 2026 | Claim deadline |
| 19 November 2026 | Final approval hearing, 10:30 a.m., Department 012 |

## Outcome

The settlement is not final. The court will decide final approval, fees and service awards at the 19 November 2026 hearing ([FAQ](https://www.emanateprivacysettlement.com/faqs/); [settlement website](https://www.emanateprivacysettlement.com/)). Payments go out only after final approval and any appeals. Claim, opt-out and objection deadlines have passed.

## What it cost

| Item | Amount | Source |
| --- | --- | --- |
| Gross settlement fund | $777,000 | [FAQ](https://www.emanateprivacysettlement.com/faqs/) |
| Estimated net for class members | About $433,709 | [FAQ](https://www.emanateprivacysettlement.com/faqs/) |
| Attorneys' fees requested | Not more than 33% ($259,000) | [FAQ](https://www.emanateprivacysettlement.com/faqs/) |
| Service awards requested | $2,500 each to four class representatives ($10,000) | [FAQ](https://www.emanateprivacysettlement.com/faqs/) |
| Administration (estimated) | About $54,291 | [FAQ](https://www.emanateprivacysettlement.com/faqs/) |

## Why it matters

- **The class is defined by sensitive actions.** Portal login, form submission and appointment scheduling are named, not general browsing.
- **Meta Pixel and Google Analytics are both in the release.** Hospital sites often run several analytics stacks on the same sensitive pages.
- **A sub-$1 million fund still requires a claims process.** Compare [Cone Health](/enforcement/cone-health), [Doe v. Amisub (Tenet)](/enforcement/doe-v-amisub-tenet-healthcare) and [Penn Medicine](/enforcement/penn-medicine).

Related pages: [Sensitive contexts and health data](/enforcement/issues/sensitive-contexts-and-health-data), [Undisclosed data exchanges](/enforcement/issues/undisclosed-data-exchanges), [CIPA § 631](/enforcement/laws/cipa-631-wiretapping).

## How Inth catches this

- **Consent banner**: Holds advertising and cross-site analytics behind consent and can keep them off portal, form and appointment routes entirely.
- **Website audit**: Loads public pages in a clean profile and records third-party requests on forms and portal entry points before and after a choice.

### Out of reach

- Inth cannot see inside a logged-in patient portal once the session leaves the public site.

Consent records with choice, purpose, country and policy version.

[Start a free scan](/run-free-codebase-scan)

## Checks for your own systems

Your ticks stay on this page. Inth does not save or send them.

### In the repository

- [ ] List every tag and pixel that can load on portal login, form and appointment pages.
- [ ] Confirm URL parameters and form fields are not passed to Meta, Google or other ad/analytics tools on those pages.

### In the browser and network

- [ ] Open appointment scheduling and a public form in a clean browser; confirm no requests go to Meta, Google Ads or similar domains before consent.
- [ ] Follow the public link into the patient portal and record what loads on the first portal page.

### With the people responsible

- [ ] Get a current inventory of every analytics and advertising tool on the hospital domains.
- [ ] Agree which routes are sensitive and who must approve adding a tag to them.

## Sources and limits

- [Settlement website](https://www.emanateprivacysettlement.com/) and [FAQ](https://www.emanateprivacysettlement.com/faqs/) (opened 6 November 2026)
- [Order granting preliminary approval (PDF)](https://www.emanateprivacysettlement.com/wp-content/uploads/2026/06/Order-Granting-Motion-for-Preliminary-Approval.pdf) (opened; form labeled proposed, with filled dates 1 June 2026 and 19 November 2026 hearing)
- [ClassAction.org settlement notice](https://www.classaction.org/news/777k-emanate-health-medical-center-settlement-ends-class-action-over-alleged-use-of-third-party-tracking-pixels)

The FAQ, settlement home page and preliminary approval order PDF were opened. The PDF is still captioned as a proposed order; hearing and fund figures are taken from the FAQ and site, which treat the 19 November 2026 hearing as set. The full settlement agreement text beyond the FAQ summary was not opened. Class size is not stated.

Source review: 6 November 2026. This page describes the cited record and procedural stage. It does not audit the company's current systems. Inth wrote the technical checks; they cannot decide which laws apply or prove compliance.

## Related cases

[Every case in the Enforcement library](/enforcement)