Family Practice Center PC reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-07. The breach occurred on 10/11/2021. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filing window Jul 7, 2022 → Jul 11, 2022. View entity profile → Other incidents for this victim →
incident inc_ff3d76ce3b3648b3 · 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.
Health (basic) · Identity (basic) · Government ID
MT PA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 11, 2021
When the intrusion reportedly occurred, per the linked filings
Family Practice Center PC reported a data breach to the Montana Attorney General. The breach was reported on 2022-07-07. The breach occurred on 10/11/2021. 3 Montana residents were affected.
Affected (this filing): 3
Family Practice Center PC (Pennsylvania) reported to HHS OCR on 2022-07-11 a ransomware incident affecting 83,969 individuals. Breached information was located on a network server. PHI involved included names, addresses, dates of birth, Social Security numbers, diagnoses, and other treatment information. The entity notified HHS, affected individuals, the media, and posted substitute notice on its website. Additional administrative, technical, and security safeguards were implemented. OCR provided HIPAA technical assistance.
Affected (this filing): 83,969
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.