Clustered 3 filings across 3 jurisdictions · filed Mar 25, 2022. View entity profile → Other incidents for this victim →
incident inc_c8b017b2165544c4 · merge_method human · 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.
IL MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 14, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 10, 2022
Reported by WASHINGTON AG filing
Christie Business Holdings Company, P.C. reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-25. The breach occurred from 7/14/2021 to 8/19/2021. 115 Montana residents were affected.
Affected (this filing): 115
Christie Business Holdings Company, P.C., a health sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2022-03-10 and filed notice on 2022-03-25. 694 Washington residents were affected. 15 days elapsed between awareness and notification. 239 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 694
Christie Business Holdings Company, P.C. reported to HHS on 2022-03-25 a Hacking/IT Incident affecting 502,869 individuals. Breached information located on Email. An employee was the subject of an email phishing attack exposing PHI including names, addresses, DOB, SSNs, and financial/medical data. Response included credit monitoring and staff retraining.
Affected (this filing): 502,869
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.