Clustered 3 filings across 3 jurisdictions · filed Nov 14, 2023. View entity profile → Other incidents for this victim →
incident inc_45639ef6f4484dfd · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
ME MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 1, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 15, 2023
Reported by MAINE AG filing
Endocrine and Psychiatry Center reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-14. The breach occurred from 3/1/2023 to 3/20/2023. 2 Montana residents were affected.
Affected (this filing): 2
Endocrine and Psychiatry Center reported an external system breach (hacking) that was discovered on October 15, 2023, having occurred sometime prior to March 20, 2023. The breach affected 28,531 individuals, compromising names and financial account or card numbers with their security codes. The organization began notifying affected individuals on November 14, 2023, and offered 12 months of complimentary credit monitoring services through Equifax for those whose Social Security numbers were impacted.
Affected (this filing): 28,531
Endocrine and Psychiatry Center reported to HHS on 2023-11-14 a Hacking/IT Incident affecting 28,531 individuals. Breached information located on Network Server. The incident involved PHI including names, DOB, SSN, driver's license, and diagnoses. The entity offered credit monitoring and implemented security safeguards.
Affected (this filing): 28,531
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.