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

Confirmed15 records · 8 statesUnverified claimConfirmedEnforcedkarakurthigh sensitivity

Merged incident · 15 records

The Chattanooga Heart Institute — March 2023 breach

Clustered 15 records across 8 jurisdictions: 14 filings and 1 leak-site claim · filing window Jul 12, 2023 → Mar 28, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

15 records

States

Affected · reported

547,434

First → last dated filing

Jul 12, 2023 → Mar 28, 2024

Merge confidence

100%

incident inc_1b6cfd019d9d4b79 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 8, 2023–Mar 16, 2023, discovered Mar 8, 2023. 547,434 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 5 more. Notifications rolled out on a 260-day schedule across 13 dated filings beginning Jul 12, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

84days

Range of discovered_at dates across filings

Filing span

260days

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 clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 58dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 8, 2023breach begins

Mar 8, 2023discovered · members disagree

Jul 12, 2023first dated filing

Mar 28, 2024most 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

JAN 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
MAY 23Leak sitekarakurt postfirst record · attacker claim · unverifiedoperator-confirmedday 0
JUL 12MA AGMA AG notice8 MA residentsoperator-confirmed+50d
JUL 28HHS OCRHHS OCR noticestates nationwide total 545,491operator-confirmed+66d
JUL 28ME AGME AG noticestates nationwide total 170,450operator-confirmed+66d
JUL 28MT AGMT AG notice33 MT residentsoperator-confirmed+66d
JUL 28IN AGIN AG noticestates nationwide total 170,450auto-linked+66d
JUL 28NH AGNH AG noticeno count statedoperator-confirmed+66d
OCT 6ME AGME AG noticestates nationwide total 411,383operator-confirmed+136d
OCT 6VT AGVT AG noticeno count statedoperator-confirmed+136d
OCT 6NH AGNH AG notice15 NH residentsoperator-confirmed+136d
FEB 13ME AGME AG noticestates nationwide total 413,236operator-confirmed+266d
MAR 27VT AGVT AG noticeno count statedoperator-confirmed+309d
MAR 28ME AGME AG noticestates nationwide total 547,434+310d
MAR 28NH AGNH AG noticemost recent · no count statedauto-linked+310d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 8, 2023
Discovered: Mar 8, 2023IL AGApr 17, 2023MT AG + NH AG + VT AGMay 31, 2023ME AGfilings disagree on discovery
Data types: Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
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)

547,434

Sum of filed state slices

316· 0.1% of stated

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

US547,434

IN207

ME53

MT33

NH15

MA8

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

260 days

Cadence

~1 / 21.7d

vs. multi-state median

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