University of Mississippi Medical Center
bd_e6b1f21dce38dae4 · schema v1 · pii pii-v1
Full breach record for University of Mississippi Medical Center →University of Mississippi Medical Center (MS) reported to HHS OCR on 2017-07-07 a Hacking/IT Incident affecting 7,492 individuals. On May 7, 2017, ransomware encrypted data on a segregated network server containing records from a legacy electronic medical record system last used ~May 2016. Affected data included demographic, clinical, and health insurance information. The CE was under an active OCR Corrective Action Plan at the time; it revised security policies, conducted an enterprise-wide risk analysis, and fulfilled all notification obligations. Breached info located on Electronic Medical Record and Network Server.
Source provenance
- Source URL
- https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
- Filed at
- Jul 7, 2017
- Raw hash
- 8bcc726e9e8f8cf3dd944549e1db668c578a435e7b7f92ad55d4529acb1f767e
Source filing
Reporting entity
- Name
- University of Mississippi Medical Centernorm: university of mississippi medical center
- Domain
- umc.edu
- Industry
- Health Care Services
Victim entity
- Name
- University of Mississippi Medical Centernorm: university of mississippi medical center
- Domain
- umc.edu
- Industry
- Health Care Services
- Industry
- Healthcaresource default
Incident
- Discovered
- May 7, 2017
- Materiality determined
- —
- Notification sent
- —
- Affected individuals
- 7,492
- Data types
- HEALTH_BASICIDENTITY_BASICPHI
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
- Threat actor
- ExternalFinancial
- Regulator citations
- HHS OCR Corrective Action Plan (CAP) active at time of breachOCR Pacific Region monitoringOCR obtained assurances of corrective action and notification compliance
Compliance
- Time to disclose
- 9 weeks(61 days from discovery to filing)
- Compliance flags
- HHS notified
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
- Clock breakdown
Statute Window Elapsed Threshold Status HIPAA Discovered: May 7, 2017→ Notified: not extracted— regulatory submission HHS notified
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.