Clustered 4 filings across 4 jurisdictions · filed Oct 17, 2025. View entity profile → Other incidents for this victim →
incident inc_2a04be71b5ce4439 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
FL MT NH VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 9, 2025
When the intrusion reportedly occurred, per the linked filings
Jul 21, 2025
Reported by NEW HAMPSHIRE AG, VERMONT AG filings
Modernizing Medicine, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2025-10-17. The breach occurred from 07/09/2025 to 07/10/2025. 22 Montana residents were affected.
Affected (this filing): 22
Modernizing Medicine, Inc. notified the NH AG of a data security event affecting 162 NH residents. Unauthorized access occurred July 9-10, 2025; detected July 21, 2025. Data included PHI, SSNs, and PII. ModMed engaged forensic investigators and law enforcement, enhanced security controls, and offered credit monitoring.
Affected (this filing): 162
Modernizing Medicine, Inc. reported to HHS on 2025-10-17 a Hacking/IT Incident affecting 198,795 individuals. Breached information located on Network Server. Business Associate present.
Affected (this filing): 198,795
Modernizing Medicine, Inc. (ModMed) disclosed a data breach affecting podiatry providers and patients. Unauthorized access occurred July 9-10, 2025, involving personal, health, and government ID data. ModMed engaged forensic investigators and law enforcement, enhanced security controls, and offered credit monitoring. No financial account data was compromised.
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.