Clustered 3 filings across 2 jurisdictions · filed Jun 14, 2022. View entity profile → Other incidents for this victim →
incident inc_696f72d6da834afa · merge_method human · 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.
MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 4, 2021
When the intrusion reportedly occurred, per the linked filings
Apr 15, 2022
Reported by WASHINGTON AG filing
Sight Partners Physicians PC reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-14. The breach occurred from 12/4/2021 to 12/5/2021. 86 Montana residents were affected.
Affected (this filing): 86
Sight Partners Physicians, P.C., a health sector entity reported a unclear/unknown incident to the Washington Attorney General. The organization became aware of the incident on 2022-04-15 and filed notice on 2022-06-14. 83,848 Washington residents were affected. 60 days elapsed between awareness and notification. 132 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 83,848
Sight Partners Physicians, P.C. reported to HHS on 2022-06-14 a Hacking/IT Incident affecting 86,101 individuals. Breached information located on Electronic Medical Record. The web description notes a ransomware attack on a business associate (Howard University College of Dentistry) involving dental records, dates of service, and health insurance information. The entity implemented additional administrative, technical, and security safeguards.
Affected (this filing): 86,101
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.