DataBreaches.Net

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

Easy Question, Complicated Answer: What Does It Take to Stop Workers From Snooping?

Posted on December 3, 2025 by Dissent

One of the most worrying concerns DataBreaches and Protenus reported each year when reporting on breaches of health data was the insider threat. Often the insider threat takes the form of “snooping” out of curiosity. At other times, it may have more nefarious motives, such as obtaining information on an adversary or relative to embarrass them publicly on social media or to use information to perpetrate identity theft or fraud.  In Report on Patient Privacy 25, no. 11 (November, 2025), Theresa Defino addresses the snooping issue by discussing a presentation by UHealth (the University of Miami Health System). Unfortunately, as Defino reports, UHealth was not particularly forthcoming in providing details about a significant incident it experienced.

If the whole point of networking is to share experiences and learn from each other, UHealth’s reluctance to be more transparent is not particularly admirable. Had they acknowledged what went wrong in their preventive approach, how they might have been able to detect it sooner, and what entities can do to prevent what happened to them, the presentation would probably have been even more helpful.

That said, read Defino’s report, which includes:

Point Is ‘Not to Fire’ People

Tuya added that the Privacy Rule “is clear that patients have a right to keep their health information confidential, and that right applies whether the patient is a stranger, a friend, someone you see at the grocery store or someone that you see on TV. Addressing employee snooping also matters because it can lead to some serious consequences for employees and organizations.”

“Something that we see a lot is…access to a child’s record,” Tuya said, where the employee uses their work credentials to access the electronic health record (EHR) rather than through being an authorized user via the patient portal, or a spouse checks on an appointment for a partner.

Many institutions “just take the position that all personal access is inappropriate,” but they also may apply lesser disciplinary measures for this sort, Tuya said.

It could happen that a provider accessing a family member’s record is actually caring for that individual, so it will be crucial to know if this is the case and whether it is allowed by the organization’s bylaws, Lawrence said. Similarly, that provider might call in a prescription. “It’s probably not a privacy violation,” but it could violate other policies, Lawrence said.

When crafting a zero-tolerance or a low-tolerance policy that may lead to termination, “you want that termination language in there at some point,” Lawrence said. But she added that the “whole point of doing this is not to fire the most people. The point of you doing this is almost a little fear” generation, and sending a message so that employees are “taking this seriously.”

But under UHealth’s policy, not every violation results in termination.

That seems appropriate — it is important to determine what the individual’s motivation was and what their understanding was of policy and procedures.

Read more at Report on Patient Privacy 25, no. 11 (November, 2025), republished on JDSupra.


Related:

  • Update on Dos-OP's report on Nova RaaS
  • HHS OCR Seeks Questions About HIPAA Security Rule Risk Management Requirement
  • John P. Meehan Agency was hacked in July 2024. Affected customers were first finding out in November 2025.
  • Ransomware blog claims New Horizons Medical has been attacked
  • FTC Takes Action Against Education Technology Provider for Failing to Secure Students’ Personal Data
  • Data breach hits 'South Korea's Amazon,' potentially affecting 65% of country’s population
Category: Commentaries and AnalysesHealth DataHIPAAInsiderU.S.

Post navigation

← Update on Dos-OP’s report on Nova RaaS
Cyberattack on Puerto Rico IT vendor Truenorth hits 3 agencies →

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

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

  • Teen who allegedly stole millions of personal data records arrested in Spain
  • Akira ransomware: FBI tallies 250 million in payouts
  • IE: HSE confirms second ransomware attack but ‘no evidence’ patient data was stolen
  • Examining impact of federal relief program after major healthcare cyberattack — Research Brief
  • Justice Department Announces Actions to Combat Two Russian State-Sponsored Hacking Groups
  • Should entities be required to disclose the name of a vendor if the breach was at the vendor’s?
  • The Hidden Risks of Information Disclosure: A Costly Lesson from Cornwall
  • Defense Bill Would Require New Cyber Requirements for Some DoD Telecom Contracts
  • Tell the truth, or someone will tell it for you — Trumbull County, Ohio edition (1)
  • US Posts $10 Million Bounty for Iranian Hackers

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

  • U.S. Plans to Scrutinize Foreign Tourists’ Social Media History
  • ANNOUNCEMENT: EFF Launches Age Verification Hub as Resource Against Misguided Laws
  • FTC Denies Petition from SpyFone App CEO to Vacate 2021 Order
  • Privacy concerns raised as Grok AI found to be a stalker’s best friend
  • PRIVACY—S.D. Cal.: Employee did not waive privacy right in personal email data on company provided laptop, (Dec 5, 2025)

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: Dissent.73
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.