Clustered 3 filings across 3 jurisdictions · filed Mar 9, 2021. View entity profile → Other incidents for this victim →
incident inc_055f3d47853642f0 · 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.
Health (basic) · Identity (basic) · Government ID
FEDERAL ME MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 30, 2020
When the intrusion reportedly occurred, per the linked filings
Feb 16, 2021
Reported by MAINE AG filing
The New London Hospital Association, Inc. reported a cyber-attack to HHS on March 9, 2021, affecting 34,878 patients. The breach occurred on a network server and involved electronic protected health information (ePHI), including names, addresses, dates of birth, and Social Security numbers. The hospital has since implemented additional administrative and technical safeguards.
Affected (this filing): 34,878
The New London Hospital Association, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-09. The breach occurred on 7/30/2020. 11 Montana residents were affected.
Affected (this filing): 11
On July 30, 2020, The New London Hospital Association, Inc. experienced an external system breach. The incident was discovered on February 16, 2021. The breach affected 34,878 individuals, compromising their names and Social Security numbers. Affected individuals were notified on March 9, 2021, and offered one year of credit monitoring services through Experian.
Affected (this filing): 34,878
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.