Clustered 3 filings across 2 jurisdictions · filing window Sep 11, 2016 → Sep 12, 2016. View entity profile → Other incidents for this victim →
incident inc_7f2e13241b2247c8 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Health (basic) · Identity (basic)
CA MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 8, 2016
When the intrusion reportedly occurred, per the linked filings
Aug 9, 2016
Reported by CALIFORNIA AG, HHS OCR filings
Pratap S. Kurra, M.D. reported a data breach where billing tickets containing patient names, procedure types, and anesthesia details were accidentally discarded during a move on August 8, 2016. Records were retrieved within 24 hours. No SSNs, financial, or medical insurance data were exposed. The incident was reported to the California AG and HHS.
On August 9, 2016, Pratap S. Kurra, M.D. (CA) discovered a breach in which his practice accidentally discarded paper billing tickets during an office move. The tickets were out of his control for less than 24 hours before being retrieved. The breach affected approximately 2,029 individuals. PHI involved included the CE's name, patients' names, hospital names, procedure types and times, anesthesia used, and difficulty of cases. Breached information located on Paper/Films. OCR provided technical assistance; the CE implemented corrective billing procedures.
Affected (this filing): 2,029
Pratap Kurrar, M.D. reported a data breach to the Montana Attorney General. The breach was reported on 2016-09-12. The breach occurred from 8/8/2016 to 8/9/2016. 1 Montana residents were affected.
Affected (this filing): 1
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.