The MHMR Authority of Brazos Valley is a public non-profit community MHMR center. Through the Texas Department of State Health Services and Texas Department of
Clustered 3 filings across 3 jurisdictions · filing window Dec 22, 2022 → Aug 1, 2023. View entity profile → Other incidents for this victim →
incident inc_774e4e9631ec4757 · merge_method deterministic · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Government ID · Identity (basic)
ME TX
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 5, 2022
When the intrusion reportedly occurred, per the linked filings
The MHMR Authority of Brazos Valley is a public non-profit community MHMR center. Through the Texas Department of State Health Services and Texas Department of
MHMR Authority of Brazos Valley reported to HHS on 2023-02-28 a Hacking/IT Incident affecting 78984 individuals. Breached information located on Network Server.
May 30, 2023
Reported by MAINE AG filing
MHMR Authority of Brazos Valley, a healthcare entity based in Bryan, Texas, reported an external system breach (hacking) occurring on November 5, 2022, discovered on May 30, 2023. The incident compromised the personal information of 83,245 individuals, including 8 Maine residents. Acquired data included names combined with driver's license numbers. The entity provided written notification and offered 12 months of credit/dark web monitoring and identity protection insurance.
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.
Affected (this filing): 78,984
Affected (this filing): 83,245