Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Affected (total reported)
2,500
Data types
3
Health (basic) · Identity (basic) · Minor
Jurisdictions
1
FEDERAL
Linked filings
1
all HHS OCR
Sensitive data
minor
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
My Pediatrician, PA reported to HHS on 2016-06-01 a hacking incident affecting 2500 individuals. The breach occurred at its business associate, Bizmatics, Inc., and involved protected health information (PHI) on a network server.
Affected (this filing): 2,500
HHS notified
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.