DataBreaches.Net

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

Fairbanks Hospital notifies patients after discovering employees could have been inappropriately accessing patient records for years (UPDATED)

Posted on December 22, 2016 by Dissent

Fairbanks Hospital in Indianapolis is notifying an undisclosed number of patients that employees could have been accessing protected health information of patients since at least November 2013 (and possibly earlier). The information that was accessed included current and former patients’ social security numbers, contact information, diagnosis, treatment and health insurance.

In a notification dated December 16, the hospital writes that they are unaware of any actual or attempted misuse of any protected health information.

Of concern, it appears that their investigators were not able to determine whether any employee actually accessed any patient’s record inappropriately. So it may well be that some employees snooped on records, and yet, the hospital would not have been able to detect that.  And if it couldn’t detect whether the employees were accessing PHI records inappropriately, it sounds like they might have to notify every patient seen at the hospital since November 2013. DataBreaches.net has sent an inquiry to Fairbanks via their site contact form and will update this post as more information becomes available.

From their notification:

December 16, 2016

To Our Valued Patients,

Fairbanks Hospital recently discovered an event that may affect the security of certain current and former patients’ protected health information. While we are unaware of any actual or attempted misuse of any protected health information, we are providing potentially impacted patients with information about the event, steps taken since discovering the incident, and what they can do to better protect against identity theft and fraud, should they feel it is appropriate to do so.

What Happened? On October 18, 2016, Fairbanks became aware that some files on our internal network that contained patient information were electronically accessible to Fairbanks employees, including employees who were not intended to have access to patient information. Fairbanks hired an outside computer forensics expert to determine the nature and scope of this issue. The investigation has determined that this issue existed since at least November of 2013, however we are unable to determine whether the issue existed prior to that time. We have now corrected this issue so that only the appropriate Fairbanks personnel has electronic access to files containing patient information.

The patient information impacted by this issue was only accessible to Fairbanks employees. Because we have not been able to confirm whether this issue ever resulted in inappropriate access to patient information by a Fairbanks employee, we are providing notice of this incident to all potentially affected individuals in an abundance of caution.

What Information Was Involved? Based upon our investigation, it was determined that the following types of patient information were contained on one or more files on our network that were impacted by this issue: name, Social Security number, date of birth, contact information, patient identification number, diagnosis, treatment information, health insurance information, and information relating to initial admission and scheduling of appointments. The types of information impacted were different depending on the individual patient, with the majority of affected patients only having their name and limited information relating to initial admission and scheduling of appointments impacted. Fairbanks is unaware of any actual or attempted misuse of patient information as a result of this incident.

What Are We Doing? Fairbanks takes the security of our patients’ information very seriously. We have taken steps to ensure only the appropriate Fairbanks personnel has access to patient information. We are mailing written notice of this incident to all potentially impacted individuals for whom we have contact information, along with the same information that is contained below, entitled Steps You Can Take to Protect Against Identity Theft and Fraud. We are also reporting this incident to the U.S. Department of Health and Human Services and news media outlets servicing the state of Indiana.

[…]

UPDATED DEC. 23: Well, they didn’t answer my emailed inquiry other than to just send me the same notification I had already seen, but it appears that on Dec. 16, they submitted a report to HHS indicating that 12,994 patients were affected.

 


Related:

  • Former U.S. Soldier Pleads Guilty to Hacking and Extortion Scheme Involving Telecommunications Companies
  • DOGE Denizen Marko Elez Leaked API Key for xAI
  • Four people bailed after arrests over cyber attacks on M&S, Co-op and Harrods
  • Texas Enacts Electronic Health Record Data Localization Law
  • United Australia Party confirms ransomware attack, personal data and email correspondence exposed
Category: Breach IncidentsCommentaries and AnalysesHealth DataInsiderOf NoteU.S.

Post navigation

← OH: Henry County home health and hospice patients’ records stolen
FL: Palm Beach sheriff’s deputy arrested in ID theft case →

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

  • North Country Healthcare responds to Stormous’s claims of a breach
  • Gladney Adoption Center had serious data exposures in the past few months. What will they do to prevent more?
  • Former U.S. Soldier Pleads Guilty to Hacking and Extortion Scheme Involving Telecommunications Companies
  • DOGE Denizen Marko Elez Leaked API Key for xAI
  • Four people bailed after arrests over cyber attacks on M&S, Co-op and Harrods
  • RansomedVC is back — and is still attacking its competitors
  • Texas Enacts Electronic Health Record Data Localization Law
  • United Australia Party confirms ransomware attack, personal data and email correspondence exposed
  • Armenian National Extradited to the United States Faces Federal Charges for Ransomware Extortion Conspiracy
  • 70% of healthcare cyberattacks result in delayed patient care, report finds

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

  • Texas Enacts Electronic Health Record Data Localization Law
  • Upstate NY county clerk again refuses to enforce Texas abortion judgment
  • Attorney General James Leads Coalition Urging Congress to Protect Americans from Masked ICE Agents
  • Attorney General Tong Announces $85,000 Settlement with TicketNetwork for Violations of the Connecticut Data Privacy Act​
  • Fourth Circuit upholds West Virginia ban on abortion pills
  • Meta fixes bug that could leak users’ AI prompts and generated content
  • The EU’s Plan To Ban Private Messaging Could Have a Global Impact (Plus: What To Do About It)

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.