Rotech Healthcare reported a data breach to the Montana Attorney General. The breach was reported on 2016-08-10. The breach occurred on 6/13/2016. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Aug 10, 2016 → Aug 11, 2016. View entity profile → Other incidents for this victim →
incident inc_0fbda9f4b0004cd2 · 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.
PHI · Health (basic) · Identity (basic)
FEDERAL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 13, 2016
When the intrusion reportedly occurred, per the linked filings
Rotech Healthcare reported a data breach to the Montana Attorney General. The breach was reported on 2016-08-10. The breach occurred on 6/13/2016. 1 Montana residents were affected.
Affected (this filing): 1
Rotech Healthcare Inc. reported to HHS on August 11, 2016, an unauthorized disclosure incident affecting 957 patients. Employees printed medical records from the electronic medical records system and removed them from the office. The compromised information included names, Social Security numbers, dates of birth, addresses, and phone numbers. The breach involved physical paper records which were later recovered by the Secret Service.
Affected (this filing): 957
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.