WASHINGTONHackingHealthcareHealthcareCustomer Data InvolvedHealth (basic)Low

PROVAIL

bd_82d076fa557e8406 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Aug 8, 2025

To disclose

—

Affected

501

Linked

3 records

Confidence

95%

Full breach record for PROVAIL →2 incidents on file

PROVAIL (Washington state Healthcare Provider) reported to HHS OCR on 2025-08-08 a Hacking/IT Incident affecting 501 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further detail is available in the public HHS disclosure.

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

Aug 8, 2025

Filed

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

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitebeastbd_b9ac5529b1ebdf5d2025-06-10 · +59dVerified

Regulatory filings (1) · sorted by filing gap

Washington State AGbd_932c580a345bbfbf2026-01-16 · +161dVerified by operator

Name: PROVAIL
norm: provail
Domain: provail.org
Industry: Health Care Services

Name: PROVAIL
norm: provail
Domain: provail.org
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 501nationwide
Data types: Health (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
Threat actor: External
Regulator citations: HHS OCR breach report filed 2025-08-08

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 OCRAug 8 · first · this page

Washington State AG+161d

Pattern: first filing Aug 8 (WA), last Jan 16 (WA) — a 161-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: Aug 8, 2025
Raw hash: 18cf80aa416ad27308b3b1245172fdd09a6bd3d9d27abc1069fe5b580443a0d0

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

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entityPROVAIL

Victim entityPROVAIL

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing