Clustered 3 filings across 2 jurisdictions · filing window Jul 13, 2025 → Apr 14, 2026. View entity profile → Other incidents for this victim →
incident inc_b7e4ed8ae3fd4b5c · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
PII · PHI
ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 11, 2025
When the intrusion reportedly occurred, per the linked filings
Cookeville Regional Medical Center At Cookeville Regional Medical Center, we are dedicated to providing the highest quality care to our patients and making a positive impact on our community.
Cookeville Regional Medical Center At Cookeville Regional Medical Center, we are dedicated to providing the highest quality care to our patients and making a positive impact on our community.
Mar 16, 2026
Reported by MAINE AG filing
Cookeville Regional Medical Center (Cookeville, TN) reported an external system breach (hacking) to the Maine Attorney General. The incident occurred on 07/11/2025 and was discovered on 03/16/2026. A total of 337,917 individuals were affected, including 22 Maine residents. Written consumer notifications were sent on 04/14/2026, and 12 months of Experian identity theft protection services were offered. Notification was filed by Alexander Boyd of Polsinelli PC. The filing did not enumerate which specific data elements were acquired.
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.
Affected (this filing): 337,917