healthcare Archives | HIPAA Compliant Email

August 7, 2026July 7, 2026

HIPAA Compliant Email in Gmail (What Actually Qualifies)

hipaa compliant email gmail guide featured image

[mh_key_takeaways]

Gmail dominates business email, and it dominates small healthcare practice email too. The question is where the line sits between everyday Gmail and HIPAA compliant email Gmail.

The short answer is that personal gmail.com accounts cannot be made compliant. Google Workspace on a paid plan can, with the right configuration and a signed business associate agreement. For senders who want a simpler path, a HIPAA-compliant email service layered over Gmail handles the encryption and the BAA in one step.

This guide walks through the license tiers, the covered services, the encryption options, and the practical setup steps for practices that want to keep Gmail as their day-to-day inbox while meeting the Security Rule.

Personal Gmail cannot carry PHI regardless of encryption

A personal gmail.com address is a consumer account. Google does not sign business associate agreements for consumer accounts, and HIPAA requires a BAA with every business associate that handles protected health information.

Encryption alone does not solve this. A sender who encrypts a message with a third-party tool but sends it from a gmail.com account is still transmitting PHI through a provider that has not agreed to safeguard it.

The Office for Civil Rights has fined practices for exactly this pattern. Small practitioners often assume that adding a padlock icon is enough. The Security Rule looks at both the transmission and the entity handling the transmission.

The compliant path is to move to Google Workspace on a paid plan with the practice’s own domain. That switches the account from a consumer service to a business service that Google will cover under a BAA.

Google Workspace signs a BAA for covered services

Google Workspace administrators can accept a BAA in the Admin console under Account, Legal and compliance. The acceptance is a two-click process for a super administrator.

The agreement covers a defined list of Google services, including Gmail, Calendar, Drive, Meet, Docs, Sheets, Chat, Vault, Keep, Sites, Forms, Slides, and Tasks. Not every Google product is covered.

Non-covered services include Google Groups, third-party marketplace apps, and any Google service the admin has not explicitly enabled for the covered set. Users who share a patient chart in Groups are outside the BAA.

The BAA takes effect at the moment of acceptance and applies to future activity. Past activity is not retroactively covered, so practices should sign the BAA before any staff account touches a patient message.

hipaa compliant email gmail in article illustration one

Encryption in Google Workspace uses TLS and server-side keys

Google Workspace encrypts stored messages at rest with keys Google manages. That protects the mailbox from physical disk theft or unauthorized access to Google infrastructure.

Transport uses TLS 1.2 or higher when the receiving server supports it. Google publishes real-time transparency numbers showing about 95 percent of Gmail traffic uses TLS in both directions.

The 5 percent gap is not random. It reflects small receiving servers, misconfigured domains, and systems that do not support current TLS versions. For a receiving practice on a legacy server, the message may still deliver over plain SMTP.

Enforcing TLS on outbound is a partial fix. Administrators can require TLS to specific recipient domains through the Admin console, but that only works if the receiving side supports it. Otherwise the message bounces.

Native S/MIME requires Enterprise Plus

Google Workspace supports hosted S/MIME on Enterprise Plus, Education Standard, and Education Plus. Business Starter, Standard, and Plus do not include native S/MIME.

Setup requires uploading an S/MIME certificate for each user through the Admin console and configuring the incoming and outgoing S/MIME settings. Certificates come from a certificate authority and typically renew annually.

To send an encrypted message to an external recipient, the sender needs the recipient’s public certificate. That is the friction point. Getting a public certificate from a patient is not a workflow that scales.

For that reason, most practices skip native S/MIME even on plans that support it, and they use a third-party gateway that handles the certificate problem through a portal instead.

[mh_example]

Virtru is a common third-party option for Gmail

Virtru offers a browser extension that adds an encryption toggle to the Gmail compose window. When the toggle is on, the message body and attachments are encrypted before they leave the browser.

External recipients receive a link, open the message in a Virtru portal, and authenticate with a Google or Microsoft account, or with a one-time passcode. The sender can revoke access or set an expiration.

Virtru signs a BAA with covered entities. Pricing is per-user per-month and scales with the size of the practice. Deployment requires the admin to allow the extension through the Chrome policy or install it manually per user.

The trade-off with any browser-based extension is that it depends on the user remembering to toggle the encryption on. A message sent without the toggle goes out in the clear.

hipaa compliant email gmail in article illustration two

Cisco Secure Email Encryption Service works for larger systems

Cisco Secure Email Encryption Service, previously Cisco Registered Envelope Service, is a portal-based product Cisco offers to enterprises. It integrates with the Cisco email security appliance and cloud email security offerings.

Recipients receive an encrypted envelope, click a link, and open the message in a Cisco-hosted portal after authenticating. The sender can require additional verification and can pull the message back after delivery.

Cisco will sign a BAA with covered entities. The service is more common in large hospital systems that already run Cisco email security infrastructure than in solo practices or small groups.

For a small practice on Google Workspace, Cisco is usually more infrastructure than the workflow needs. A smaller gateway or a browser extension delivers the same compliance result with less operational overhead. Practices comparing options often review the broader hipaa compliant email cisco landscape before choosing.

Hosted HIPAA email services layer over Gmail without a plan upgrade

A hosted HIPAA compliant email service handles the encryption, the portal, and the BAA on top of the existing Gmail account. The practice does not need to upgrade to Enterprise Plus or manage S/MIME certificates.

Providers in this category include Mailhippo, Paubox, LuxSci, and Hushmail. Each connects to a Gmail account through OAuth or SMTP relay and encrypts outbound messages before they leave the sender’s device or the relay.

The recipient experience varies. Some services deliver a portal link. Others encrypt via TLS enforcement and pass the message through with no visible portal for recipients whose provider supports it.

Mailhippo takes the middle path. Messages to compliant receiving servers deliver directly, and messages to non-compliant destinations fall back to a portal. That preserves the recipient’s inbox experience wherever the destination server can handle encrypted delivery.

[mh_protip]

Admin console settings that harden a Workspace tenant

Two-step verification should be enforced for every user on the tenant. Enforcement, not just enablement, is the setting that blocks a login without a second factor.

Legacy protocols like POP and IMAP should be disabled for accounts that do not need them. Every enabled legacy protocol is a potential authentication path that bypasses two-step verification.

Data Loss Prevention rules can inspect outbound mail for content patterns like Social Security numbers, credit card numbers, or clinical terms, and either block, warn, or redirect the message. DLP is included on Business Standard and higher.

The Google Workspace HIPAA compliance guide lists the specific settings Google recommends for covered entities. Working through the guide once and documenting the state of each setting is the closest thing to a self-audit for a small practice.

Common breach patterns in Gmail-based practices

Autocomplete misfires cause a large share of email breaches. A clinician types the first two letters of a patient’s name, Gmail suggests the wrong contact, and the message goes to the wrong person.

Forwarded threads are the second common pattern. A patient message gets forwarded to a colleague for consultation, then forwarded again to a family member, and the chain leaves the covered environment somewhere along the way.

Attachment mistakes come next. Staff attach the wrong PDF, or attach the correct PDF to the wrong thread. Google’s undo send window is 30 seconds at most and does not recover a message the recipient has already opened.

The HHS breach portal lists dozens of email incidents per year in the small provider category, and the pattern is consistent. Compliance-grade sending is a combination of platform, encryption, and process, and process is often the weakest link.

What to configure this week if you are on Gmail today

If the practice is on personal Gmail, the immediate step is to purchase a Google Workspace Business Standard plan or higher and migrate the account to the practice’s own domain. Business Basic does not include the security controls needed.

Sign the BAA in the Admin console, enforce two-step verification, disable legacy protocols, and confirm the covered services list matches what staff use for patient communication.

Install a third-party encryption extension or connect a hosted HIPAA email service. Test a message to a personal address on a provider that does not enforce TLS, and confirm the message arrives as a portal link rather than plaintext.

For practices that also need a compliant patient-facing website, forms, and marketing setup around the email service, working with an agency that focuses on HIPAA-compliant website design and the broader healthcare website conversion optimization workflow keeps the email, the intake, and the marketing on the same compliance footing.

Sign the Google Workspace BAA in the Admin console.
Enforce two-step verification for every user account.
Disable POP and IMAP unless a specific workflow requires them.
Install a hosted HIPAA email service or S/MIME certificates on Enterprise Plus.
Document the covered services list and confirm staff use only those services for PHI.

Setting up hipaa compliant email gmail is a paid Google Workspace plan, a signed BAA, an encryption path for external mail, and staff training. Miss any of those pieces and the account is not compliant no matter how the software looks from the outside.

[mh_faqs]

March 2, 2026July 7, 2026

HIPAA Compliance Email Requirements for 2026

hipaa compliance email guide featured image

[mh_key_takeaways]

HIPAA compliance email is a stack, not a product. The Security Rule requires encryption of PHI in transit and at rest, the Privacy Rule requires patient authorization for uses outside treatment, and the Breach Notification Rule requires reporting when either safeguard fails.

No single mail service delivers HIPAA compliance by itself. Compliance comes from combining a HIPAA-eligible plan, a signed BAA, a second layer of content encryption, retention that meets the six-year rule, and administrative controls on the sending mailbox. A dedicated HIPAA secure email service simplifies the stack for practices without in-house IT.

This guide walks through each layer of the HIPAA email posture, the rules that drive each layer, and the practical steps small and mid-size practices use to stay compliant without over-investing in enterprise tooling.

HIPAA compliance email rules that actually apply

The Security Rule requires encryption of electronic PHI in transit and at rest when the risk analysis determines encryption is a reasonable and appropriate safeguard. Practices treat encryption as effectively mandatory for email because every risk analysis reaches the same conclusion.

The Privacy Rule requires patient authorization for uses and disclosures of PHI outside treatment, payment, or operations. Email marketing to patients falls under the authorization requirement when the marketing content promotes third party products or services.

The Breach Notification Rule requires reporting any unauthorized PHI disclosure to affected patients within 60 days. Reports to HHS follow the same 60 day window for breaches affecting more than 500 people, and go into the annual summary for smaller breaches.

Reference the full text at HHS HIPAA Security Rule and HHS HIPAA Privacy Rule when building the practice policy document.

HIPAA compliance email encryption requirements

HIPAA email encryption at a minimum uses TLS 1.2 or higher between mail servers. Gmail and Outlook both encrypt in transit by default on paid plans.

TLS alone protects the message on the wire but not on the servers the sender does not control. Best practice adds a second layer through Purview Message Encryption, S/MIME, or a portal-based delivery service.

The second layer matters most for messages that cross organizational boundaries. Internal mail between two mailboxes on the same tenant stays encrypted at rest by the tenant storage layer. External mail to a patient personal Gmail account travels through servers with unknown security posture.

Practices sending real PHI need to confirm the exact SKU, add-on, or dedicated service that unlocks second-layer encryption. See HIPAA email encryption guidance for the specific configuration steps on each major platform.

hipaa compliance email in article illustration one

HIPAA compliance email BAA requirements

A business associate agreement binds the vendor to the same PHI safeguards the covered entity uses internally. HIPAA requires a signed BAA with any vendor that stores, processes, or transmits PHI on behalf of the covered entity.

Google, Microsoft, and Amazon publish standard BAAs that covered entities accept in their admin consoles. Smaller vendors like Mailhippo include the BAA in the base plan without a separate negotiation.

Practices sending PHI on Gmail free, Outlook.com, Yahoo, or any consumer mail service without a BAA carry breach exposure on every outbound message. The BAA does not exist for consumer services, so no path to compliance exists on those platforms.

Reference the sample BAA at HHS sample business associate agreement provisions before signing any vendor BAA. Confirm the vendor BAA includes breach notification, subcontractor terms, and permitted uses that match the practice needs.

HIPAA compliance email disclaimer language

A HIPAA email disclaimer sits at the bottom of every outbound message in a clinical inbox. The disclaimer alerts accidental recipients that the message may contain PHI and instructs them to delete the message and notify the sender.

Standard disclaimer language includes four elements. A statement that the message may contain PHI. A statement that unauthorized use or disclosure is prohibited. An instruction to notify the sender and delete the message. A reference to the practice privacy policy.

The disclaimer does not create HIPAA compliance. It supports an operational purpose by helping recover from accidental misaddressing. See HIPAA email disclaimer signature for approved sample language covered entities can adapt.

Add the disclaimer through the mail server transport rules rather than user signatures. Server-side disclaimers apply to every outbound message, including messages sent from mobile devices where users often forget to enable the signature.

[mh_example]

HIPAA compliance email retention rules

The Privacy Rule requires six years of documentation for the designated record set. Emails that document treatment decisions, billing arrangements, patient consent, or breach notifications count as part of the designated record set.

The six-year clock runs from creation or last effective date, whichever is later. A treatment plan documented in an email in 2020 that stays effective through 2024 needs retention through 2030.

State laws sometimes require longer retention. New York requires six years for adult records and six years past the age of majority for minor records. California requires seven years past the last date of service.

Most practices apply the strictest applicable rule to all clinical inboxes to simplify classification. Archiving vendors like Mimecast, Barracuda, and Global Relay automate the retention window and produce audit-ready exports on demand.

hipaa compliance email in article illustration two

HIPAA compliance email on Google Workspace

Google Workspace paid plans are HIPAA-eligible when the tenant has a signed BAA with Google. Business Starter at $6 per user per month is the entry price. Business Standard, Business Plus, and Enterprise plans add more storage, advanced admin controls, and Vault archiving.

Accept the BAA in the Workspace admin console under Account, Legal, then HIPAA Business Associate Agreement. The BAA covers Gmail, Drive, Calendar, Meet, and other core services.

Configure the required admin settings after accepting the BAA. Disable consumer third party apps in Marketplace. Enable two-step verification for every account. Configure Vault retention to meet the six-year rule. Enable client-side encryption on Business Plus or higher for the strongest content protection.

Practices sending PHI to patients outside the tenant often layer a portal-based encryption service on top of Workspace. The gateway triggers on subject line keywords or content patterns and routes sensitive messages through an encrypted path.

HIPAA compliance email marketing rules

HIPAA restricts marketing communications that use PHI. The Privacy Rule requires patient authorization for marketing content that promotes third party products, services, or events.

Refill reminders and appointment reminders do not require authorization when the message covers the practice own services. Newsletters that promote a specific pharmaceutical product require authorization because the practice would receive payment from the manufacturer.

Email marketing platforms like Mailchimp and Constant Contact do not sign BAAs on their standard plans. Practices sending patient communications through those platforms need to use a HIPAA-eligible marketing platform that signs a BAA. See email marketing hipaa compliance for the vendor comparison.

Segment patient lists carefully. Sending a newsletter about diabetes management to a diabetes-diagnosed list treats the diagnosis code as PHI. The list itself becomes PHI at that point. Store the list in a HIPAA-eligible platform and treat it under the same rules as the underlying record.

[mh_protip]

HIPAA compliance email signature and identity controls

Every clinical email needs a signature block that identifies the sender by name, title, practice, and contact information. Identity clarity supports the Privacy Rule requirement for accountable disclosure.

Signature management tools like Exclaimer and Rocketseed apply consistent signature blocks across every mailbox. See best email signature management tools for hipaa compliance healthcare pharma for the vendor comparison for regulated environments.

Enable two-factor authentication on every clinical mailbox. Password rotation on a 60 to 90 day cycle catches compromised credentials before an attacker can pivot into the patient record system. Log every mailbox login in the audit trail.

The HIPAA email signature pattern also documents the practice HIPAA officer and a contact channel for privacy questions. Patients who see the officer contact tend to escalate privacy concerns directly to the practice rather than filing complaints with HHS.

HIPAA compliance email risk analysis and workflow

The Security Rule requires a documented risk analysis. The analysis inventories every place PHI touches the practice, identifies threats and vulnerabilities, and documents the safeguards applied to each risk.

Email risks include misaddressing, phishing, credential theft, and vendor breaches. The risk analysis documents the encryption layer, BAA status, retention configuration, and access controls that address each risk.

Update the analysis when the practice adds a new vendor, migrates to a new tenant, or changes the encryption product. Auditors ask for the analysis and the update history during a HIPAA audit.

Common HIPAA email risk items:

Misaddressing to a wrong external recipient
Phishing that steals mailbox credentials
Attachments that exceed the mail server encryption boundary
Auto-forwarding rules that copy PHI to personal accounts
Retention shorter than six years on clinical inboxes
BAA gaps with newly added vendors

HIPAA compliance email for small and mid-size practices

Small practices without dedicated IT often skip the encryption stack entirely and send PHI through consumer mail. The pattern shows up in breach reports year after year.

The lowest-friction path for a five to twenty seat practice combines Google Workspace Business Starter with Mailhippo for outbound encryption. Workspace covers the internal mail with a BAA. Mailhippo handles external mail to patients and vendors without requiring the recipient to install any software.

Practices running a patient-facing web presence also need matching safeguards on the site. Intake forms, appointment booking, and patient portal login all touch PHI. Working with a partner that handles HIPAA compliant website design keeps the web and email stacks aligned. See also the security features for healthcare websites reference guide.

For further reading, review the HIPAA Journal guide to compliant email and the HHS FAQ on business associate agreements before finalizing the practice HIPAA email policy.

[mh_faqs]

February 23, 2026July 7, 2026

HIPAA Secure Email Explained (Requirements, Providers, Setup)

[mh_key_takeaways]

Every provider claiming to sell HIPAA secure email is technically selling a set of features and a legal agreement. HIPAA does not certify products.

The practice buys tools that let it meet the Security Rule, and the practice remains responsible for how those tools are used. A HIPAA-compliant email service like Mailhippo covers the encryption, the BAA, and the audit logging in one bundle so the practice does not have to assemble three separate products.

This guide walks through what actually makes an email service HIPAA secure, the provider options at each price tier, and the setup steps that separate a compliant workflow from a technically encrypted mess.

The Security Rule sets the requirements, not the vendor

The HIPAA Security Rule lists administrative, physical, and technical safeguards for electronic protected health information. Email falls under transmission security, access control, and audit control.

Encryption is an addressable specification, which means the covered entity has to implement it if it is reasonable and appropriate. In practice, HHS treats encryption as the default expectation for external PHI transmission.

No product carries a HIPAA certification. Any provider claiming to be HIPAA-certified is misrepresenting how the law works. Products can be HIPAA-ready or HIPAA-eligible, meaning they support the features a covered entity needs.

The covered entity is responsible for the workflow around the product. Buying compliant software and using it non-compliantly still produces a breach.

Three requirements separate secure email from ordinary email

Encryption is the first requirement. TLS 1.2 or higher for transit, AES-128 or AES-256 for content and storage. The exact ciphers and key lengths are documented in NIST Special Publication 800-52 Rev. 2 and NIST 800-111.

A signed business associate agreement is the second. The BAA makes the provider legally responsible as a business associate under HIPAA. Without it, sharing PHI with the provider is unauthorized regardless of the encryption.

Audit logging is the third. Administrators need to pull records showing who sent what, when, to whom, and whether the message was encrypted. Logs need to be retained for at least six years to match HIPAA’s records requirement.

Missing any of the three disqualifies the product. Practices that focus only on encryption discover during an incident that they cannot pull logs or that the provider never signed a BAA.

hipaa secure email in article illustration one

Big platform providers work if the plan tier is right

Google Workspace signs BAAs on all paid plans starting at Business Starter. The BAA covers Gmail, Calendar, Drive, Meet, and several other core services.

Microsoft 365 signs BAAs on business and enterprise plans. Business Basic and higher qualify. Outlook.com consumer accounts do not.

Both platforms encrypt messages at rest with provider-managed keys and use TLS 1.2 or higher for transit whenever the receiving server supports it. External delivery is the gap. Neither guarantees TLS on outbound if the receiver does not enforce it.

For full external encryption, Google Workspace practices need Enterprise Plus for native S/MIME or a third-party gateway. Microsoft 365 practices need Business Premium for the Purview Encrypt button or a similar gateway.

Dedicated healthcare email services simplify the setup

Dedicated HIPAA email services focus on the healthcare workflow specifically. Mailhippo, Paubox, LuxSci, Hushmail, TrueVault, and Enguard all fit this category.

The common pattern is a BAA in the base plan, encryption on every outbound message by default, and a simpler admin interface than the big platforms. Prices typically run $5 to $30 per user per month depending on the feature set.

Some services replace the mailbox entirely. Enguard, Hushmail, and Paubox on their hosted-mailbox tiers provide a full mail service including the mailbox, the encryption, and the compliance controls.

Others layer over existing Gmail or Outlook. Mailhippo and Paubox both offer gateway options that let the practice keep its current email address and inbox while the service handles the encryption and BAA.

[mh_example]

Enterprise appliances suit large hospital systems

Cisco Secure Email Encryption Service, Barracuda Email Protection, and Proofpoint Email Encryption serve large healthcare organizations. Each integrates with the organization’s broader security stack and its email security gateway.

These products cost more per user, require dedicated administration, and typically involve a services engagement to deploy. In return, they deliver deep integration with SIEM, DLP, and identity systems.

For a solo practice or small group, enterprise appliances are overkill. For a 500-provider hospital system with existing Cisco infrastructure, they are usually the right tier. Practices comparing options often review the enterprise secure email encryption service cisco tier alongside the smaller-practice choices.

All three enterprise vendors sign BAAs and support the technical safeguards HIPAA requires. The differentiators are scale, integration, and administrative model.

hipaa secure email in article illustration two

Free HIPAA secure email is not a real category

Every provider that signs a BAA charges for the service. The BAA carries legal liability, and the vendor prices that liability into the plan.

Free encrypted email tiers exist for personal use. ProtonMail, Tutanota, and CounterMail all offer free tiers. None of them sign a BAA at the free level.

The lowest-cost real HIPAA secure email starts around $5 per user per month. Google Workspace Business Starter, Microsoft 365 Business Basic, and small-practice-tier Mailhippo all fall in that range.

Practices that try to build a compliant workflow on free tools spend the savings on incident response the first time a message leaks. The math favors paying for a base plan.

The four-step setup workflow

Step one is signing the BAA. On Google Workspace, that lives in the Admin console under Account, Legal and compliance. On Microsoft 365, it is in the Service Trust Portal. Dedicated services usually include the BAA in the sign-up flow.

Step two is configuring encryption for outbound external mail. That is either native S/MIME, a portal-based product like Purview or Mailhippo, or a gateway that enforces encryption on all outbound.

Step three is access control. Enforce multi-factor authentication, disable legacy protocols like POP and IMAP unless required, and set role-based permissions so only staff who need PHI access have it.

Step four is documentation. A two-page policy covering the tool, the trigger, the recipient handling, and the annual review satisfies OCR expectations. The HHS Security Rule guidance and NIST SP 800-66 Rev. 2 outline the documentation elements.

[mh_protip]

What providers include and what they leave to the practice

Every provider handles the technical safeguards on their infrastructure. Encryption in transit and at rest, physical security of the data centers, redundancy, and platform-level access controls are the vendor’s job.

The practice handles the administrative safeguards. Staff training, policies and procedures, workforce clearance, sanctions for policy violations, and the risk analysis all sit with the covered entity.

The practice also handles the workforce-level access decisions. Who has an email account, what role they have, what content they are authorized to send, and how they authenticate.

A provider signing a BAA does not transfer the practice’s obligations. It shares the technical burden and it creates a legally responsible partner for the covered entity’s transmissions.

Common configuration mistakes that fail an audit

Forgetting to sign the BAA is the most common mistake. Practices that subscribe to Google Workspace or Microsoft 365 assume the BAA is automatic. It is not. A super administrator has to accept the BAA explicitly.

Leaving legacy protocols enabled is the second common mistake. POP and IMAP predate modern authentication and often bypass multi-factor requirements. Disable them for any account that does not need them.

Skipping audit log configuration is the third. Both Google and Microsoft log by default, but retention settings often need to be extended to meet HIPAA’s six-year record requirement.

Practices comparing options often check hipaa compliant secure email reviews and is email hipaa secure explainers before making the final call, because vendor marketing pages rarely surface these configuration details.

Choosing a provider based on the practice’s size and stack

A solo practitioner or small clinic usually gets the best fit from a dedicated healthcare service like Mailhippo. Setup takes an hour, the BAA is in the base plan, and the monthly cost is under $20.

A group practice already on Google Workspace or Microsoft 365 usually stays on the big platform and adds a gateway. Switching mail providers for a 30-person practice is a bigger project than adding an encryption layer.

A large hospital system with existing enterprise security infrastructure typically routes email through Cisco, Barracuda, or Proofpoint. The scale justifies the appliance cost and the administrative overhead.

Whichever provider fits, the practice’s marketing and patient acquisition side should match the security posture. Agencies specializing in healthcare marketing and healthcare website maintenance keep the intake forms, appointment reminders, and outbound clinical mail on a consistent compliance track.

Verify the BAA is signed and current for every service that touches PHI.
Confirm encryption for internal, external, transit, and at-rest paths.
Enforce multi-factor authentication and disable legacy protocols.
Enable and retain audit logs for at least six years.
Document the workflow, train annually, and review the setup once a year.

A HIPAA secure email service is a combination of encryption, a signed BAA, audit logging, and a documented workflow. Any product that delivers the four pieces qualifies. The differentiator between providers is how much of the setup the vendor handles and how much stays with the practice.

[mh_faqs]