Clustered 3 filings across 2 jurisdictions · filed Jun 28, 2021. View entity profile → Other incidents for this victim →
incident inc_427cc9a9e3264138 · 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.
MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 26, 2021
When the intrusion reportedly occurred, per the linked filings
Apr 26, 2021
Reported by WASHINGTON AG filing
Ankle and Foot Physicians and Surgeons PLLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-06-28. The breach occurred on 4/26/2021. 1 Montana residents were affected.
Affected (this filing): 1
Ankle and Foot Physicians and Surgeons PLLC (WA) reported to HHS OCR on 2021-06-28 a ransomware attack affecting ePHI on a network server for 5,244 individuals. Exposed data included names and dates of birth. The CE notified HHS, affected individuals, the media, and local law enforcement, posted substitute notice on its website, hired a new IT provider, implemented additional safeguards, and retrained staff.
Affected (this filing): 5,244
Ankle and Foot Physicians and Surgeons, PLLC, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2021-04-26 and filed notice on 2021-06-28. 4,996 Washington residents were affected. 63 days elapsed between awareness and notification. 1 days to identify the breach.
Affected (this filing): 4,996
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.