GLOBALClaimed by ContiFirst sightinglinked via shared-victim match · 100%
Posted to leak site Oct 26, 2021bd_acaf4319581999a9
Clustered 4 filings across 4 jurisdictions · filing window Oct 26, 2021 → Jan 25, 2022. View entity profile → Other incidents for this victim →
incident inc_7909f33367884b49 · 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.
MA MT NH
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 1, 2021
When the intrusion reportedly occurred, per the linked filings
Medical Healthcare Solutions, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-01-21. The breach occurred from 10/1/2021 to 10/4/2021. 13 Montana residents were affected.
Medical Healthcare Solutions, Inc. (MA, Business Associate) reported to HHS OCR on 2022-01-22 a ransomware incident affecting 133,997 individuals via a Network Server. Exposed PHI included names, SSNs, driver's license numbers, addresses, dates of birth, diagnoses, lab results, medications, and financial/claims information. The BA notified HHS, affected individuals, and media; provided substitute notice; offered credit monitoring; and implemented enhanced safeguards including staff retraining.
State of New Hampshire Attorney General breach notification filed by Medical Healthcare Solutions, Inc. on January 25, 2022. The attached consumer notification letter is empty (pages 1-9 contain no text). No breach details, dates, data types, or response actions are provided in the source document.
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): 13
Affected (this filing): 133,997