Clustered 3 filings across 3 jurisdictions · filed Oct 14, 2016. View entity profile → Other incidents for this victim →
incident inc_604c09cd21244228 · 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 MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 15, 2016
When the intrusion reportedly occurred, per the linked filings
Aug 15, 2016
Reported by CALIFORNIA AG filing
Integrity Transitional Hospital reported to HHS on 2016-10-14 a Hacking/IT Incident affecting 29514 individuals. Breached information located on Network Server. The entity ceased healthcare operations effective September 1, 2017.
Affected (this filing): 29,514
Integrity Transitional Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2016-10-14. The breach occurred on 8/15/2016. 2 Montana residents were affected.
Affected (this filing): 2
Integrity Transitional Hospital notified the California Attorney General of a data breach discovered on August 15, 2016. An unauthorized individual potentially accessed patient lab results, health insurance information, and scanned driver's licenses. The incident did not involve Social Security numbers or financial account information. The organization engaged forensic experts and is enhancing system security.
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.