Clay Platte Family Medicine, Summit Family and Sports Medicine Clinic, Cobblestone Family Medicine Clinic, and Barry Pointe Family Medicine Clinic data breach (2024) · DisclosureLens
Confirmed breach. Intrusion Jun 26, 2024, discovered Jun 26, 2024 — the first regulatory filing landed 114 days later. 12 individuals reported across the linked filings.
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.
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
12
Data types
—
Jurisdictions
2
MT NH
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 26, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Jun 26, 2024
Reported by NEW HAMPSHIRE AG filing
114 days
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Clay Platte Family Medicine and affiliated clinics detected unauthorized network access on June 26, 2024. An actor accessed and acquired files containing PHI and basic identity data. Four New Hampshire residents were affected. Notices were mailed October 16, 2024, offering credit monitoring. The incident is contained.
Clay Platte Family Medicine, Summit Family and Sports Medicine Clinic, Cobblestone Family Medicine Clinic, and Barry Pointe Family Medicine Clinic reported a data breach to the Montana Attorney General. The breach was reported on 2024-10-18. The breach occurred on 6/26/2024. 8 Montana residents were affected.
Affected (this filing): 8
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.