MedStar Mobile Healthcare reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-19. The breach occurred from 10/19/2022 to 10/20/2022. 56 Montana residents were affected.
Affected (this filing): 56
Clustered 2 filings across 2 jurisdictions · filed Dec 19, 2022. View entity profile → Other incidents for this victim →
incident inc_6afecce2f9854544 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 19, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 20, 2022
Reported by CALIFORNIA AG filing
MedStar Mobile Healthcare reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-19. The breach occurred from 10/19/2022 to 10/20/2022. 56 Montana residents were affected.
Affected (this filing): 56
MedStar Mobile Healthcare, an ambulance service provider in Tarrant County, Texas, reported a cyberattack on October 19-20, 2022. An unauthorized third party accessed a restricted network location containing files with personal health information. While actual access to specific files could not be confirmed, the breach potentially exposed names, dates of birth, contact information, and medical care details. MedStar engaged third-party experts to investigate and is securing its systems.
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.