St. Therese Medical Group, Inc reported to HHS OCR on 2012-09-17 a Theft affecting 3031 individuals. Breached information was located on a Desktop Computer. No business associate was identified as involved.
Affected (this filing): 3,031
Clustered 2 filings across 1 jurisdiction · filed Sep 17, 2012. View entity profile → Other incidents for this victim →
incident inc_5f435134192d4981 · merge_method deterministic · confidence 100%
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.
Health (basic) · Identity (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 22, 2012
When the intrusion reportedly occurred, per the linked filings
St. Therese Medical Group, Inc reported to HHS OCR on 2012-09-17 a Theft affecting 3031 individuals. Breached information was located on a Desktop Computer. No business associate was identified as involved.
Affected (this filing): 3,031
St. Therese Medical Group reported a data breach to the California Attorney General. The breach occurred on July 22, 2012. The notification includes sample letters for patients and providers, indicating that protected health information (PHI) and basic identity information were likely affected. No specific details regarding the cause, scope, or number of individuals affected are provided in the public filing summary or the redacted attachment text.
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.