Will Geek for You
← All articles

HIPAA-Compliant Email: A Plain-English Checklist for Small Medical Practices

HIPAA-Compliant Email: A Plain-English Checklist for Small Medical Practices

A medical practice staff member reviewing email at a bright, tidy front desk

HIPAA-compliant email is not just a matter of turning on encryption. A practice needs an email provider that will sign a Business Associate Agreement (BAA) for the service it uses, reasonable safeguards for messages containing health information, and clear rules for staff access and patient communication. Regular email is not automatically secure, but HIPAA does not ban email.

The short version: Choose a business email service that will sign a BAA, use appropriate encryption, give staff individual accounts, and set a simple policy for what belongs in email versus a patient portal.

What does HIPAA-compliant email actually mean?

HIPAA requires practices to protect electronic protected health information (ePHI), including when it is sent or stored in email. The Security Rule does not prescribe one email product or one universal setup; your practice needs safeguards that fit the risks and should document its decisions.

Encryption helps protect messages as they travel between systems. But it is only one part of the picture: a signed BAA, access controls, staff training, written procedures, and a way to respond to a lost device or other incident matter too. The HHS guidance on email and patient communication explains that providers may use email with patients if they apply reasonable safeguards.

A BAA is a written agreement that sets out how a service provider may handle protected health information for your practice. If an email provider stores or handles patient messages for you, ask whether the specific business service and plan you intend to use are covered by a BAA, and get the agreement signed before using that service for ePHI.

Some providers offer BAAs for certain business services; others will not sign one for a personal or free account. A BAA does not make your practice compliant by itself, and a provider’s general claim of being “HIPAA ready” is not a substitute for checking the agreement, service scope, and your own setup. HHS explains when a cloud provider is a business associate.

Where can email go wrong in a 10-person practice?

The risks often come from ordinary routines, not sophisticated attacks. For example, a patient may reply to an appointment reminder with symptoms or medication details, even though the original message asked only to confirm a time.

A staff member might forward a message to personal Gmail to finish work at home. Several front-desk employees may use one shared password, making it hard to know who read or sent a message. A referral with records may go to the wrong specialist address, or a lost phone may still have the practice inbox open.

These examples do not mean your staff must stop communicating by email. They mean you need clear habits and safeguards that make the safer choice easy.

Illustration of clinic staff handling a shared inbox and a secured phone

HIPAA-compliant email checklist for a small practice

Use this HIPAA-compliant email checklist as a starting point. Assign someone to confirm each item and keep records of your decisions.

1. Provider and BAA

  • Confirm the service and plan. Ask the provider whether it will sign a BAA covering the email service and features you plan to use.
  • Get the agreement signed and saved. Do not rely on a sales conversation or an unsigned template.
  • Check connected services. Email archiving, backup, or other tools that handle ePHI may need their own review and agreements.
  • Keep personal accounts out of the workflow. Staff should not forward patient messages to personal accounts unless that service and use have been properly approved and covered.

2. Encryption

  • Ask how messages are protected in transit. Confirm that encryption is enabled for email sent between your practice and other email systems, and find out what happens if the recipient’s system cannot negotiate an encrypted connection.
  • Use a secure message or portal for sensitive details. A secure portal can be a better route for records, test results, or extended clinical discussions.
  • Keep subject lines generic. A subject line such as “Appointment follow-up” reveals less than a diagnosis or test result, even when the message body is protected.
  • Document your approach. HIPAA’s Security Rule treats encryption as an addressable specification: your practice should assess the risks, choose reasonable protections, and document its decision. See HHS’s Security Rule overview.

3. Policy and training

  • Write a short email policy. Explain what staff may send, when to use a portal, how to verify recipients, and what not to forward.
  • Train staff with real examples. Cover patient replies with medical details, sending records to a specialist, and what to do when a message goes to the wrong address.
  • Set an incident process. Tell staff who to contact if a phone is lost, an account may be compromised, or information is sent to the wrong person.
  • Include email in your security risk review. Revisit the setup when you add a service, change workflows, or discover a weakness.

4. Access and devices

  • Give every staff member an individual login. A shared front-desk address can be useful, but staff should access it through their own accounts when the system allows it. This makes it easier to remove one person’s access without disrupting everyone.
  • Turn on multi-factor authentication (MFA). MFA asks for an additional proof of identity, such as an app prompt, beyond a password.
  • Limit access to job needs. A staff member who does not need clinical email should not have broad access to it.
  • Protect phones and computers. Use screen locks, device encryption where supported, and a way to remove practice data from a lost device. Remove access promptly when a staff member leaves.

5. Patient communication rules

  • Verify the address before sending. A typo can send information to the wrong person.
  • Offer a secure option for clinical details. Tell patients how to use your portal or secure-message process for symptoms, records, and other sensitive information.
  • Record communication preferences. Note when a patient asks for a different way to be contacted.
  • Keep the message limited. Send only the information needed for the purpose, and avoid unnecessary details.

Simple illustration of a five-part email safety checklist for a clinic

What if a patient emails symptoms or other health details?

You cannot control what a patient chooses to send. You can control how your practice responds, what staff are trained to do, and whether your intake process points patients toward a more suitable channel.

If a patient initiates email, HHS says a provider may generally assume email is acceptable unless the patient says otherwise. Still, explain that ordinary email may not be secure and offer a portal, phone, or another option. For detailed clinical information, a patient portal or secure message is usually a better path than a long email thread.

If someone replies to an appointment reminder with symptoms, staff should follow your written process rather than improvise. For example, acknowledge the message without repeating unnecessary health details, direct the patient to the portal or phone line, and route any urgent concern according to your clinical procedures.

Clinic staff member speaking with a patient by phone while a secure portal is open on a laptop

How much does HIPAA-compliant email cost?

For a small practice, email software is often a modest per-user monthly expense. The total depends on the provider, plan, security features, and how many staff need access; ask for the BAA and confirm whether it covers the features you actually need.

The larger effort is often setup and policy work: reviewing how messages flow, configuring accounts and devices, writing procedures, and training staff. You may be able to keep that manageable by starting with a focused review and fixing the biggest gaps first rather than buying a large system you do not need.

How to send HIPAA-compliant email: start this week

  1. List your email accounts and users. Include shared inboxes, phones, and any personal accounts staff use for practice work.
  2. Ask your provider about its BAA and safeguards. Confirm the agreement covers your service and check how encryption, MFA, and access controls are handled.
  3. Set one clear patient-message rule. Tell staff what to do when patients email clinical details, and show patients how to use your portal or secure contact option.

We’re not lawyers, and this checklist is practical guidance, not legal advice. For a practice-specific review, we at Will Geek for You can offer a free 15-minute look at your email setup and help identify sensible next steps.

Frequently asked questions

Is Gmail HIPAA compliant?

A product name alone does not answer that. Check whether the specific business service and plan will be covered by a signed BAA and whether your practice has configured and uses it with appropriate safeguards; do not assume a personal account is suitable for patient information.

Can I email patients about appointments?

Yes, HIPAA does not ban email communication with patients. Verify the address, keep the message limited, and respect a patient’s communication preferences.

Do I need a BAA with my email provider?

If the provider creates, receives, maintains, or transmits ePHI for your practice, you generally need a signed BAA covering that service. Ask the provider directly and keep the signed agreement on file.

Does a BAA make my email HIPAA compliant?

No. It is an important part of the setup, but your practice also needs appropriate security settings, access controls, staff policies and training, and a documented approach to protecting patient information.