Tandigm Health (Tandigm) reported a data breach to the Montana Attorney General. The breach was reported on 2018-11-21. The breach occurred from 4/24/2017 to 12/31/2017. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Nov 21, 2018. View entity profile → Other incidents for this victim →
incident inc_e8e1fb20e7e04751 · merge_method deterministic · confidence 100%
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.
FEDERAL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 24, 2017
When the intrusion reportedly occurred, per the linked filings
Tandigm Health (Tandigm) reported a data breach to the Montana Attorney General. The breach was reported on 2018-11-21. The breach occurred from 4/24/2017 to 12/31/2017. 1 Montana residents were affected.
Affected (this filing): 1
Tandigm Health (PA) reported to HHS on 2018-11-21 a Hacking/IT Incident affecting 7,376 individuals. A vulnerability on the covered entity's website allowed unauthorized individuals to bypass security safeguards and potentially access a network server database containing PHI, including demographic and clinical information. The CE immediately fixed the misconfiguration, tested and validated its security configuration, and notified HHS, affected individuals, and the media. OCR reviewed the CE's policies for Security Rule compliance.
Affected (this filing):
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.