DataBreaches.Net

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

Riverside Health System notifies 919 patients after employee improperly accessed their information

Posted on December 31, 2013 by Dissent

I hope this is the last breach of PHI I’ll have to report in 2013, but since there’s still 5 hours to go, who knows? WAVY in Newport News, Virginia reports:

A local hospital is offering free credit monitoring after officials say an employee inappropriately accessed patients’ medical records.

According to Peter Glagola, Director of Public Relations at Riverside Health System, 919 medical records from September 2009 to October 2013 were accessed by the employee.

Those records included patients’ social security numbers, summary of the patients’ history and other information.

Read more on WAVY.

WTKR reports that the breach was discovered by a random company audit on November 1.

Because the inappropriate access went on for four years before it was detected, I’d say Riverside Health Systems has room for improvement in its monitoring/detection safeguards.

The coverage does not indicate what the employee’s motivation was, nor whether law enforcement was contacted. Nor does it mention which of their hospitals the employee worked at, or whether the employee was situated in a central administrative office. (Update: Daily Press reports that the employee was a licensed practical nurse, LPN, with Riverside Medical Group).

The statement from Riverside Health System posted to their website on December 29:

Medical Records Inappropriately Accessed by Team Member

Newport News, VA – Riverside Health System is offering free credit monitoring to several hundred patients affected by a privacy breach.

The breach was discovered during a random company audit on Nov. 1. After an investigation, Riverside’s Compliance Department determined that an employee had inappropriately accessed 919 medical records, spanning September 2009 through October 2013. The information accessed included patients’ social security numbers, a summary of the patient history and other information that appears in Riverside’s electronic medical record.

The employee has been terminated.

Riverside is contacting the patients affected by this event. All will be offered complementary three-bureau credit monitoring. The company has attempted to send notification letters to all patients and next of kin to those known to be deceased, but has been unable to locate current contact information for all affected patients. If you believe that you may be affected by this privacy incident and have not received a notification letter, you may call 1-877-753-6854 toll free and someone will be available to speak with you.

“Riverside would like to apologize for this incident,” said company Spokesperson Peter Glagola. “We are truly sorry this happened. We have a robust compliance program and ongoing monitoring in place, and that’s how we were able to identify this breach. We are looking at ways to improve our monitoring program with more automatic flags to protect our patients.”

Riverside is partnering with FairWarning®, a company that offers a patient breach and monitoring software tool, to expand audit capabilities.

 


Related:

  • 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
  • Heritage Provider Network $49.99M Class Action Settlement
  • Integris Health Agrees to $30 Million Settlement Over 2023 Data Breach
Category: Health Data

Post navigation

← ‘Wichcraft notice to customers
Accretive Health Settles FTC Charges That It Failed to Adequately Protect Consumers’ Personal Information →

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.