DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed5 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedembargohigh sensitivity
Merged incident · 5 records

Heart of America Medical Centr (HAMC) — May 2025 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window Jul 1, 2025 → Aug 4, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

4

Affected · reported

29,446

First → last filing

Jul 1, 2025 → Aug 4, 2026

Merge confidence

100%

incident inc_9b8251ab8ee44a46 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion May 7, 2025, discovered Jun 12, 2025 — the first regulatory filing landed 19 days later; 1 later filing was flagged late. 29,446 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 2 more. Notifications rolled out on a 399-day schedule across 4 filings beginning Jul 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
19days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 36d

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMassachusetts✗ MA AG >90dLeak gap✗ Leak >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 7, 2025breach begins
Jun 12, 2025discovered
notification delay · 19 days
Jul 1, 2025first filing
Aug 4, 2026most 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

  1. JUL 1HHS OCRHHS OCR noticefirst filing · 29,430 ND residentsday 0
  2. JUL 17Leak siteembargo postattacker claim · unverified+17d
  3. AUG 1MA AGMA AG notice14 MA residents+396d
  4. AUG 3NH AGNH AG notice2 NH residents+398d
  5. AUG 4IN AGIN AG noticemost recent · states nationwide total 29,430+399d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 7, 2025
IN AG
Discovered
Jun 12, 2025· 36d undetected
MA AG + NH AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MA AG + NH AG
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)

29,430

Sum of filed state slices

48· 0.2% of stated

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

US29,430
IN32
MA14
NH2

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

399 days

Cadence

~1 / 133d

vs. multi-state median

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