All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed9 filings · 8 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 9 filings

Partnership HealthPlan of California — March 2022 breach

Clustered 9 filings across 8 jurisdictions · filing window May 18, 2022 → May 23, 2022. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

Affected · reported

854,913

First → last filing

May 18, 2022 → May 23, 2022

Merge confidence

100%

incident inc_1abf495f11024771 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Mar 19, 2022, discovered Mar 19, 2022 — the first regulatory filing landed 60 days later. 854,913 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 5 more. Notifications rolled out on a 5-day schedule across 9 filings beginning May 18, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

60days

Discovered → first regulatory filing

Discovery variance

45days

Range of discovered_at dates across filings

Filing span

5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington⏱ WA AG >30dHIPAA✓ HHS notifiedCalifornia✓ CA 60-day OK · 60dMaine✓ ME AG ≤30d · 15dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Mar 19, 2022breach begins

Mar 19, 2022discovered · members disagree

notification delay · 60 days

May 18, 2022first filing

May 23, 2022most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

MAY 18HHS OCRHHS OCR noticefirst filing · states nationwide total 852,375auto-linkedday 0
MAY 18WA AGWA AG notice1,352 WA residentsday 0
MAY 18IN AGIN AG noticestates nationwide total 854,913auto-linkedday 0
MAY 18CA AGCA AG noticeno count statedoperator-confirmedday 0
MAY 18OR AGOR AG noticestates nationwide total 854,913operator-confirmedday 0
MAY 18MT AGMT AG notice242 MT residentsoperator-confirmedday 0
MAY 18ME AGME AG noticestates nationwide total 854,913operator-confirmedday 0
MAY 18MA AGMA AG notice144 MA residentsauto-linkedday 0
MAY 23NH AGNH AG noticemost recent · 44 NH residentsauto-linked+5d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 19, 2022
Discovered: Mar 19, 2022WA AG + CA AG + MT AG +1May 3, 2022ME AGfilings disagree on discovery
Data types: Authentication · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Ransomware

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

854,913

Sum of filed state slices

2,069· 0.2% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US854,913

WA1,352

MT242

IN203

MA144

ME84

NH44

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

5 days

Cadence

~1 / 0.6d

vs. multi-state median

1.6× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.