DataBreaches.Net

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

Multnomah County notified 1,700 patients after discovering employee was forwarding emails to personal account

Posted on February 8, 2017 by Dissent

From Multnomah County, Oregon:

January 20, 2017

On August 24, 2012, a Health Department employee began automatically forwarding all emails received in the employee’s county email account to a personal Google email account not maintained by the county. Some of these emails included protected health information (PHI) subject to the Health Insurance Portability and Accountability Act (HIPAA) were forwarded.

Multnomah County personnel discovered the incident on Nov. 22, 2016 during a random audit. The county started an investigation and began collecting further information about what happened. During that investigation, the county found no evidence that messages in the personal email account were opened are read. Upon completing the investigation, county personnel verified that the personal email account was deleted and no longer accessible to the employee.

Because the employee was a member of a Health Department team, some emails had attachments with protected health information. The information disclosed may have included your first and last name, medical record number, medication name, prescription number, diagnosis, date of service and/or age.

The County has not found any indication that any Social Security number, home address or phone number was included. Because none of the messages in the employee’s personal email account appear to have been accessed, we believe there is a low risk that your information was further disclosed. However, the personal email account is maintained by Google and not the county. We are not aware of any other inappropriate uses or disclosures of your personal information.

Multnomah County and the County Health Department are committed to keeping your personal information private and we take many steps to protect it. We have policies and procedures for handling personal information which were reviewed with the staff member involved in this incident. We are also reviewing controls, business practices and policies to increase protections of personal information in response to this incident. We sincerely regret any inconvenience or worry this incident presents to you.

If you have questions or concerns about this letter, please contact us at 1-877-422-7676 and state case #1322 after the beep.

The incident was reported to HHS as impacting 1,700 patients.


Related:

  • NY: Gloversville hit by ransomware attack, paid ransom
  • 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.
  • Data breach in 42 Latvian municipalities: DVI imposes 300,000 euro fine on ZZ Dats
  • Kaufman County's data breach was their second one in three weeks
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
Category: Government SectorHealth DataInsiderU.S.

Post navigation

← Sports Direct hacked last year, but still hasn’t told its staff of data breach?
IL: Alton Steel employees report tax refund fraud following W-2 phishing incident (Updated) →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.