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 clocksMaine⏱ ME AG >30d · 33dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
10,848
Data types
1
Government ID
Jurisdictions
2
ME NY
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 9, 2022
When the intrusion reportedly occurred, per the linked filings
75 days
Breach discovered
Sep 22, 2022
Reported by MAINE AG filing
32 days
🗽NEW YORKHHS OCRFirst filinglinked via same-victim cross-source · 100%
Somnia Pain Management of Kentucky reported to HHS on 2022-10-24 a Hacking/IT Incident affecting 10848 individuals. Breached information located on Network Server. The entity experienced a ransomware attack compromising medical records. The case has been closed.
Affected (this filing): 10,848
🦞Maine State AGMost recentlinked via same-victim cross-source · 100%
Somnia Pain Mgt of Kentucky reported a data breach to the Maine Attorney General, affecting one resident. The breach, which was an external system breach (hacking), occurred on July 9, 2022, and was discovered on September 22, 2022. The compromised information includes names in combination with Driver's License or Non-Driver Identification Card Numbers. The company offered 12 months of credit monitoring and identity protection services to those affected.
Affected (this filing): 1
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.