Arizona Dermatopathology reported a data breach to the Montana Attorney General. The breach was reported on 2019-07-24. The breach occurred on 3/21/2019. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Jul 24, 2019 → Jul 25, 2019. View entity profile → Other incidents for this victim →
incident inc_848e8fd0908d484f · 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.
AZ MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 21, 2019
When the intrusion reportedly occurred, per the linked filings
May 15, 2019
Reported by HHS OCR filing
Arizona Dermatopathology reported a data breach to the Montana Attorney General. The breach was reported on 2019-07-24. The breach occurred on 3/21/2019. 1 Montana residents were affected.
Affected (this filing): 1
Arizona Dermatopathology reported to HHS on 2019-07-25 a Hacking/IT Incident affecting 6,425 individuals. Breached information located on Network Server. A business associate, American Medical Collection Agency, alerted the covered entity on May 15, 2019, that its payment website was compromised, potentially exposing patient PHI (demographic and clinical). The CE ceased using the BA, notified individuals and HHS, and cooperated with OCR.
Affected (this filing): 6,425
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.