East Tennessee Children's Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-19. The breach occurred from 3/11/2022 to 3/14/2022. 26 Montana residents were affected.
Affected (this filing): 26
Clustered 2 filings across 2 jurisdictions · filed May 19, 2022. View entity profile → Other incidents for this victim →
incident inc_24619c89bd2b47ca · 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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 11, 2022
When the intrusion reportedly occurred, per the linked filings
Apr 19, 2022
Reported by MAINE AG filing
East Tennessee Children's Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-19. The breach occurred from 3/11/2022 to 3/14/2022. 26 Montana residents were affected.
Affected (this filing): 26
East Tennessee Children's Hospital Association Inc. reported a data breach affecting 6 Maine residents. The breach, which occurred between March 11 and March 14, 2022, was discovered on April 19, 2022. The incident was described as an external system breach (hacking), and affected data included names and Social Security numbers. The hospital offered 12 months of identity theft protection services through IDX.
Affected (this filing): 6
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.