Coastal Carolina Centers of Urology and Surgery, LLC reported to HHS on 2026-05-21 a Hacking/IT Incident affecting 2886 individuals. Breached information located on Network Server.
Affected (this filing): 2,886
Clustered 3 filings across 3 jurisdictions · filing window May 21, 2026 → May 22, 2026. View entity profile → Other incidents for this victim →
incident inc_4d1c0ec1526f4cf5 · 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.
PHI · Health (basic) · Identity (basic)
IN SC VT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 26, 2025
When the intrusion reportedly occurred, per the linked filings
Coastal Carolina Centers of Urology and Surgery, LLC reported to HHS on 2026-05-21 a Hacking/IT Incident affecting 2886 individuals. Breached information located on Network Server.
Affected (this filing): 2,886
Coastal Carolina Centers of Urology and Surgery LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-26 and was reported on 2026-05-21. 2 Indiana residents were affected. 2,886 individuals affected in total.
Affected (this filing): 2,886
Coastal Carolina Centers of Urology and Surgery, LLC reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-05-22. The reporting organization type is Health Care. 1 Vermont residents were affected. Categories of data breached: Health Records.
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.