Moorestown Visiting Nurse Association
bd_0c2d0e2e8660ee1b · schema v1 · pii pii-v1
Full breach record for Moorestown Visiting Nurse Association →The covered entity (CE), Moorestown Visiting Nurse Association, reported that its business associate (BA) experienced a ransomware attack affecting the protected health information (PHI) of 26,465 individuals. The PHI involved included names, addresses, dates of birth, Social Security numbers, patient identification numbers, and medical records. The CE notified HHS, affected individuals, and the media. In response to the breach, both the CE and BA implemented additional technical safeguards to better protect PHI.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 7, 2020
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitecoldlockbd_797528ccab1df79f2020-03-19 · +49dVerified by operator
Regulatory filings (4) · sorted by filing gap
- Montana State AGbd_3cc841a3182f78bc2020-05-07Verified
- Indiana State AGbd_cb3dc1bfdd05aed12020-05-07Verified by operator
- Massachusetts State AGbd_ff211dfec426af042020-05-07Verified by operator
- Illinois State AGbd_df721905d34e49e52020-01-01 · +127dVerified by operator
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last May 7 (NJ) — a 127-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.