Confirmed breach. Intrusion Dec 24, 2023, discovered Dec 24, 2023 — the first regulatory filing landed 45 days later. 31,125 individuals reported across the linked filings.
Washington County Hospital and Nursing Home reported a data breach to the Indiana Attorney General. The breach occurred on 2023-12-24 and was reported on 2024-02-07. 17 Indiana residents were affected. 31,125 individuals affected in total.
Affected (this filing): 31,125
🇺🇸ALHHS OCRlinked via same-victim cross-source · 100%
Washington County Hospital and Nursing Home (AL) reported to HHS on 2024-02-22 a ransomware attack affecting 29,346 individuals. PHI on network servers was compromised, including names, Social Security numbers, dates of birth, diagnoses/conditions, lab results, medications, and other treatment information. The entity notified HHS, affected individuals, and media, provided substitute notice, and offered complimentary credit monitoring. Additional administrative, technical, and security safeguards were implemented.
Affected (this filing): 29,346
🦞Maine State AGlinked via same-victim cross-source · 100%
Washington County Hospital and Nursing Home, a healthcare provider, experienced an external system breach on December 24, 2023. The breach was discovered on the same day and affected 5 Maine residents. The compromised information included names and Social Security numbers. The company provided 12 months of credit monitoring and identity theft protection services through Cyberscout.
Washington County Hospital and Nursing Home reported a data breach to the Montana Attorney General. The breach was reported on 2024-02-23. The breach occurred on 12/24/2023. 2 Montana residents were affected.
Affected (this filing): 2
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.