Regence BlueShield Data Breach (January 2025)
Regence BlueShield reported a data breach to the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Jan 31, 2025. It affected 783 people.
What Happened
- Cause: Unauthorized access or disclosure (someone saw or shared information they should not have, including insiders and mistakes).
- Where the information was: Network Server.
- Type of organization (HHS): Business Associate.
- Industry: Healthcare.
- Based in: Oregon.
Regence BlueShield, the covered entity (CE) reported that an employee misconfigured a computer command which resulted in the protected health information (PHI) of 783 individuals being sent to the wrong recipients. The PHI involved demographic and clinical information. The CE notified HHS, affected individuals, and the media. In response to the breach and OCR’s investigation, the CE revised its policies and procedures and implemented additional technical safeguards.
Case summary from the U.S. Department of Health and Human Services, Office for Civil Rights
What Was Exposed
The filings and notice letter mention these kinds of information:
Not everyone affected had every item exposed. Your letter says which of your details were involved.
What to Do Now
If Medical Information Was Exposed
- Read the "explanation of benefits" statements from your health plan, and question any care you did not receive.
- Ask your providers for a copy of your records if you suspect someone used your identity for treatment.
- Be careful with calls about "your recent treatment" asking you to confirm details or pay.
What to Do Now
- Read the notice letter carefully: it should say what was exposed, when, and what the organization is offering (often free credit monitoring).
- If anything sensitive was involved, a free credit freeze with Equifax, Experian and TransUnion is the strongest single step.
- Watch for phishing that mentions the breach. Contact the organization only through phone numbers or websites you find yourself.
- Keep the letter: you may need it for a claim, a settlement or a dispute later.
For Everyone Affected
- Watch for phishing that mentions the breach. Contact the organization only through phone numbers or websites you find yourself.
- Keep the letter: you may need it for a claim, a settlement or a dispute later.
Official Filings
| Filed With | Date | People Affected | Source |
|---|---|---|---|
| U.S. Department of Health and Human Services (HHS) Office for Civil Rights | Jan 31, 2025 | 783 | HHS breach portal |
Similar Breaches Reported Around the Same Time
| Reported | Organization | People Affected | Industry |
|---|---|---|---|
| Jan 31, 2025 | Mental Health Association Inc. | 12,633 | Healthcare |
| Jan 31, 2025 | Infosys Public Services, Inc. | 2,985 | Healthcare |
| Jan 31, 2025 | Jewish Child Care Association of New York | 1,962 | Healthcare |
| Jan 31, 2025 | Regence (Regence BlueShield and Regence BCBS of OR) | 714 in WA | Healthcare |
| Jan 31, 2025 | Delta County Memorial Hospital District | – | Healthcare |
| Jan 31, 2025 | PIH Health, Inc. | 2,947,264 | Healthcare |
Questions
- Is the Regence BlueShield data breach letter legitimate?
- Regence BlueShield filed a breach notice with the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Jan 31, 2025. If your letter matches those details, it is likely genuine. Still, don't use phone numbers or links from an email you weren't expecting; look up the organization yourself.
- Can I sue Regence BlueShield or claim compensation?
- It depends on what was exposed, whether you lost money or time because of it, and the laws where you live. Large breaches sometimes lead to class actions and settlements, which are announced by a court-appointed administrator. A lawyer can tell you where you stand.
- How many people were affected?
- Regence BlueShield told HHS that 783 people were affected.