DataHEALTH, Inc. Data Breach (January 2022)
DataHEALTH, Inc. reported a data breach to the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Jan 20, 2022. It affected 3,649 people.
What Happened
- Cause: Hacking (outsiders broke into computer systems).
- Where the information was: Network Server.
- Type of organization (HHS): Business Associate.
- Industry: Healthcare.
- Based in: Texas.
The business associate (BA), DataHEALTH, reported that it was the subject of a ransomware attack that affected the protected health information (PHI) of 3.649 individuals. The PHI involved included names, addresses, dates of birth, Social Security numbers, medications, diagnoses, and other treatment information. The BA notified HHS, affected individuals, and the media, In response to the breach, the CE provided complimentary credit monitoring services and implemented additional administrative, technical, and security safeguards to better protect its PHI.
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 Your Social Security Number Was Exposed
- Freeze your credit with all three bureaus (Equifax, Experian and TransUnion). It is free, takes a few minutes online, and stops new accounts being opened in your name. You can lift it when you need credit.
- Get an Identity Protection PIN from the IRS (irs.gov/ippin). It stops anyone else filing a tax return with your number.
- Take the free credit monitoring if the letter offers it, and note the enrollment deadline.
- Check your credit reports for free at annualcreditreport.com, and look for accounts you don't recognize.
- If someone has already used your number, report it at IdentityTheft.gov for a recovery plan.
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.
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 20, 2022 | 3,649 | HHS breach portal |
Similar Breaches Reported Around the Same Time
| Reported | Organization | People Affected | Industry |
|---|---|---|---|
| Jan 20, 2022 | Thomas Jefferson University Hospital, Inc. | 5,239 | Healthcare |
| Jan 20, 2022 | Abington Memorial Hospital dba Jefferson Abington Hospital | 3,475 | Healthcare |
| Jan 20, 2022 | Medical Review Institute of America | 2,406 | Healthcare |
| Jan 21, 2022 | Advocates, Inc. | 70,031 | Healthcare |
| Jan 21, 2022 | Allegheny Health Network Home Infusion, LLC | 15,342 | Healthcare |
| Jan 21, 2022 | University of Arkansas for Medical Sciences | 518 | Healthcare |
Questions
- Is the DataHEALTH, Inc. data breach letter legitimate?
- DataHEALTH, Inc. filed a breach notice with the U.S. Department of Health and Human Services (HHS) Office for Civil Rights on Jan 20, 2022. 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 DataHEALTH, 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?
- DataHEALTH, Inc. told HHS that 3,649 people were affected.