WASHINGTONAccidentalHealthcareHealthcareMisconfigurationCustomer Data InvolvedPHIHealth (basic)Identity (basic)HighContained

UW Medicine

bd_721496fd43b47b11 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Feb 20, 2019

To disclose

—

Affected

973,024

Linked

5 filings

Confidence

68%

UW Medicine reported to HHS on 2019-02-20 a Hacking/IT Incident affecting 973024 individuals. Breached information located on Network Server. A configuration error resulted in PHI (names and medical record numbers) becoming accessible on the internet.

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

Feb 20, 2019

Filed

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

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Montana State AGbd_3adad2f84e312d482019-02-20Verified by operator
Washington State AGbd_4ecc99dad6670eb72019-02-20Verified
California State AGbd_d6512ec60a11cad62019-02-20Verified by operator
Oregon State AGbd_0968762279005b792019-02-25 · +5dCandidate

Name: UW Medicine
norm: uw medicine
Domain: uwmedicine.org
Industry: Health Care Services

Name: UW Medicine
norm: uw medicine
Domain: uwmedicine.org
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 973,024nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Misconfiguration
MITRE ATT&CK: T1074 Data Staged
Regulator citations: Notified HHS

During the incident: Implemented additional administrative and technical safeguards
Retrained workforce members on methods to better protect its PHI
Notified HHS
Notified affected individuals
Notified the media
Provided substitute notice
Changes made: Implemented additional administrative and technical safeguards
Retrained workforce members on methods to better protect its PHI
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 · 5 filings · 4 states

View merged incident ↗

Montana State AGFeb 20 · first

Washington State AGFeb 20 · first

California State AGFeb 20 · first

HHS OCRFeb 20 · first · this page

Oregon State AG+5d

Pattern: first filing Feb 20 (MT), last Feb 25 (OR) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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: Feb 20, 2019
Raw hash: fd73378c2c8920f83cbe68daed1baea4346d74e0a77911ace2af5158b9704b51

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

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityUW Medicine

Victim entityUW Medicine

IncidentMisconfiguration

Stated responseImplemented additional administrative and technical safeguards

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing