Confirmed breach. Intrusion Mar 23, 2022, discovered Mar 23, 2022 — the first regulatory filing landed 58 days later. 529 individuals reported across the linked filings.
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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
529
Data types
3
PII · Identity (basic) · Government ID
Jurisdictions
1
CA
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 23, 2022
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Mar 23, 2022
Reported by CALIFORNIA AG filing
58 days
🐻CALIFORNIAHHS OCRFirst filinglinked via same-victim cross-source · 100%
Julieta Y. Echeverria D.D.S., Inc. reported to HHS on 2022-05-20 a Theft affecting 529 individuals. Breached information located on Paper/Films. Documents containing PHI (names, DOB, SSN, diagnoses) were stolen during an office burglary.
Julieta Y. Echeverria D.D.S., Inc. reported that an unauthorized individual accessed its office overnight on March 23, 2022, and stole paper patient records. The stolen records contained protected health information (PHI), including names, addresses, and potentially Social Security numbers. The organization launched an investigation and is providing 12 months of identity monitoring services through Kroll to affected patients.
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.