DataStat, Inc. Data Breach (February 2016)
DataStat, Inc. reported a data breach to the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Feb 12, 2016. It affected 552 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: Paper/Films.
- Type of organization (HHS): Business Associate.
- Industry: Healthcare.
- Based in: Michigan.
An employee of a business associate (BA), DataStat, erroneously misdirected surveys to 487 individuals after failing to following the BA’s re-print protocol after a printer paper jam. The types of protected health information (PHI) involved in the breach included demographic information, including names and addresses. The CE provided breach notification to HHS and affected individuals. The BA also improved technical safeguards to assist with quality assessment checks and sanctioned the involved employee with a written warning. OCR obtained documentation that the BA implemented the corrective actions steps listed above.
Case summary from the U.S. Department of Health and Human Services, Office for Civil Rights
What Was Exposed
Information involved, as described in the filings:
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 | Feb 12, 2016 | 552 | HHS breach portal |
Other Breaches Reported by DataStat, Inc.
| Reported | Organization | People Affected |
|---|---|---|
| Aug 8, 2022 | DataStat, Inc. | 1,650 |
Similar Breaches Reported Around the Same Time
| Reported | Organization | People Affected | Industry |
|---|---|---|---|
| Feb 12, 2016 | BlueCross BlueShield of South Carolina | 998 | Healthcare |
| Feb 12, 2016 | Radiology Regional Center, PA | 483,063 | Healthcare |
| Feb 12, 2016 | Magnolia Health Corporation | – | Healthcare |
| Feb 15, 2016 | Alliance Health Networks, LLC | 42,372 | Healthcare |
| Feb 9, 2016 | Washington State Health Care Authority (HCA) | 91,187 | Healthcare |
| Feb 8, 2016 | Seim Johnson, LLP | 30,972 | Healthcare |
Questions
- Is the DataStat, Inc. data breach letter legitimate?
- DataStat, Inc. filed a breach notice with the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Feb 12, 2016. 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 DataStat, 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?
- DataStat, Inc. told HHS that 552 people were affected.