FLORIDAMalwareHealthcareHealthcareRansomwareBusiness Associate (HIPAA)Customer Data InvolvedData EncryptedRansom DemandedPHIHealth (basic)Identity (basic)MediumResolved

UF Health Shands

bd_85822a959e69e1b1 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jun 12, 2020

To disclose

—

Affected

13,146

Linked

2 filings

Confidence

69%

Full breach record for UF Health Shands →

UF Health Shands reported to HHS on 2020-06-12 a Hacking/IT Incident affecting 13146 individuals. Breached information located on Email. The covered entity's business associate experienced a ransomware attack. This case is closed and consolidated into an existing investigation.

J jump to incidentP pin to compareR raw source

HIPAA clock✓ HHS notified

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

Incident timeline — partial

? — ?

Breach window unknown

Jun 12, 2020

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 2 filings about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

HHS OCRbd_e42f27879940b6002020-06-12Candidate

Name: UF Health Shands
norm: uf health shands
Industry: Health Care Services

Name: UF Health Shands
norm: uf health shands
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 13,146nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Email
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Reported to HHS

During the incident: Case closed and consolidated into an existing investigation
Source: Quoted from the filing itself, not independently verified.

Compliance flags: HHS notified
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
Clock breakdown: Statute Window Elapsed Threshold Status
HIPAA
Discovered: not extracted
→ Notified: not extracted
— regulatory submission HHS notified

Statute	Window	Elapsed	Threshold	Status
HIPAA	Discovered: not extracted → Notified: not extracted	—	regulatory submission	HHS notified

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

HHS OCRJun 12 · first

HHS OCRJun 12 · first · this page

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

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: Jun 12, 2020
Raw hash: c311526c168858056007a3725a5739baa1abc6cd5503f7b954c39617ddf76a56

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html1.2 KB

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityUF Health Shands

Victim entityUF Health Shands

IncidentUnauthorized Access

Stated responseCase closed and consolidated into an existing investigation

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing