DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

FTC Offers Businesses Tips for Dealing with Medical Identity Theft

Posted on February 5, 2011 by Dissent

The Federal Trade Commission, the nation’s consumer protection agency, has information for health care providers and insurers about how to help patients minimize the risk of medical identity theft and deal with the consequences if they become victims of it.  Here are the highlights of the FTC’s new publication, Medical Identity Theft FAQs for Health Care Providers and Health Plans:

  • How would people know if they’re victims of medical identity theft? They could be billed for medical services they didn’t receive, contacted by a debt collector about a medical debt they don’t owe, see medical collection notices on their credit report that they don’t recognize, be told by their health plan that they’ve reached their limit on benefits, or be denied insurance because their medical records show a condition they don’t have.
  • What should health care providers and insurers do if they learn that a patient may be the victim of medical identity theft? They should conduct an investigation, understand their obligations under the Fair Credit Reporting Act, review their data security practices, and provide any necessary notifications that a data breach has occurred.
  • What should health care providers and insurers tell a patient who is the victim of medical identity theft? They should:
    • advise victims to take advantage of their rights under the HIPAA (Health Insurance Portability and Accountability Act) Privacy Rule.
    • encourage victims or potential victims to notify their health plans.
    • tell victims to file a complaint with the FTC at www.ftccomplaintassistant.govor by phone at             1-877-ID-THEFT       ( 1-877-438-4338); TTY:    1-866-653-4261;  and to check out the information at www.ftc.gov/idtheft.
    • encourage victims to file a report with local police, and send copies of the report to their health plan’s fraud department, their health care provider(s), and the three nationwide credit reporting companies – Equifax, Experian, and TransUnion.  Information on how to file a police report and reach the credit reporting companies is at www.ftc.gov/idtheft/consumers/defend.html.
    • encourage patients to look for signs of other misuses of their personal information by reviewing their credit reports.  The law requires each of three major nationwide credit reporting companies to give people a free copy of their credit report each year if they ask for it at www.AnnualCreditReport.com or  1-877-322-8228 .  If they find inaccurate or fraudulent information, they can visit www.ftc.gov/idtheft to learn how to get it corrected or removed.
  • How can health care providers and insurers help patients deter, detect, and defend against medical identity theft? They can order copies of the FTC’s consumer brochure, Medical Identity Theft in English or Spanish and make them available to patients.  Bulk copies are available at http://bulkorder.ftc.gov.  Health care providers and insurers can link to it, copy it, or adapt it for their websites or newsletters.

Source: FTC


Related:

  • Safaricom-Backed M-TIBA Victim of a Possible Data Breach Affecting Millions of Kenyans
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
Category: Health Data

Post navigation

← UK: Tayside Police officer admits leaking sensitive data
Thousands of Medi-Cal records of San Franciscans breached →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.