Interactive Medical Systems reported a data breach to the Montana Attorney General. The breach was reported on 2020-02-13. The breach occurred from 7/19/2019 to 12/31/2019. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Feb 13, 2020 → Feb 27, 2020. View entity profile → Other incidents for this victim →
incident inc_cc0eefc52ec6427c · 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.
MT NC
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 19, 2019
When the intrusion reportedly occurred, per the linked filings
Interactive Medical Systems reported a data breach to the Montana Attorney General. The breach was reported on 2020-02-13. The breach occurred from 7/19/2019 to 12/31/2019. 2 Montana residents were affected.
Affected (this filing): 2
Interactive Medical Systems, Corp. (NC), a business associate, reported to HHS on 2020-02-27 a Hacking/IT Incident affecting 15,010 individuals via an email phishing scheme. Breached ePHI was located in Email systems and included names, addresses, dates of birth, Social Security numbers, and financial and health insurance information. The BA notified HHS, affected individuals, media, FBI, and the NY Attorney General. Corrective actions — policy revisions, updated risk analysis, and employee retraining — were implemented and confirmed by OCR.
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.