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

Cardiology Associates of Mobile — October 2024 breach

Clustered 6 filings across 6 jurisdictions · filing window Dec 3, 2024 → Jan 10, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

172,678

First → last filing

Dec 3, 2024 → Jan 10, 2025

Merge confidence

100%

incident inc_9df2bd8b21134621 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe unauthorized access. Intrusion Oct 18, 2024–Oct 22, 2024, discovered Oct 22, 2024 — the first regulatory filing landed 42 days later. 172,678 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 38-day schedule across 6 filings beginning Dec 3, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
16days

Range of discovered_at dates across filings

Filing span
38days

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 clocksMaine✓ ME AG ≤30d · 26dHIPAA✓ HHS report on timeMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 18, 2024breach begins
Oct 22, 2024discovered · members disagree
notification delay · 42 days
Dec 3, 2024first filing
Jan 10, 2025most 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 3ME AGME AG noticefirst filing · states nationwide total 1,514day 0
  2. DEC 19HHS OCRHHS OCR noticestates nationwide total 172,678+16d
  3. JAN 8NE AGNE AG noticeno count stated+36d
  4. JAN 10MA AGMA AG notice37 MA residents+38d
  5. JAN 10MT AGMT AG notice17 MT residents+38d
  6. JAN 10NH AGNH AG noticemost recent · 10 NH residents+38d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 18, 2024 – Oct 22, 2024
ME AG
Discovered
Oct 22, 2024NE AG + MT AG + NH AGNov 7, 2024ME AG + HHS OCRfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
ME AG + HHS OCR + NE AG +3
Attack vector
Unauthorized Access
ME 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)

172,678

Sum of filed state slices

65· 0.0% of stated

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

US172,678
MA37
MT17
NH10
ME1

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 filing6 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
Reviewed
operator-reviewed Jun 12, 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

38 days

Cadence

~1 / 7.6d

vs. multi-state median

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