LOUISIANAHackingHealthcareHealthcareBusiness Associate (HIPAA)Customer Data InvolvedPHIHealth (basic)Identity (basic)Medium

AMEDISYS, INC.

bd_061a38035e44d0be · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 26, 2026

To disclose

—

Affected

9,111

Linked

2 filings

Confidence

68%

Full breach record for AMEDISYS, INC. →3 incidents on file

Amedisys reported to HHS on 2026-03-26 a Hacking/IT Incident affecting 9111 individuals. Breached information located on Network Server. Business associate present.

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

Filed

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

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Texas State AGbd_832a56572603b15c2026-04-02 · +7dVerified

Name: AMEDISYS, INC.
norm: amedisys
Domain: amedisys.com
Industry: Health Care Services

Name: AMEDISYS, INC.
norm: amedisys
Domain: amedisys.com
Industry: Health Care Services
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 9,111nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare providerBusiness associate involved
Attack vector: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 ChannelT1119 Automated Collection
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 · 2 filings · 2 states

View merged incident ↗

HHS OCRMar 26 · first · this page

Texas State AG+7d

Pattern: first filing Mar 26 (LA), last Apr 2 (TX) — a 7-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 26, 2026
Raw hash: b39b980cd94c50c1544adc71ba3371c6eae6a2fdedbdf6322d671b42feca5138

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

Download View at source

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityAMEDISYS, INC.

Victim entityAMEDISYS, INC.

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing