FLORIDAUnauthorized AccessHealthcareHealthcarePHIMedium

ProxyCare

bd_bda67140109f470d · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 27, 2026

To disclose

—

Affected

45,196

Linked

4 filings

Confidence

88%

Full breach record for ProxyCare →

Proxycare, Inc., a Florida-based healthcare provider, reported a Hacking/IT Incident to HHS OCR affecting 45,196 individuals. The breach involved a network server. No business associate was reported as involved.

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 27, 2026

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

Massachusetts State AGbd_538e129165d4f09c2026-03-27Verified
Vermont State AGbd_d88517ca94b1350b2026-03-27Verified
New Hampshire State AGbd_ff368c4755cbb8732026-04-01 · +5dVerified

Name: ProxyCare
norm: proxycare
Domain: proxycarerx.com

Name: ProxyCare
norm: proxycare
Domain: proxycarerx.com
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 45,196nationwide
Data types: PHI
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: Reported to 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 ↗

Massachusetts State AGMar 27 · first

Vermont State AGMar 27 · first

HHS OCRMar 27 · first · this page

New Hampshire State AG+5d

Pattern: first filing Mar 27 (MA), last Apr 1 (NH) — 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: Mar 27, 2026
Raw hash: b0bd43a9b0d536b5ddb7301d1881dee388a9a873b7493b1cfae1526dae192c03

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

Download View at source

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityProxyCare

Victim entityProxyCare

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing