FLORIDAHackingHealthcareHealthcareCustomer Data InvolvedPHIHealth (basic)Identity (basic)Medium

Regency Oaks

bd_d12da6cfc417b5bf · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jul 11, 2025

To disclose

—

Affected

2,008

Linked

4 filings

Confidence

68%

Full breach record for Regency Oaks →

Regency Oaks reported to HHS on 2025-07-11 a Hacking/IT Incident affecting 2008 individuals. Breached information located on Email.

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

Jul 11, 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 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Vermont State AGbd_a5fce55530de448b2025-07-11Verified
Massachusetts State AGbd_00c4966682b143902025-07-12 · +1dVerified
Illinois State AGbd_788f07521c9d592b2025-07-01 · +10dCandidate

Name: Regency Oaks
norm: regency oaks
Industry: Health Care Services

Name: Regency Oaks
norm: regency oaks
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 2,008nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Email
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
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.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Illinois State AGJul 1 · first

Vermont State AG+10d

HHS OCR+10d · this page

Massachusetts State AG+11d

Pattern: first filing Jul 1 (IL), last Jul 12 (MA) — a 11-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: Jul 11, 2025
Raw hash: b72d279fcfc62aa712fab09fc3a624ea7991eadb06cd04f3424aa92603a8bcc2

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

Download View at source

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityRegency Oaks

Victim entityRegency Oaks

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing