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 claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
12,306
Data types
4
Government ID · Identity (basic) · Financial account
Jurisdictions
2
NH TN
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach discovered
Sep 14, 2021
Reported by NEW HAMPSHIRE AG filing
44 days
🇺🇸TNHHS OCRFirst filinglinked via same-victim cross-source · 100%
Professional Healthcare Management, Inc. reported to HHS on 2021-10-28 a Hacking/IT Incident affecting 12306 individuals. Breached information located on Network Server. The incident involved a ransomware attack compromising PHI including names, DOBs, addresses, SSNs, and diagnoses.
Affected (this filing): 12,306
HHS notified
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Professional Healthcare Management, Inc. (PHM) notified the New Hampshire Attorney General of a ransomware attack discovered on September 14, 2021. The incident affected 3 New Hampshire residents. PHM engaged forensic experts, secured systems, and provided credit monitoring. Potentially impacted data included names, SSNs, health insurance info, and financial account numbers. No evidence of misuse was found.
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.