Clustered 3 filings across 3 jurisdictions · filing window Oct 2, 2020 → Nov 20, 2020. View entity profile → Other incidents for this victim →
incident inc_0121cc5dc4f8471b · merge_method deterministic · confidence 100%
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.
ME MT OH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 5, 2020
When the intrusion reportedly occurred, per the linked filings
Premier Health Partners reported a data breach to the Montana Attorney General. The breach was reported on 2020-10-02. The breach occurred from 5/5/2020 to 6/16/2020. 16 Montana residents were affected.
Affected (this filing): 16
Premier Health Partners reported to HHS on 2020-10-02 a Unauthorized Access/Disclosure affecting 254,786 individuals. Breached information located on Email. Employees were victims of an email phishing attack exposing ePHI including names, addresses, DOB, driver's license numbers, SSNs, claims, financial info, and diagnosis/treatment data. The entity implemented additional administrative, technical, and security safeguards.
Affected (this filing): 254,786
Nov 6, 2020
Reported by MAINE AG filing
Premier Health Partners reported a data breach affecting one Maine resident. The breach, which occurred between May 5, 2020, and June 16, 2020, was discovered on November 6, 2020. The compromised information included names and Social Security numbers. The company offered 12 months of credit monitoring and identity restoration services through CyberScout to those affected.
Affected (this filing): 1
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.