Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
986
Data types
3
Health (basic) · Identity (basic) · Financial account
Jurisdictions
2
IL IN
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 19, 2024
When the intrusion reportedly occurred, per the linked filings
116 days
🏎️Indiana State AGFirst filinglinked via same-victim cross-source · 100%
Thrive Physical Therapy Partners reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-19 and was reported on 2025-04-14. 1 Indiana residents were affected. 22 individuals affected in total.
Affected (this filing): 22
🇺🇸ILHHS OCRMost recentlinked via same-victim cross-source · 100%
Thrive Physical Therapy Partners (a Business Associate, IL) reported to HHS on 2025-04-16 a Hacking/IT Incident affecting 986 individuals. An employee was the target of an email phishing scheme that compromised PHI including demographic, clinical, and financial information. Breached information was located in Email. The BA notified HHS, impacted individuals, and the media, and implemented additional administrative, technical, and security safeguards. OCR provided technical assistance regarding the HIPAA Rules.
Affected (this filing):
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.