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

Florida Heart Associates — May 2021 breach

Clustered 7 filings across 6 jurisdictions · filing window Jul 7, 2021 → Nov 8, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

45,148

First → last filing

Jul 7, 2021 → Nov 8, 2021

Merge confidence

100%

incident inc_118159ec8dce4dae · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. Intrusion May 9, 2021–May 19, 2021, discovered May 19, 2021 — the first regulatory filing landed 49 days later. 45,148 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 124-day schedule across 6 filings beginning Jul 7, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
49days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 124d

Days between the first leak-site claim and the first regulatory filing. 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
124days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 56dHIPAA✓ HHS report on timeFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 9, 2021breach begins
May 19, 2021discovered
notification delay · 49 days
Jul 7, 2021first filing
Jul 30, 2021most 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. JUL 7HHS OCRHHS OCR noticefirst filing · states nationwide total 45,148day 0
  2. JUL 13MA AGMA AG notice103 MA residents+6d
  3. JUL 13MT AGMT AG notice5 MT residents+6d
  4. JUL 14ME AGME AG notice39 affected+7d
  5. JUL 17IN AGIN AG noticestates nationwide total 45,148+10d
  6. JUL 30ME AGME AG notice39 affected+23d
  7. NOV 8Leak sitepysa postmost recent · attacker claim · unverified+124d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 9, 2021 – May 19, 2021
MT AG
Discovered
May 19, 2021· 10d undetected
HHS OCR + MT AG + ME AG
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MT AG + ME 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)

45,148

Sum of filed state slices

315· 0.7% of stated

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

US45,148
IN168
MA103
ME39
MT5

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

124 days

Cadence

~1 / 20.7d

vs. multi-state median

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