Starling Physicians reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-03. The breach occurred from 7/7/2020 to 10/7/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Sep 3, 2020 → Sep 4, 2020. View entity profile → Other incidents for this victim →
incident inc_1d47ce8c6fe44fb8 · 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.
CT MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 7, 2020
When the intrusion reportedly occurred, per the linked filings
Starling Physicians reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-03. The breach occurred from 7/7/2020 to 10/7/2020. 1 Montana residents were affected.
Affected (this filing): 1
Starling Physicians, PC (CT) reported to HHS on 2020-09-04 a Hacking/IT Incident affecting 7,777 individuals. Two employees were victims of an email phishing attack that exposed ePHI stored in email, including names, dates of birth, Social Security numbers, addresses, and health insurance and medical treatment information. The CE notified HHS, affected individuals, and the media, offered credit monitoring, and implemented additional technical safeguards and staff retraining. OCR obtained assurances that corrective actions were implemented.
Affected (this filing):
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.