DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed13 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 13 filings

Prospect Medical Holdings, Inc. — July 2023 breach

Clustered 13 filings across 9 jurisdictions · filing window Jan 1, 2023 → Mar 1, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

8

Affected · reported

not comparable

First → last filing

Jan 1, 2023 → Mar 1, 2024

Merge confidence

100%

incident inc_10a17db8b9f54dff · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Jul 31, 2023–Aug 31, 2023, discovered Aug 1, 2023. Data reported: Government ID, Identity (basic), PII, and 3 more. Notifications rolled out on a 425-day schedule across 12 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
43days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 235d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
425days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont⏱ VT AG >14 bdayCalifornia✓ CA 60-day OK · 59dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 31, 2023breach begins
Aug 1, 2023discovered · members disagree
Jan 1, 2023first filing
Mar 1, 2024most recent filing

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

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 24Leak siterhysida postattacker claim · unverified+235d
  3. SEP 29IN AGIN AG noticestates nationwide total 190,492+271d
  4. SEP 29MA AGMA AG notice649 MA residents+271d
  5. SEP 29MT AGMT AG notice243 MT residents+271d
  6. SEP 29NH AGNH AG notice73 NH residents+271d
  7. SEP 29ME AGME AG noticestates nationwide total 190,492+271d
  8. SEP 29VT AGVT AG noticeno count stated+271d
  9. SEP 29HHS OCRHHS OCR notice1,309,096 affected+271d
  10. SEP 29CA AGCA AG noticeno count stated+271d
  11. DEC 13CA AGCA AG noticeno count stated+346d
  12. FEB 29NH AGNH AG notice1,882 NH residents+424d
  13. MAR 1MA AGMA AG noticemost recent · 4,958 MA residents+425d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 31, 2023
IN AG
Discovered
Aug 1, 2023IL AG + MT AG + NH AG +2Sep 13, 2023ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + MT AG + NH AG +4
Attack vector
Unauthorized Access
MT AG

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)

190,492

Sum of filed state slices

7,155· 3.8% of stated

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

US190,492
MA4,958
NH1,882
MT243
ME67
IN5

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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 Aug 23, 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

425 days

Cadence

~1 / 35.4d

vs. multi-state median

53.1× slower

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.