Clustered 2 filings across 2 jurisdictions · filing window Dec 22, 2023 → Jan 5, 2024. View entity profile → Other incidents for this victim →
incident inc_78609e32b489434e · 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.
PHI · Health (basic) · Identity (basic)
NH NY
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 17, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 30, 2023
Reported by NEW HAMPSHIRE AG filing
NYC Health + Hospitals reported to HHS on 2023-12-22 a Unauthorized Access/Disclosure affecting 3000 individuals. Breached information located on Desktop Computer, Paper/Films. An employee allowed a volunteer to view PHI (names, DOB, lab results). The entity notified HHS, individuals, and media, sanctioned the employee, and retrained staff.
Affected (this filing): 3,000
UKG, a workforce management provider, disclosed that on April 17, 2023, an employee inadvertently saved a file containing personal information of New York City Health + Hospitals employees to a shared folder. This file was copied to five other customer environments for training. UKG discovered the incident on October 30, 2023. Approximately 3 New Hampshire residents were affected. UKG deleted the file, notified customers, and offered credit monitoring.
Affected (this filing): 3
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.