Emerson Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2019-03-08. The breach occurred from 5/9/2018 to 5/17/2018. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed Mar 8, 2019. View entity profile → Other incidents for this victim →
incident inc_cbbe669f98e1497f · 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.
MA MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 9, 2018
When the intrusion reportedly occurred, per the linked filings
Emerson Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2019-03-08. The breach occurred from 5/9/2018 to 5/17/2018. 2 Montana residents were affected.
Affected (this filing): 2
Emerson Hospital (MA) reported to HHS on 2019-03-08 an Unauthorized Access/Disclosure breach affecting 6,314 individuals. The hospital's business associate, MiraMed Global Services Inc., impermissibly transmitted electronic files containing PHI to an unauthorized third party. PHI involved included names, addresses, Social Security numbers, and insurance information. Emerson Hospital notified HHS, affected individuals, and the media, and offered free identity protection services to all affected individuals. Breached information was located on Other.
Affected (this filing):
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.