Summit Pathology and Summit Pathology Laboratories, Inc. reported to HHS on 2024-10-18 a Hacking/IT Incident affecting 1813538 individuals. Breached information located on Network Server.
Affected (this filing): 1,813,538
Clustered 3 filings across 3 jurisdictions · filing window Oct 18, 2024 → Oct 23, 2024. View entity profile → Other incidents for this victim →
incident inc_ea577c06f78a4ed7 · 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.
CO NH WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 18, 2024
Reported by WASHINGTON AG filing
Summit Pathology and Summit Pathology Laboratories, Inc. reported to HHS on 2024-10-18 a Hacking/IT Incident affecting 1813538 individuals. Breached information located on Network Server.
Affected (this filing): 1,813,538
Summit Pathology & Summit Pathology Laboratories, Inc., a health sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2024-04-18 and filed notice on 2024-10-18. 3,250 Washington residents were affected. 183 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 3,250
State AG filing for Summit Pathology and Summit Pathology Laboratories, Inc. in New Hampshire. The attachment content is empty; no breach details, dates, or data types were extracted from the provided source.
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.