Henry County Hospital — December 2025 breach
Clustered 3 filings across 3 jurisdictions · filing window Oct 20, 2026 → Oct 28, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_9e771a6981e34f30 · merged by deterministic · confidence 95%
Litigation Timing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing about this breach
- OCT 1MA AGMA AG noticefiling day not on record · no count statedauto-linked—
- OCT 20NH AGNH AG noticefirst filing · 17 NH residentsday 0
- OCT 28TX AGTX AG noticemost recent · states nationwide total 63,562auto-linked+8d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Dec 2, 2025 – Dec 18, 2025 MA AG
- Discovered
- Dec 18, 2025MA AGJun 26, 2026NH AG + TX AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI MA AG + NH AG + TX AG
- Attack vector
- Unauthorized Access MA AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
63,562
Sum of filed state slices
977· 1.5% of stated
98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 0.95 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (95% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
8 days
vs. multi-state median
1.3× slower
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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.