Sound Community Services, Inc. Data Breach (May 2017)
Sound Community Services, Inc. reported a data breach to the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on May 26, 2017. It affected 1,278 people.
What Happened
- Cause: Email account break-in (attackers got into staff email accounts).
- Where the information was: Email.
- Type of organization (HHS): Healthcare Provider.
- Industry: Healthcare.
- Based in: Connecticut.
On January 13, 2017, an unknown individual accessed the covered entity's (CE) CEO’s email account and sent emails to its employees. The CEO’s email account contained a file with the electronic protected health information (ePHI) – names and client numbers – of approximately 1,273 individuals. The CE immediately took steps to implement additional technical safeguards for its email system and engaged a third-party service to assist in its ongoing privacy and security activities. The CE provided breach notification to HHS, and OCR provided technical assistance regarding the breach notification requirements pertaining to to the media and affected individuals.
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 | May 26, 2017 | 1,278 | HHS breach portal |
Similar Breaches Reported Around the Same Time
| Reported | Organization | People Affected | Industry |
|---|---|---|---|
| May 26, 2017 | Mississippi Division of Medicaid | 5,220 | Healthcare |
| May 26, 2017 | Arizona Department of Health Services | 2,500 | Healthcare |
| May 26, 2017 | AU Medical Center, Inc. | 5,600 | Healthcare |
| May 26, 2017 | Kennewick Public Hospital District, dba Trios Health | 942 in WA | Healthcare |
| May 26, 2017 | Beacon Health System | 1,239 | Healthcare |
| May 26, 2017 | FastHealth Corporation | 18,192 | Healthcare |
Questions
- Is the Sound Community Services, Inc. data breach letter legitimate?
- Sound Community Services, Inc. filed a breach notice with the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on May 26, 2017. 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 Sound Community Services, Inc. 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?
- Sound Community Services, Inc. told HHS that 1,278 people were affected.