NextGen Healthcare provides customized solutions to fit the exact needs of ambulatory practices. Our solutions empower patients to take control of their health and enable clinicians to be more productive and engaged.
Clustered 2 filings across 2 jurisdictions · filing window Jan 17, 2023 → May 4, 2023. View entity profile → Other incidents for this victim →
incident inc_ff6fff119a2949d9 · merge_method human · confidence 100%
Discovered → first regulatory filing
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.
Identity (basic) · Government ID · Health (basic)
SC
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
NextGen Healthcare provides customized solutions to fit the exact needs of ambulatory practices. Our solutions empower patients to take control of their health and enable clinicians to be more productive and engaged.
Jan 28, 2023
When the intrusion reportedly occurred, per the linked filings
Jan 28, 2023
Reported by SOUTH CAROLINA AG filing
NextGen Healthcare, Inc. reported a cybersecurity incident in January 2023 involving a BlackCat ransomware attack. The breach was facilitated by stolen client credentials, allowing unauthorized access to systems. Over 1.04 million patient records were affected, exposing PHI, names, DOBs, and SSNs. NextGen engaged forensic investigators, notified law enforcement, and offered credit monitoring to affected individuals.
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): 1,049,375