Clustered 3 filings across 3 jurisdictions · filed Sep 5, 2023. View entity profile → Other incidents for this victim →
incident inc_5e32b658c91246dd · 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.
CA KS MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 12, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 13, 2023
Reported by CALIFORNIA AG filing
Amerita reported a data breach to the Montana Attorney General. The breach was reported on 2023-09-05. The breach occurred from 3/12/2023 to 3/13/2023. 92 Montana residents were affected.
Affected (this filing): 92
Amerita reported to HHS on 2023-09-05 a Hacking/IT Incident affecting 219,707 individuals. Breached information located on Network Server. The incident involved PharMerica (parent company) and exposed PHI including names, addresses, claims, financial info, medications, and treatment data. Response included credit monitoring and security safeguards.
Affected (this filing): 219,707
Amerita reported that an unknown third party accessed its computer systems from March 12-13, 2023. The incident involved personal information including names, addresses, and patient health information such as medical history, diagnosis, medications, and health insurance details. Social Security numbers were not involved. Amerita engaged cybersecurity advisors and enhanced technical security measures. 8,238 Rhode Island residents were affected.
Affected (this filing): 8,238
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.