WASHINGTONHackingHealthcareHealthcareCustomer Data InvolvedPHIHealth (basic)Identity (basic)Medium

Lake Washington Vascular

bd_ef8cdd5b9a98992e · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Feb 25, 2025

To disclose

—

Affected

21,534

Linked

2 filings

Confidence

69%

Full breach record for Lake Washington Vascular →

Lake Washington Vascular reported to HHS on 2025-02-25 a Hacking/IT Incident affecting 21,534 individuals. Breached information located on Network Server.

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 25, 2025

Filed

—

Corroborated · see linked filings

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

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteqilinbd_05631bda1b7705cd2025-02-19 · +6dCandidate

Name: Lake Washington Vascular
norm: lake washington vascular
Industry: Health Care Services

Name: Lake Washington Vascular
norm: lake washington vascular
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 21,534nationwide
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: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: External
Regulator citations: Notified HHS OCR

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: Feb 25, 2025
Raw hash: 3ce1630c66eda3c6e1af963cf110543d0b51becc2296ba5bfed7fbb52fc8c2ec

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/html981 B

Download View at source

Linked disclosures

Ransomware claims (1)

Reporting entityLake Washington Vascular

Victim entityLake Washington Vascular

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing