DisclosureLens
HHS OCRState AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Alabama Cardiovascular Group — June 2024 breach

Clustered 4 filings across 4 jurisdictions · filing window Aug 1, 2024 Aug 2, 2024. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

280,534

First → last filing

Aug 1, 2024 Aug 2, 2024

Merge confidence

100%

incident inc_4a8cc2f1588644fe · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes unauthorized access. Intrusion Jun 6, 2024, discovered Jun 6, 2024 — the first regulatory filing landed 56 days later. 280,534 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
56days

Discovered → first regulatory filing

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMassachusetts MA credit monitoring dueHIPAA HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 6, 2024breach begins
Jun 6, 2024discovered
notification delay · 56 days
Aug 1, 2024first filing
Aug 2, 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. AUG 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 2IN AGIN AG noticestates nationwide total 280,534+1d
  3. AUG 2MA AGMA AG notice27 MA residents+1d
  4. AUG 2HHS OCRHHS OCR noticemost recent · states nationwide total 280,534+1d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 6, 2024
IN AG
Discovered
Jun 6, 2024
IL AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
MA AG + HHS OCR
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)

280,534

Sum of filed state slices

122· 0.0% of stated

100% 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 claim

No leak-site claim on record for this incident.

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

1 days

Cadence

~1 / 0.3d

vs. multi-state median

8.0× faster

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.