CALIFORNIAHackingHealthcareHealthcarePHIHealth (basic)Identity (basic)HighContained

One Medical

bd_ace0db4fc909c3e3 · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Jul 17, 2026

To disclose

—

Affected

153,174

Linked

3 filings

Confidence

70%

Full breach record for One Medical →2 incidents on file

One Medical Group, Inc. reported to HHS on 2026-07-17 a Hacking/IT Incident affecting 153174 individuals. Breached information located on Network Server.

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 17, 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 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

New Hampshire State AGbd_0a3e917e20144dd42026-07-06 · +11dVerified
Washington State AGbd_eb3976117e8189792026-07-03 · +14dVerified

Name: One Medical
norm: one medical
Domain: app.onemedical.com
Industry: Health Care Services

Name: One Medical
norm: one medical
Domain: app.onemedical.com
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 153,174nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Hacking / IT incident
Where the data lived: Network server
Covered-entity type: Healthcare provider
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Notified HHS

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 · 3 filings · 3 states

View merged incident ↗

Washington State AGJul 3 · first

New Hampshire State AG+3d

HHS OCR+14d · this page

Pattern: first filing Jul 3 (WA), last Jul 17 (CA) — a 14-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 17, 2026
Raw hash: 751792511a425b9f9c998e9f4c757c4d1349da7f7e8f3bdcfd194dd87e239460

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

Download View at source

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityOne Medical

Victim entityOne Medical

IncidentUnauthorized Access

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing