OnePoint Patient Care — August 2024 breach
Clustered 16 filings across 11 jurisdictions · filing window Aug 6, 2024 → Feb 6, 2025. View entity profile → Other incidents for this victim →
incident inc_afaf75a9425b480e · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 6Leak siteinc_ransom postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
- SEP 12Leak siteinc_ransom postattacker claim · unverifiedoperator-confirmed+38d
- OCT 1IL AGIL AG noticeno count statedauto-linked+56d
- OCT 14HHS OCRHHS OCR noticestates nationwide total 1,741,152operator-confirmed+69d
- OCT 23WA AGWA AG notice34,394 WA residents+78d
- OCT 23MT AGMT AG notice3,902 MT residentsauto-linked+78d
- OCT 23CA AGCA AG noticeno count statedauto-linked+78d
- OCT 23MA AGMA AG notice34,518 MA residentsoperator-confirmed+78d
- OCT 23OR AGOR AG noticestates nationwide total 795,916auto-linked+78d
- NOV 22OR AGOR AG noticestates nationwide total 1,741,152auto-linked+108d
- NOV 22CA AGCA AG noticeno count statedauto-linked+108d
- NOV 22ME AGME AG noticestates nationwide total 1,741,152auto-linked+108d
- NOV 25SC AGSC AG notice1,623 SC residentsauto-linked+111d
- NOV 25NH AGNH AG notice843 NH residentsauto-linked+111d
- FEB 6CA AGCA AG noticeno count statedauto-linked+184d
- FEB 6OR AGOR AG noticemost recent · states nationwide total 93,672auto-linked+184d
- 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 WA 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.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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
184 days
Cadence
~1 / 12.3d
vs. multi-state median
23.0× 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.