Clustered 3 filings across 3 jurisdictions · filing window May 10, 2024 → Jun 6, 2024. View entity profile → Other incidents for this victim →
incident inc_f2ca2d3e64de4009 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
Identity (basic)
CT IN ME
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 26, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 26, 2024
Reported by MAINE AG, HHS OCR filings
Best Health Physical Therapy reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-26 and was reported on 2024-05-10. 1 Indiana residents were affected. 3,764 individuals affected in total.
Affected (this filing): 3,764
Best Health Physical Therapy LLC, a healthcare organization, reported a ransomware incident that occurred and was discovered on February 26, 2024. The breach affected 18 Maine residents. The company provided written notification to the affected individuals on May 10, 2024, and offered 12 months of credit monitoring and identity theft protection services through CyEx.
Affected (this filing): 18
Best Health Physical Therapy, LLC (CT) reported to HHS on 2024-06-06 a Hacking/IT Incident affecting 3,764 individuals. Breached information was located on a Network Server and other systems. PHI compromised included names, dates of birth, drivers' license numbers, and medical information. The CE notified HHS, affected individuals, and the media, and offered credit monitoring and identity protection services while implementing additional technical safeguards.
Affected (this filing): 3,764
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.