Clustered 3 filings across 3 jurisdictions · filed Feb 27, 2026. View entity profile → Other incidents for this victim →
incident inc_0830e07652414256 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
PII
AL IN ME
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 5, 2024 → Jul 15, 2024
When the intrusion reportedly occurred, per the linked filings
Jan 27, 2026
Reported by MAINE AG filing
Jackson Hospital and Clinic (Montgomery, AL) reported unauthorized access to the network of former vendor Nationwide Recovery Services occurring July 5-15, 2024. Jackson Hospital's own systems were not affected. The incident was discovered ~January 27, 2026. One Maine resident was among 14,485 total affected. Experian IdentityWorks (12 months) was offered to affected individuals.
Affected (this filing): 1
Jackson Hospital and Clinic reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-05 and was reported on 2026-02-27. 6 Indiana residents were affected. 14,485 individuals affected in total.
Affected (this filing): 14,485
Jackson Hospital and Clinic (AL) reported to HHS OCR on 2026-02-27 a Hacking/IT Incident affecting 13,910 individuals. Breached information was located on a Network Server. A business associate was present. No further details were provided in the web description.
Affected (this filing): 13,910
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.