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

Confirmed5 records · 3 statesUnverified claimConfirmedEnforcedmedusahigh sensitivity

Merged incident · 5 records

Mt. Carmel Care Center — August 2023 breach

Clustered 5 records across 3 jurisdictions: 4 filings and 1 leak-site claim · filing window Dec 14, 2023 → Aug 26, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

Affected · reported

2,375

First → last filing

Dec 14, 2023 → Aug 26, 2024

Merge confidence

100%

incident inc_681d577b698d4959 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 17, 2023–Oct 15, 2023, discovered Jun 6, 2024. 2,375 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 256-day schedule across 4 filings beginning Dec 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Leak precedence

44days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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

256days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 17, 2023breach begins

Jun 6, 2024discovered

Dec 14, 2023first filing

Aug 26, 2024most recent filing

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

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

OCT 31Leak sitemedusa postfirst record · attacker claim · unverifiedoperator-confirmedday 0
DEC 14HHS OCRHHS OCR noticestates nationwide total 1,430operator-confirmed+44d
AUG 26ME AGME AG noticestates nationwide total 2,375+300d
AUG 26VT AGVT AG noticeno count statedoperator-confirmed+300d
AUG 26MA AGMA AG noticemost recent · 1,539 MA residentsauto-linked+300d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 17, 2023 – Oct 15, 2023
Discovered: Jun 6, 2024· 294d undetected
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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)

2,375

Sum of filed state slices

1,541· 64.9% of stated

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

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 filing4 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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Oct 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

256 days

Cadence

~1 / 85.3d

vs. multi-state median

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