How Can Medical Practices Protect Against HIPAA Violations Caused by Phishing Emails?
"We train our employees on HIPAA, but phishing emails are becoming much harder to recognize. What should our medical practice do to prevent an employee from accidentally giving a hacker access to patient information?"
Your strongest phishing defense isn’t a single software product. It is a combination of people, processes, and technology.
Employees should know how to recognize suspicious messages, your practice should have a simple procedure for verifying unusual requests, and your IT safeguards should make it harder for a stolen password or malicious attachment to become a major breach.
Phishing attacks are designed to trick employees into clicking malicious links, opening attachments, revealing passwords, approving fraudulent login requests, or taking another action that gives an attacker access to systems containing electronic protected health information (ePHI).
The HHS Office for Civil Rights (OCR) specifically identifies phishing as a frequent social-engineering attack and recommends security awareness training, simulated phishing exercises, anti-phishing technologies, access controls, and other safeguards to reduce the risk.
A Strong Phishing Defense
Train → Verify → Protect → Report → Respond → Review
The goal isn’t to make every employee a cybersecurity expert. It’s to make sure employees recognize when something doesn’t look right, know how to verify suspicious requests, and report mistakes immediately.
Why This Matters
Phishing works because attackers don’t always try to defeat your technology. They try to defeat your employees. A criminal doesn’t necessarily need to hack directly through a sophisticated firewall if an employee can be persuaded to voluntarily provide a username and password.
Today’s phishing messages can also be remarkably convincing. An attacker may impersonate a physician, manager, vendor, IT technician, financial institution, delivery company, or familiar technology platform. Social-engineering attacks can arrive through email, text messages, phone calls, and even video.
That changes the question your practice should be asking.
Instead of: “Do our employees know not to click suspicious emails?”
Ask: “Would our employees recognize a phishing email that didn’t look suspicious?”
Teach Employees That Phishing Is More Than a Bad Link
Employees often associate phishing with obvious spam. That’s dangerous because modern attacks may look professional and familiar. A phishing attempt could appear to be:
- A Microsoft 365 password-expiration warning
- An EHR login request
- A message from your IT company
- A document-sharing notification
- An invoice from a vendor
- A voicemail notification
- A message from another employee
- A request from a physician
- A benefits or payroll message
- A delivery notification
- A request to review a document
- A patient-related message
The attacker may be trying to steal login credentials, install malicious software, obtain sensitive information, initiate a fraudulent payment, or gain access to other systems. OCR warns that phishing sites can closely resemble legitimate websites and trick employees into entering usernames and passwords that attackers can then use against the organization.
Your training therefore needs to go beyond: “Don’t click weird links.” Employees need to recognize suspicious requests and behavior.
Teach Employees to Recognize Urgency and Pressure
Phishing messages frequently try to short-circuit normal decision-making. The message may say:
Examples of Pressure Tactics
- “Your account will be disabled in 30 minutes.”
- “I need this patient information immediately.”
- “Your mailbox is over capacity. Log in now.”
- “I need you to take care of this before I go into a meeting.”
- “You have a secure document waiting. Click here.”
Urgency is a reason to verify—not a reason to bypass procedure.
Train staff to stop when a request unexpectedly asks them to log in, provide credentials, send sensitive information, download something, change payment information, or perform an unusual task.
Never Share Passwords or Authentication Codes
Make this rule extremely clear: No legitimate coworker, physician, manager, vendor, or IT technician should need an employee’s password.
Employees should also be suspicious of unexpected requests for authentication codes or prompts asking them to approve a login they didn’t initiate. Passwords and authentication factors exist to establish the identity of the person accessing your systems. The HIPAA Security Rule requires procedures to verify that people seeking access to ePHI are who they claim to be.
If an employee receives an unexpected authentication request, the correct response isn’t: “I’ll approve it and see what happens.” It’s: “I didn’t initiate this. I need to report it.”
Verify Unusual Requests Outside the Email
This is one of the simplest protections a medical practice can implement. Suppose an employee receives an email that appears to come from a physician: “I’m locked out of the EHR. Send me your login so I can check Mrs. Jones’ chart.”
Don’t reply: “Is this really you?” If the attacker controls or spoofed the communication, the attacker can simply respond: “Yes.”
Instead, verify through a separate trusted channel.
Call the physician using a known telephone number. Contact IT through your normal help desk. Open Microsoft 365 or another service using your normal bookmark instead of the link contained in the message.
Teach employees: Don’t verify a suspicious message using the suspicious message.
Give Employees an Easy Way to Report Suspicious Emails
Employees need to know exactly what to do when something seems wrong.
- Should they forward the message to IT?
- Use a “Report Phishing” button?
- Call the practice manager?
- Open a help-desk ticket?
- Contact your managed IT provider?
If employees don’t know, they may delete the email and move on—or worse, interact with it while trying to determine whether it’s legitimate. OCR recommends having a protocol that tells workforce members how to respond to suspicious email, including reporting it to appropriate IT personnel.
Make the procedure simple enough that an employee can follow it immediately.
Don’t Punish Employees for Reporting a Mistake Quickly
Imagine an employee clicks a link and enters a password. Thirty seconds later, the employee realizes: “I think that was fake.”
You want that employee to report the mistake immediately. You don’t want them spending the next two hours hoping nothing happens because they’re afraid they’ll get in trouble. The sooner your IT/security team knows, the sooner it may be able to reset credentials, terminate sessions, isolate a device, investigate account activity, preserve evidence, and determine whether ePHI was affected.
Build a culture where employees understand: Making a mistake is bad. Hiding the mistake can make it much worse.
Use Technical Safeguards to Back Up Your Employees
Training should never be your only phishing defense. OCR identifies technical measures that can help mitigate social-engineering threats, including anti-phishing technologies, tools that identify known malicious sources, link and attachment scanning, behavioral analysis, granular role-based access, network segmentation, and strict controls over privileged accounts.
Your safeguards should be based on your practice’s risk analysis and environment rather than a generic checklist. The current HIPAA Security Rule requires regulated entities to assess risks and vulnerabilities to ePHI and implement reasonable and appropriate measures to reduce them.
Your IT team or security provider should be able to explain what protections exist and what happens when one fails.
Use Multi-Factor Authentication Where Appropriate
A stolen password becomes much more dangerous when that password alone opens the door. Multi-factor authentication can add another layer between stolen credentials and your systems. It doesn’t eliminate phishing. Attackers have developed techniques that attempt to defeat MFA as well.
That is why employees should also be taught never to approve an authentication request they didn’t initiate. Technology creates another barrier. Employee awareness helps keep that barrier from being bypassed.
Limit the Damage One Compromised Account Can Cause
Ask yourself: If this employee’s credentials were stolen today, what could the attacker access?
That is an important security question. The Security Rule requires appropriate workforce authorization and access management for ePHI. An employee shouldn’t automatically have access to systems and information that aren’t necessary for the person’s responsibilities.
Strong access controls don’t necessarily prevent the initial phishing attack. They can help limit its impact.
Include Personal Email and Personal Devices in Your Risk Discussion
Your phishing risk doesn’t necessarily stop at the employee’s business inbox. OCR specifically warns that attackers may target an employee’s personal email. An employee who accesses personal email from a work computer could click a malicious link that compromises the work device. Likewise, a compromised personal device may create risk if that device is also used to access work email or other practice systems.
Your practice should therefore establish clear policies addressing personal email and device use based on your particular environment and risk analysis. Don’t assume: “It’s their personal account, so it isn’t our cybersecurity problem.” Look at how personal technology intersects with your practice systems.
Test Whether Your Training Actually Works
An annual presentation followed by: “Click here to certify that you completed HIPAA training.” doesn’t necessarily tell you whether employees can recognize a convincing phishing attack. OCR has specifically identified simulated phishing emails as one method organizations can use to assess workforce awareness and provide security reminders.
The objective shouldn’t be to embarrass employees who click. Use results to identify where additional training is needed. If many employees fall for the same simulation, ask: “What does this tell us about our training and safeguards?”
Make Providers and Managers Part of the Training
Don’t make cybersecurity training something only the front desk and billing staff attend. Managers and providers can be attractive targets because their accounts may provide valuable access and because employees may be more likely to comply quickly with requests that appear to come from leadership. OCR specifically notes that management should participate in security training and that senior executives may be targeted through phishing attacks known as “whaling.”
Your physician shouldn’t be exempt because: “He doesn’t have time for HIPAA training.” A high-access user can create high-impact risk.
The PAUSE Test
Use the PAUSE Test before acting on an unexpected email.
Employees don’t need to prove that an email is malicious. They simply need to recognize that something doesn’t seem right. Then they should know exactly who can help.
Real Practice Example
A medical assistant receives an email that appears to come from one of the practice’s physicians. The physician says he is having trouble accessing the EHR while away from the office and urgently needs information about a patient before speaking with a specialist. The message contains familiar terminology, the physician’s name, and details that make it appear legitimate.
The email asks the employee to click a link and sign into a document-sharing portal. Instead of clicking, the employee calls the physician using the telephone number already stored in the practice directory. The physician says: “I didn’t send that.”
The employee reports the message to IT, which investigates and alerts other employees. That employee didn’t need advanced cybersecurity skills. She needed three habits:
Recognize Something Unusual → Verify Independently → Report It
Is Phishing Specifically a HIPAA Risk?
Yes. OCR identifies phishing and other social-engineering attacks as reasonably anticipated threats that HIPAA regulated entities should consider when implementing measures to protect ePHI.
Does HIPAA Require Phishing Training?
The current HIPAA Security Rule requires a security awareness and training program for workforce members, including management. OCR specifically recommends incorporating current threats such as phishing into security awareness activities.
Is Clicking a Phishing Email Automatically a HIPAA Breach?
No. A suspicious click by itself doesn’t automatically establish that a reportable breach of PHI occurred. Your practice needs to investigate what happened, determine whether systems or ePHI were compromised, and apply the HIPAA Breach Notification Rule when applicable.
Should We Run Fake Phishing Tests on Employees?
Simulated phishing can be a useful component of your security awareness program. OCR specifically describes simulated phishing emails as a way to test workforce knowledge and provide security reminders.
Can a Phishing Attack Really Lead to HIPAA Enforcement?
Yes. In April 2025, OCR announced a $600,000 settlement involving a healthcare network after compromised email accounts from a phishing attack resulted in a breach affecting nearly 200,000 people. OCR’s investigation raised concerns involving HIPAA Privacy, Security, and Breach Notification requirements.
Warning Signs of a Phishing Email
Teach employees to slow down when a message:
One warning sign doesn’t prove an email is malicious.
It means: Stop and verify before acting.
Phishing Protection Checklist
Bottom Line
Phishing prevention is not simply saying don’t click on suspicious emails. Today’s attacks may not look suspicious. Your employees need practical habits for recognizing unusual requests, independently verifying identities, protecting credentials, reporting suspicious messages, and quickly admitting when they may have made a mistake.
Your practice also needs technical safeguards that reduce the likelihood that one successful phishing attempt turns into widespread access to ePHI. Build your defense around a simple process: Train → Verify → Protect → Report → Respond → Review
The goal isn’t to eliminate human error completely. It’s to make one employee’s mistake much less likely to become your next HIPAA breach.
Key Takeaways
- Phishing should be treated as a HIPAA security risk, not merely an IT problem.
- Train every workforce member who could encounter phishing attempts, including managers and providers.
- Teach employees to verify unusual requests through a second trusted communication method.
- Never allow employees to share passwords or authentication codes.
- Use technical protections to reduce the number of malicious messages that reach employees.
- Limit system access so one compromised account cannot expose more information than necessary.
- Make reporting suspicious emails easy and immediate.
- Teach employees to report accidental clicks instead of hiding them.
- Test your workforce periodically with simulated phishing exercises when appropriate.
- Use phishing incidents and test results to improve your security program.
Strengthen Your Practice’s HIPAA and Cybersecurity Defenses
Cybercriminals don’t need to defeat every safeguard protecting your practice. Sometimes they need only one employee to click the wrong link, reveal a password, or respond to a convincing request.
Healthcare Training Leader’s All-Access Training Pass gives your team practical, expert-led training on HIPAA privacy and security, cybersecurity, medical records, compliance, billing, credentialing, front desk operations, and other issues your practice handles every day.
Give your team the skills to recognize risks before an ordinary email becomes an expensive security incident.
Why Trust Healthcare Training Leader?
Healthcare Training Leader has helped more than 68,000 healthcare professionals at 10,000+ practices strengthen their skills and tackle the operational, financial, and compliance challenges they face every day.
Cybersecurity threats change quickly, but your employees still need practical guidance they can use in real situations. Our expert-led training focuses on turning complicated HIPAA and cybersecurity requirements into clear, actionable guidance your team can put to work.
Meet Your Expert
Brian L. Tuttle
Brian is a Certified Professional in Health IT (CPHIT), Certified HIPAA Professional (CHP), Certified HIPAA Administrator (CHA), Certified Business Resilience Auditor (CBRA), Certified Information Systems Security Professional (CISSP) with over 17 years’ experience in Health IT and Compliance Consulting.
With vast experience in health IT systems (i.e. practice management, EHR systems, imaging, transcription, medical messaging, etc.) as well as over 17 years’ experience in standard Health IT with multiple certifications and hands-on knowledge, Brian serves as compliance consultant and has conducted onsite and remote risk assessments for over 1000 medical practices, hospitals, health departments, insurance plans, and business associates throughout the United States.
In addition, Mr Tuttle has served in multiple litigated court cases serving as an expert witness offering input related to best practices and requirements for securing and providing patient access to protected health information. Mr. Tuttle has also worked directly with the Office of Civil Rights (OCR) both in defending covered entities and business associates as well as being asked by the Federal government to audit covered entities and business associates on behalf of the OCR.
Additional Resources
-
What Is the Best Way to Properly Destroy Medical Records?
Destroying old patient records requires more than putting paper through a shredder or deleting an electronic file. Know how to verify records are eligible for destruction, choose secure...
-
Protect Your Practice From Costly HIPAA Errors, Meet Federal Regs
Simply providing the same basic HIPAA run-through each year isn’t enough anymore. Protect your practice with this expert-led HIPAA Masterclass.
-
One Bad Click Can Trigger a HIPAA Breach: Protect Your Practice From Phishing
Your medical practice can invest in firewalls, security software and sophisticated technology, but an attacker may still target the person sitting at the computer. A convincing email appears...
