DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed15 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 15 records

OnePoint Patient Care — August 2024 breach

Clustered 15 records across 10 jurisdictions: 14 filings and 1 leak-site claim · filing window Oct 14, 2024 → Feb 6, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 records

States

10

Affected · reported

1,741,152

First → last dated filing

Oct 14, 2024 → Feb 6, 2025

Merge confidence

100%

incident inc_afaf75a9425b480e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. Intrusion Aug 3, 2024–Aug 8, 2024, discovered Aug 3, 2024. 1,741,152 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 115-day schedule across 13 dated filings beginning Oct 14, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
55days

Range of discovered_at dates across filings

Filing span
115days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 106dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 3, 2024breach begins
Aug 3, 2024discovered · members disagree
Oct 14, 2024first dated filing
Feb 6, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 6Leak siteinc_ransom postfirst record · attacker claim · unverifiedday 0
  2. OCT 1IL AGIL AG noticefiling day not on record · no count stated—
  3. OCT 14HHS OCRHHS OCR noticestates nationwide total 1,741,152+69d
  4. OCT 23OR AGOR AG noticestates nationwide total 795,916+78d
  5. OCT 23WA AGWA AG notice34,394 WA residents+78d
  6. OCT 23MT AGMT AG notice3,902 MT residents+78d
  7. OCT 23CA AGCA AG noticeno count stated+78d
  8. OCT 23MA AGMA AG notice34,518 MA residents+78d
  9. NOV 22OR AGOR AG noticestates nationwide total 1,741,152+108d
  10. NOV 22CA AGCA AG noticeno count stated+108d
  11. NOV 22ME AGME AG noticestates nationwide total 1,741,152+108d
  12. NOV 25SC AGSC AG notice1,623 SC residents+111d
  13. NOV 25NH AGNH AG notice843 NH residents+111d
  14. FEB 6CA AGCA AG noticeno count stated+184d
  15. FEB 6OR AGOR AG noticemost recent · states nationwide total 93,672+184d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 3, 2024 – Aug 8, 2024
OR AG
Discovered
Aug 3, 2024IL AGAug 8, 2024WA AG + MT AG + CA AG +3Sep 27, 2024OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + MT AG +5
Attack vector
Unauthorized Access
HHS OCR

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)

1,741,152

Sum of filed state slices

75,379· 4.3% of stated

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

US1,741,152
MA34,518
WA34,394
MT3,902
SC1,623
NH843
ME99

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 filing14 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

115 days

Cadence

~1 / 9.6d

vs. multi-state median

19.2× 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.