How Clinics Should Respond to a Phishing Email

Kevin Henry

Incident Response

Published Updated

6 minutes read
Share this article
How Clinics Should Respond to a Phishing Email

What should clinic staff do when they receive a suspicious email?

Do not click links, open attachments, reply, or use contact details in the message. A suspicious email may be a phishing attempt even if it appears to come from a colleague, a patient, a vendor, or a familiar organization.

Report it promptly using your clinic’s security incident reporting procedure or built-in “report phishing” feature. Avoid forwarding it through ordinary email unless your IT team instructs you to; use the clinic’s approved reporting channel so the original message and its technical details can be reviewed. Follow IT or security staff’s directions about whether to retain or delete it.

The HIPAA Security Rule requires covered entities to have procedures for identifying and responding to suspected or known security incidents, mitigating harmful effects where practicable, and documenting incidents and outcomes. HHS guidance on Security Incident Procedures explains these requirements.

How can staff recognize a phishing email?

Look for signs that the message is unexpected or trying to rush you into action. Common warning signs include an unfamiliar or slightly altered sender address, an unexpected attachment, a shortened or mismatched link, an unusual request for credentials or patient information, and urgent demands to pay, sign in, or change account details.

Pay attention to context as well as spelling and design. A polished message, familiar logo, or name you recognize does not prove it is genuine. Attackers may impersonate clinic leaders, coworkers, vendors, or organizations the clinic uses. CISA’s phishing guidance recommends recognizing suspicious messages, reporting them, and avoiding links and attachments.

How should staff verify an unusual request?

Verify the request through a separate, trusted channel—not by replying to the email, calling a number in it, or following one of its links. For example, call the person using a number in the clinic directory or contact the vendor using a known, previously verified phone number or website.

Use this approach for unexpected requests involving payments, gift cards, password resets, multifactor authentication codes, changes to payment instructions, or protected health information. If the request cannot be independently confirmed, do not act on it; report it to IT or security.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Report what happened to IT or security immediately, even if nothing unusual appears on screen. Tell them whether you clicked a link, opened or downloaded a file, entered information, approved a multifactor authentication prompt, or noticed a warning or unexpected behavior. Do not try to investigate or remove suspected malware yourself.

If you entered a password or verification code, contact IT urgently and follow its instructions to secure the account. Do not reuse a possibly compromised password. The security team may need to reset credentials, revoke active sessions, review account activity, or check for suspicious mailbox settings.

If a file appears to have installed malware or the device behaves unexpectedly, stop using it for clinic work and contact IT. Follow its instructions about disconnecting the device from the network or other containment steps. CISA’s phishing incident response guidance describes containment and account-remediation actions for organizations responding to successful phishing activity.

What information should staff report to IT or security?

Share enough detail to help the security team find and assess the message. Report the time it arrived, the displayed sender and subject, what you did with it, and whether you entered credentials, shared information, approved a prompt, or saw unusual device or account activity.

Identify any clinic account or device involved and whether the email included or requested patient information. Do not send protected health information to an unapproved address as part of your report. Use the clinic’s approved reporting tool or contact channel, and preserve the original email if instructed so investigators can review its headers and links.

Staff should report suspected exposure rather than decide whether a legal breach occurred. The clinic’s privacy and security leaders must assess the facts, document the incident, and determine any required response. HHS’s overview of the HIPAA Security Rule describes the safeguards and security processes covered entities must maintain.

What safeguards help clinics prevent and respond to phishing incidents?

A healthcare phishing incident response plan should make it easy for staff to report suspicious messages and explain who receives reports, how urgent issues are escalated, what staff should preserve, and who coordinates technical and privacy reviews. Train staff on the clinic’s own policies and reporting routes, and reinforce that prompt reporting is more important than fear of blame.

Clinics can also reduce risk with layered safeguards, such as an email security gateway that filters malicious messages, multifactor authentication, restricted access to sensitive systems, endpoint protections, and timely software updates. Multifactor authentication can help protect accounts, but it does not make phishing harmless; staff should never approve an unexpected sign-in prompt or share a one-time code. CISA recommends layered anti-phishing protections, including email gateway capabilities, and discusses the limits of weaker forms of multifactor authentication in its phishing guidance for organizations.

Under the HIPAA Breach Notification Rule, a suspected phishing email is not automatically a reportable breach. If the clinic determines that unsecured protected health information was breached, notification duties may apply. HHS says affected individuals must generally be notified without unreasonable delay and no later than 60 days after discovery; reporting to the HHS Secretary follows different requirements depending on the number of people affected. These are organizational notification deadlines, not a reason for staff to wait before reporting a suspected incident internally. See HHS’s Breach Notification Rule guidance.

In short, do not interact with suspicious messages, verify unusual requests independently, and report suspected phishing promptly through clinic procedures. Clear policies, layered technical safeguards, and quick escalation help clinics investigate threats and protect patient information.

FAQs

Should clinic staff delete a suspected phishing email?

Report it first using the clinic’s approved reporting channel, then follow IT or security staff’s instructions. Do not delete it before reporting if that could prevent the team from reviewing the original message.

What should staff do if they entered their credentials?

Contact IT or security immediately and say which account and information you entered. Follow instructions to reset the password and secure the account; do not reuse a compromised password or approve unexpected multifactor authentication prompts.

Can a phishing email compromise patient information?

Yes. A phishing email could lead to unauthorized access to an account or device that contains protected health information. Whether patient information was accessed or a reportable breach occurred depends on the facts, so alert the clinic’s security and privacy teams promptly.

How quickly should a clinic report a suspected phishing incident?

Staff should report it as soon as possible using the clinic’s security incident reporting procedure. HIPAA requires covered entities to have procedures for responding to and documenting security incidents, but the federal breach-notification deadlines apply to organizational notifications after a breach is determined—not to a staff member’s initial internal report.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles