HackingHealthcareHealthcareSupply Chain (3P Vendor)Customer Data InvolvedPHIGovernment IDIdentity (basic)Health (basic)MediumContained

OLE Health

bd_8ced1e7888cb8531 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Dec 15, 2025

Filed

Jan 16, 2026

To disclose

5 weeks

Affected

Not disclosed

Confidence

67%

Full breach record for OLE Health →

OLE Health (DBA CommuniCare + OLE) notified patients of a data security incident involving a third-party vendor, TriZetto, which works with their electronic medical record system (OCHIN). An unauthorized individual gained access to TriZetto's systems. Affected data may include names, social security numbers, dates of birth, contact information, and health/insurance information. The clinic was notified by OCHIN on December 15, 2025. No specific count of affected individuals was disclosed in the notice.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 5 weeks / 32 days

Dec 15, 2025

Discovered

Jan 16, 2026

Filed

vs. sector median

8 wks faster

Part of TriZetto Provider Solutions supply-chain incident (2025) — a supply-chain cascade affecting multiple organizations.View cascade →

Tracked as a single-filing incident — the only disclosure on record for this event so far.ConfirmedView incident

Name: OLE Health
norm: ole health

Name: OLE Health
norm: ole health
Also named: OLE Healthdba oflegal entity
CommuniCare + OLEdba oftrade name
Industry: Healthcarellm

Discovered: Dec 15, 2025
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: PHIGovernment IDIdentity (basic)Health (basic)
Data elements: Social Security numberDate of birthMedical information
Attack vector: Third-Party / Supply Chain
Threat actor: External
Third party: via TriZetto
Initial access: supply_chain

During the incident: Working closely with OCHIN to understand what happened and ensure protection of patient information
Reviewing our own processes to reduce the risk of something like this happening again
Monitoring vendor compliance with appropriate security safeguards
Changes made: Reviewing our own processes to reduce the risk of something like this happening again
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(32 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

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://oag.ca.gov/ecrime/databreach/reports/sb24-617210
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 16, 2026
Raw hash: 66c599fb7212b9784b1661342e2a7bb1b76d2c82a0b65c616a22816bc005f1c3

Reporting entityOLE Health

Victim entityOLE Health

Incidentdiscovered Dec 15, 2025

Stated responseWorking closely with OCHIN to understand what happened and ensure protection of patient information

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov