Confirmed breach. Intrusion May 21, 2025–May 24, 2025, discovered May 22, 2025 — the first regulatory filing landed 271 days later. 28,967 individuals reported across the linked filings.
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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
28,967
Data types
1
Health (basic)
Jurisdictions
2
GA NH
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 21, 2025 → May 24, 2025
When the intrusion reportedly occurred, per the linked filings
Emanuel Medical Center (GA) reported to HHS Office for Civil Rights on 2026-02-17 a Hacking/IT Incident affecting 28,963 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further detail is available from the HHS web description.
Affected (this filing): 28,963
HHS notified
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Emanuel Medical Center, a Georgia-based healthcare provider, notified the New Hampshire Attorney General of a ransomware incident affecting 4 NH residents. Unauthorized access occurred May 21-24, 2025; detected May 22, 2025. Exposed data included names, SSNs, DOBs, and PHI. Notices mailed Feb 17, 2026. Response included forensic investigation, credential resets, server rebuilds, and credit monitoring offers.
Affected (this filing): 4
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.