MedEvolve
bd_43a0abb3eba49ad4 · schema v1 · pii pii-v1
Full breach record for MedEvolve →Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
HHS OCR settled with MedEvolve, Inc. for $350,000 regarding the disclosure of PHI from an unsecured FTP server. HHS's investigation indicated that the PHI of 230,572 individuals had been disclosed, that MedEvolve failed to enter into a business associate agreement with a subcontractor, and that MedEvolve's assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI held by it as a business associate was not sufficiently accurate or thorough.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 16, 2023
Filed
—
Corroborated · see linked filings
This record is the regulator's action, not a breach notice; its own dates cannot anchor compliance clocks. See the linked filings.
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Massachusetts State AGbd_9f8a44684fb3d8bb2018-07-30 · +1751dVerified by operator
- New Hampshire State AGbd_0f2d25b2273b13f32018-07-27 · +1754dVerified by operator
- California State AGbd_0bd4122eff0cddb42018-07-10 · +1771dVerified
- Massachusetts State AGbd_2cc6cf8c3756184a2018-07-10 · +1771dVerified
Show 3 more filings ↓Show fewer ↑up to 1771d gap
- HHS OCRbd_6ac38550f52fc8d32018-07-10 · +1771dVerified
- New Hampshire State AGbd_a0496aa58a430ab52018-07-10 · +1771dVerified
- Montana State AGbd_a2d9849fbe9658052018-07-10 · +1771dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Jul 10 (CA), last Jul 30 (MA) — a 20-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.
Source ceiling
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.