Clustered 2 filings across 2 jurisdictions · filing window Nov 22, 2024 → Nov 25, 2024. View entity profile → Other incidents for this victim →
incident inc_b42ec6d8b33549f9 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
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.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 3, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 8, 2024
Reported by NEW HAMPSHIRE AG filing
Sep 27, 2024
Reported by MAINE AG filing
OnePoint Patient Care, a healthcare organization, reported a data breach to the Maine Attorney General. The breach, which occurred on August 3, 2024, was discovered on September 27, 2024, and was described as an external system breach or hacking incident. The breach affected 99 Maine residents. In response, the company offered 12 months of credit monitoring services through Experian.
Affected (this filing): 99
OnePoint Patient Care reported a data security incident to the New Hampshire Attorney General. On August 8, 2024, OPPC detected suspicious activity and determined an unauthorized third party accessed its network between August 3-8, 2024. The incident affected 843 New Hampshire residents, exposing personal information including names, addresses, medical record numbers, diagnoses, and prescription data. OPPC engaged forensic experts, notified law enforcement, and offered one year of credit monitoring.
Affected (this filing): 843
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.