Confirmed breach. Intrusion Mar 21, 2023, discovered Mar 28, 2023 — the first regulatory filing landed 142 days later (flagged late). 1 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 clocksCalifornia✗ CA 60-day late · 141dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
1
Data types
—
Jurisdictions
2
CA MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 28, 2023
When the intrusion reportedly occurred, per the linked filings
Hiawatha Harris MD, Inc dba Pathways to Wellness Medication Clinics reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-17. The breach occurred on 3/28/2023. 1 Montana residents were affected.
Affected (this filing): 1
🐻California State AGMost recentlinked via multistate filing link · 100%
Pathways to Wellness Medication Clinics experienced a network security incident on March 28, 2023, where an unauthorized party gained access to the network and disabled systems. The breach, occurring on March 21, 2023, potentially exposed personal and health information including names, addresses, SSNs, dates of birth, and health insurance details for patients in California. The company engaged forensic investigators, shut down network access, and is providing credit monitoring and fraud assistance to affected individuals.
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.