DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

REGIONAL CARE OF ROGERS, LLC — September 2024 breach

Clustered 9 filings across 9 jurisdictions · filing window Dec 1, 2024 → Dec 17, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

225,728

First → last filing

Dec 1, 2024 → Dec 17, 2024

Merge confidence

100%

incident inc_2d7972805f844530 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Sep 13, 2024–Sep 18, 2024, discovered Sep 18, 2024 — the first regulatory filing landed 74 days later (flagged late). 225,728 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 3 more. Notifications rolled out on a 16-day schedule across 9 filings beginning Dec 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
74days

Discovered → first regulatory filing

Discovery variance
51days

Range of discovered_at dates across filings

Filing span
16days

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 clocksVermont✗ VT AG >45 bdayWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 38dMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 13, 2024breach begins
Sep 18, 2024discovered · members disagree
notification delay · 74 days
Dec 1, 2024first filing
Dec 17, 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. DEC 1IL AGIL AG noticefirst filing · no count statedday 0
  2. DEC 16MA AGMA AG notice1,139 MA residents+15d
  3. DEC 16WA AGWA AG notice1,580 WA residents+15d
  4. DEC 16CA AGCA AG noticeno count stated+15d
  5. DEC 16ME AGME AG noticestates nationwide total 225,728+15d
  6. DEC 16VT AGVT AG noticeno count stated+15d
  7. DEC 16MT AGMT AG notice2,890 MT residents+15d
  8. DEC 16NH AGNH AG notice177 NH residents+15d
  9. DEC 17HHS OCRHHS OCR noticemost recent · states nationwide total 225,728+16d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 13, 2024 – Sep 18, 2024
WA AG
Discovered
Sep 18, 2024IL AG + WA AG + CA AG +3Nov 8, 2024ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MA AG + WA AG + CA AG +5
Attack vector
Phishing
WA 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)

225,728

Sum of filed state slices

5,931· 2.6% of stated

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

US225,728
MT2,890
WA1,580
MA1,139
NH177
ME145

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

16 days

Cadence

~1 / 2d

vs. multi-state median

2.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.