MINNESOTAAccidentalHealthcareHealthcareMisdeliveryCustomer Data InvolvedPHIHealth (basic)Identity (basic)MediumResolved

Mayo Clinic

bd_45136d5e41b829fb · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 22, 2019

To disclose

—

Affected

1,902

Confidence

68%

Full breach record for Mayo Clinic →7 incidents on file

Mayo Clinic reported to HHS on 2019-03-22 a Unauthorized Access/Disclosure affecting 1902 individuals. Breached information located on Other. An update to its mobile application software enabled users to access the ePHI of 1,902 individuals, including names, addresses, dates of birth, diagnoses, lab results, and medications. The CE notified HHS, affected individuals, and the media, and revised the software to fix the error.

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

Mar 22, 2019

Filed

—

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed1,902 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,902nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Unauthorized access or disclosure
Where the data lived: Other
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
Notified affected individuals
Notified the media
Posted substitute notice on its website
Revised its mobile application software
Changes made: Revised its mobile application software
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: Mar 22, 2019
Raw hash: b4c8d08ea8383e61486d1b01bfdc3819bf488e5e943462d0212c589d455609d7

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

Download View at source

Reporting entityMayo Clinic

Victim entityMayo Clinic

IncidentUnauthorized Access

Stated responseNotified HHS

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing