DataBreaches.Net

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

HHS corrects entry for LANAP & Implant Center breach

Posted on September 11, 2014 by Dissent

There’s been an interesting update to HHS’s breach tool for the entry concerning a breach reported by Dr. David DiGiallorenzo of the LANAP & Implant Center in Williamsport, Pennsylvania.

I had first noted the breach in December 2013, and then provided an update here. When the breach was added to HHS’s breach tool, I noted the addition and commented on the errors in what had been reported to HHS:

The LANAP & Implant Center breach reported here and here was reported by David DiGiallorenzo, D.M.D.  as occurring on September 17, 2012. That seems incorrect as the torrent was uploaded to a PirateBay site on February 18, 2010. Perhaps Dr. DiGiallorenzo confused date of discovery with date of breach? I’d ask them, but their lawyer has already said they’d have no further comment on the breach.  Surprisingly, Dr DiGiallorenzo seems to have reported that (only) 2,600 patients were affected by the breach. Inspection of the torrent reveals that over 11,000 individuals had PII and/or PHI in the database exposed online, so I’m really not sure how they got that number to report.  The incident was reported as “Unauthorized Access/Disclosure,Hacking Incident”,”Network Server, Electronic Medical Record,” and hopefully, HHS will confirm whether this really was a hack by a third party.

At the time, I  contacted HHS about the errors in what appeared on the breach tool, and raised a number of concerns with both HHS and the FTC concerning the incomplete and/or inaccurate disclosures to patients as well as the alleged retaliation experienced by the individual who brought the breach to the media’s attention.

On September 4, HHS updated the public breach tool entry to read:

“David DiGiallorenzo, D.M.D.”, PA,””, 11000, 02/18/2010,”Unauthorized Access/Disclosure, Hacking/IT Incident”, Other, 09/04/2014,

So HHS has now corrected the entry to show the correct number of patients affected and the correct date of the incident. Also, the entry no longer indicates “Hacking Incident,” but rather “Hacking/IT incident.” “Network Server, Electronic Medical Record” has been replaced by “Other.” I wish I knew what the “Other” stands for in this case, and I’m curious as to what OCR will find in its investigation.

Because there is no summary provided in their logs, it would appear that their investigation is still open. Seeing how OCR investigations into breaches reported in 2011 are first being closed now, I expect it will be a while before we see this investigation closed.


Related:

  • Maintenance Note
  • CISA Alert: Reported Supply Chain Compromise Affecting XZ Utils Data Compression Library, CVE-2024-3094
  • System Status Note
  • System Status Note
  • Fraudster's fake data breach claims should remind media to be careful what we report
  • "Pompompurin" taken into custody after violating conditions of pre-sentencing release on bond (1)
Category: Uncategorized

Post navigation

← D&J Optical sues former employees for misappropriation of patient/proprietary information
Yandy breach impacted over 44,000 online customers →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • 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

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • 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

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.