DataBreaches.Net

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

Henry Schein settles FTC charges it misled customers about encryption of patient data

Posted on January 5, 2016 by Dissent

It appears the FTC acted on a complaint I filed with them last year concerning Henry Schein Dental’s use of the word “encryption” in their marketing and their refusal to individually notify customers that the “encryption” provided by Dentrix G5  was not NIST-grade encryption that would give them Safe Harbor under HIPAA.

Background on my concerns and why I filed a complaint can be found  here, here, and here. Kudos to the researcher who identified the vulnerability and helped me understand its significance. He also filed a supplemental to my complaint to the FTC, further explaining the “encryption” issue.

I’m gratified to see that the FTC agreed with every concern I raised in my complaint.

Here’s the FTC’s press release, with links to their complaint and proposed consent order:

Henry Schein Practice Solutions, Inc. (“Schein”), the provider of leading office management software for dental practices, will pay $250,000 to settle Federal Trade Commission charges it falsely advertised the level of encryption it provided to protect patient data.

The FTC’s complaint alleges that Schein marketed its Dentrix G5 software to dental practices around the country with deceptive claims that the software provided industry-standard encryption of sensitive patient information and, in doing so, ensured that practices using its software would protect patient data, as required by the Health Insurance Portability and Accountability Act (HIPAA).

“Strong encryption is critical for companies dealing with sensitive health information,” said Jessica Rich, Director of the FTC’s Bureau of Consumer Protection. “If a company promises strong encryption, it should deliver it.”
In its complaint, the FTC alleges that Schein was aware that Dentrix G5 used a less complex method of data masking to protect patient data than Advanced Encryption Standard (AES), which is recommended as an industry standard by the National Institute of Standards and Technology (NIST) and provides the appropriate protection to meet certain regulatory obligations under HIPAA. Nevertheless, for two years, Schein touted the product’s “encryption capabilities” for protecting patient information and meeting “data protection regulations” in multiple marketing materials, including newsletters and brochures targeted at dentists.

Under the terms of the proposed consent order, Schein will be required to pay $250,000 to the FTC. In addition, the company will be prohibited from misleading customers about the extent to which its products use industry-standard encryption or the extent to which its products help ensure regulatory compliance or protect consumers’ personal information.

In addition, Schein will be required to notify all of its customers who purchased Dentrix G5 during the period when the company made the misleading statements that the product does not provide industry-standard encryption and provide the FTC with ongoing reports on the notification program.

The Commission vote to issue the administrative complaint and to accept the consent agreement was 4-0. The FTC will publish a description of the consent agreement package in the Federal Register shortly. The agreement will be subject to public comment for 30 days, beginning today and continuing through Feb. 4, 2016, after which the Commission will decide whether to make the proposed consent order final. Interested parties can submit comments electronically.

Henry Schein Responds

Henry Schein reached out to me today after the announcement. Although they will not be issuing a press release, they did send me a statement which says, in part:

Henry Schein is committed to providing our customers products and services they can rely on to build their practices and provide quality care. This commitment is at the heart of all we do. With that as context, we had a disagreement with the FTC about how we used the word “encrypted” in Dentrix G5 marketing from early 2012 to January 2014.

[…]

The settlement with the FTC does not represent an admission of wrongdoing regarding the Dentrix product. We made a decision to settle with the FTC to avoid long and costly litigation. We would much prefer to invest our resources into products and services that help our customers operate successful practices and provide quality patient care.

[…]

Dentrix provides multiple features to help protect patient data, especially
when used in combination with practice security measures based upon standards, best practices, laws, and regulations. We do recommend that offices employ some form of full disc encryption that utilizes AES-level encryption.

And Now You Know

In a way, this consent order is a better outcome for patients and consumers than if Henry Schein had taken my advice to individually notify customers, in which case, I wouldn’t have filed a complaint. As a result of this consent order, we now have guidance as to how the FTC views the use of the word “encryption” in marketing or advertising. And that might also have significant implications for breach notification letters in the event of a breach. If an entity tells consumers that data were “encrypted” when they were only MD5 hashed, how might the FTC view that claim? I would bet that they might find that a deceptive (“unfair”) practice that puts consumers at risk by not accurately informing them of how secure the data were and the likelihood that someone could crack the “encryption.”

Update: The FTC Blog for Businesses also has a post on this matter, FTC takes on toothless encryption claims for dental practice software.

Category: Business SectorCommentaries and AnalysesHealth DataOf NoteOtherU.S.

Post navigation

← Southern New Hampshire U. still investigating database leak exposing over 140,000 records
Latvian Hacker Deniss Calovskis Sentenced to Time Served →

7 thoughts on “Henry Schein settles FTC charges it misled customers about encryption of patient data”

  1. Justin Shafer says:
    January 5, 2016 at 9:47 pm

    All is well that ends well! =) Thanks Pogo!

    1. Dissent says:
      January 6, 2016 at 6:48 am

      I’m still surprised by this! I just wish FTC had more resources and had done something with other complaints I’ve submitted over the past few years.

  2. crankycanuck says:
    January 7, 2016 at 7:02 pm

    “we now have guidance as to how the FTC views the use of the word “encryption” in marketing or advertising.”

    Very nice, significant, and big win for both privacy and consumer protection.

    “Industry-standard encryption” and “industry-standard protection” were terms I also questioned when Bell got hacked. I never really gave it another thought since then.

    I think this is a bigger win than what I originally realized. We are going to see reference to this little gem again.

    The FTC blog title cracked me up. I mean… that’s like salt in the wound.

  3. Darrell Pruitt says:
    January 9, 2016 at 11:51 am

    Pogo and Justin, nice work both of you.

    1. Dissent says:
      January 9, 2016 at 3:15 pm

      Thanks, Darrell.

      This demonstrates what can happen when researchers bring their findings to privacy advocates and help us understand the issue or risk. I doubt Justin would have ever filed an FTC complaint, and for my part, I wouldn’t have understood the VU enough to care about it without his patient assistance. And of course, some of this wouldn’t have happened except for a few experts who agreed to comment on the record as to whether “data masking” is “encryption” or not.

      Team work.

      1. Justin Shafer says:
        January 10, 2016 at 1:57 pm

        I believe your exact words were “grow a spine”. 😉

        1. Dissent says:
          January 10, 2016 at 2:43 pm

          I conveniently don’t remember, but that sounds like something I might have said, yes.

Comments are closed.

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

  • Department of Justice says Berkeley Research Group data breach may have exposed information on diocesan sex abuse survivors
  • Masimo Manufacturing Facilities Hit by Cyberattack
  • Education giant Pearson hit by cyberattack exposing customer data
  • Star Health hacker claims sending bullets, threats to top executives: Reports
  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang Leaked
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)

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

  • ARC sells airline ticket records to ICE and others
  • Clothing Retailer, Todd Snyder, Inc., Settles CPPA Allegations Regarding California Consumer Privacy Act Violations
  • US Customs and Border Protection Plans to Photograph Everyone Exiting the US by Car
  • Google agrees to pay Texas $1.4 billion data privacy settlement
  • The App Store Freedom Act Compromises User Privacy To Punish Big Tech
  • Florida bill requiring encryption backdoors for social media accounts has failed
  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.