Milligan Chiropractic Group, Inc. d/b/a Del Mar Chiropractic Sports Group reported to HHS on 2018-03-30 a Theft affecting 2640 individuals. Breached information located on Laptop.
Affected (this filing): 2,640
Clustered 2 filings across 1 jurisdiction · filed Mar 30, 2018. View entity profile → Other incidents for this victim →
incident inc_2d008ac63b474e12 · merge_method deterministic · confidence 86%
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.
Identity (basic) · Health (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 31, 2018
When the intrusion reportedly occurred, per the linked filings
Jan 31, 2018
Reported by HHS OCR, CALIFORNIA AG filings
Milligan Chiropractic Group, Inc. d/b/a Del Mar Chiropractic Sports Group reported to HHS on 2018-03-30 a Theft affecting 2640 individuals. Breached information located on Laptop.
Affected (this filing): 2,640
Milligan Chiropractic Group, Inc. d/b/a Del Mar Chiropractic Sports Group reported the theft of an employee's laptop on January 31, 2018. The incident potentially affected 2,584 California residents. Exposed data included names, dates of birth, and clinic/progress notes (PHI). No SSNs or financial data were involved. The organization implemented enhanced electronic safeguards, secure cloud storage, and employee training.
Affected (this filing): 2,584
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.