OREGONAccidentalHealthcareHealthcareMisdeliveryBusiness Associate (HIPAA)Customer Data InvolvedPHIHealth (basic)Identity (basic)LowContained

REGENCE BLUESHIELD

bd_991fe0a69a7f25b9 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jan 31, 2025

To disclose

—

Affected

783

Confidence

69%

Full breach record for REGENCE BLUESHIELD →2 incidents on file

Regence BlueShield reported to HHS on 2025-01-31 a Unauthorized Access/Disclosure affecting 783 individuals. Breached information located on Network Server. An employee misconfigured a computer command resulting in PHI (demographic and clinical) being sent to the wrong recipients. The CE notified HHS, affected individuals, and the media, and implemented additional technical safeguards.

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

Jan 31, 2025

Filed

—

No filing yet · watching

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

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

Name: REGENCE BLUESHIELD
norm: regence blueshield
Industry: Health Care Services

Name: REGENCE BLUESHIELD
norm: regence blueshield
Industry: Healthcaresource default

Discovered: Not extracted — the OCR public portal omits it
Materiality determined: —
Notification sent: —
Affected individuals: 783nationwide
Data types: PHIHealth (basic)Identity (basic)
HHS breach type: Unauthorized access or disclosure
Where the data lived: Network server
Covered-entity type: Business associate
Attack vector: Misconfiguration
MITRE ATT&CK: T1530 Data from Cloud Storage
Threat actor: Internal
Regulator citations: Notified HHSOCR’s investigation
Third party: via Regence BlueShieldbusiness associate

During the incident: Notified HHS, affected individuals, and the media
Revised its policies and procedures
Implemented additional technical safeguards
Changes made: Revised its policies and procedures
Implemented additional technical safeguards
Source: Quoted from the filing itself, not independently verified.

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.

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: Jan 31, 2025
Raw hash: 0795315f4036fd9f1de803ecd2fd1159775f3a867820405c178e8fe055f3af00

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/html1.4 KB

Download View at source

Reporting entityREGENCE BLUESHIELD

Victim entityREGENCE BLUESHIELD

IncidentMisconfiguration

Stated responseNotified HHS, affected individuals, and the media

ComplianceHHS notified

Extraction provenanceno artifact recorded

Source provenanceocrportal.hhs.gov

Source filing