Confirmed breach. Intrusion Jun 1, 2025–Aug 31, 2025, discovered Aug 1, 2025 — the first regulatory filing landed 314 days later. 896 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 claimConfirmedEnforcedlow sensitivity
Affected (total reported)
896
Data types
1
PII
Jurisdictions
2
NH TN
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 1, 2025 → Aug 31, 2025
When the intrusion reportedly occurred, per the linked filings
Open Arms Care Corporation, a healthcare provider in Tennessee, reported a hacking/IT incident on June 11, 2026, affecting 893 individuals. The breach involved unauthorized access to email information. No business associate was involved.
Affected (this filing): 893
HHS notified
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Open Arms Care Corporation (OAC) notified the New Hampshire Attorney General of a data security incident involving unauthorized access to an email account. The breach occurred between June and August 2025, discovered in August 2025. Three New Hampshire residents were affected, with data including names, SSNs, and driver's license information. OAC offered 12 months of credit monitoring and secured its email environment.
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.