MINNESOTAAccidentalHealthcareHealthcareMisdeliveryBusiness Associate (HIPAA)Customer Data InvolvedPHIHealth (basic)Identity (basic)MediumContained

Mayo Clinic

bd_8ebe81c379bd04d2 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Nov 3, 2023

To disclose

—

Affected

1,152

Confidence

69%

Full breach record for Mayo Clinic →7 incidents on file

Mayo Clinic reported to HHS on 2023-11-03 a Unauthorized Access/Disclosure affecting 1152 individuals. Breached information located on Network Server. An employee inadvertently submitted PHI (names, DOB, lab results, MRNs, gender, race, treatment info) to an academic journal, which was then published online. The CE implemented additional administrative safeguards and retrained staff.

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

Nov 3, 2023

Filed

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

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed1,152 affectedView incident

Name: Mayo Clinic
norm: mayo clinic
Domain: mayoclinic.org
Industry: Health Care Services

Name: Mayo Clinic
norm: mayo clinic
Domain: mayoclinic.org
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 1,152nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Unauthorized access or disclosure
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1530 Data from Cloud Storage Object
Threat actor: Internal
Regulator citations: Notified HHS

During the incident: Notified HHS and affected individuals
Implemented additional administrative safeguards to better protect PHI
Staff were retrained
Changes made: Implemented additional administrative safeguards to better protect PHI
Staff were retrained
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.

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: Nov 3, 2023
Raw hash: fb90b78b6c72e2e12fd251a094831b55063438ed0e98366207374a08d0466ca5

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.5 KB

Download View at source

Reporting entityMayo Clinic

Victim entityMayo Clinic

IncidentUnauthorized Access

Stated responseNotified HHS and affected individuals

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing