Clustered 4 filings across 4 jurisdictions · filing window Aug 13, 2024 → Nov 7, 2024. View entity profile → Other incidents for this victim →
incident inc_59d1584187504afd · merge_method human · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN MT TX
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 3, 2024
When the intrusion reportedly occurred, per the linked filings
Southwest Family Medicine Associates proudly offers a true one-stop shop medical home. The team at SFMA practices cutting-edge medicine that focuses on disease prevention and wellness. Our revolutionary Early Detect Program combines an annual wellness exam with early detection testing.
South West Family Medicine Associates, PA reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-07. The breach occurred from 7/3/2024 to 8/7/2024. 3 Montana residents were affected.
South West Family Medicine Associates PA reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-03 and was reported on 2024-11-07. 19 Indiana residents were affected. 36,959 individuals affected in total.
Affected (this filing): 36,959
Southwest Family Medicine Associates, PA (TX) reported to HHS on 2024-11-07 a ransomware incident affecting 36,959 individuals' PHI stored on a network server. Compromised information included demographic and clinical data. The CE notified HHS, affected individuals, and the media. In response to OCR's investigation, the CE revised policies and procedures, implemented additional technical safeguards, and retrained its workforce.
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.
Affected (this filing): 3
Affected (this filing): 36,959