Support Center | ☎︎ Call us: (845) 440-5000 | info@vjnetworks.com
Back to Blog

HIPAA-Compliant Email: How to Send Patient Records to Other Offices Securely

CybersecurityManaged IT
Last updated: November 11, 2026

HIPAA compliant email for sending patient records to another office is email protected in transit and backed by a documented decision. The Security Rule makes encryption addressable, which is not the same as optional.

Records leave a clinic all day. Every workday. A referral packet goes to a specialist. Lab results go to the next office. A billing file goes to a vendor. Each trip is a small decision about how it travels. Most get made by habit.

This piece covers those transfers, office to office and office to vendor, and nothing wider. We provide managed IT for small practices across Rockland, Westchester and Bergen counties, and our page on IT support for healthcare practices shows the rest of that work.

Two clinic staff at a reception counter looking at a closed patient folder
Most transfers between offices are decided at the front desk.

HIPAA Compliant Email Between Offices: What HHS Actually Says

HIPAA compliant email, for a transfer between two offices, is not a product you buy. It’s a way of sending. The message is protected while it travels, and your practice has weighed the risk and written the decision down. HHS’s FAQ and the regulation describe both pieces, and the duty to assess and document sits with the practice, not the vendor.

The Office for Civil Rights answered the email question years ago. Its Security Rule FAQ says the rule “does not expressly prohibit the use of email for sending e-PHI.” It then says a covered entity “must assess its use of open networks, identify the available and appropriate means to protect e-PHI as it is transmitted, select a solution, and document the decision.” HHS last reviewed that FAQ in July 2013.

The regulation itself sits in 45 CFR 164.312(e), the transmission security standard. Encryption appears there as an addressable specification: “Implement a mechanism to encrypt electronic protected health information whenever deemed appropriate.” Addressable does not mean optional. Under 45 CFR 164.306(d)(3) you assess whether it is reasonable and appropriate for your practice, then implement it, or document why not and implement an equivalent alternative where one is reasonable.

Sending is allowed in the first place because of the Privacy Rule. HHS’s treatment communications FAQ says covered providers may share protected health information for treatment “without patient authorization, as long as they use reasonable safeguards when doing so,” and that these communications “may occur orally or in writing, by phone, fax, e-mail, or otherwise.” Its examples include one physician consulting another by email about a patient’s condition.

Email is allowed. The question is how. That’s the whole job.

One more thing before the comparison. HHS published a proposed rewrite of the Security Rule in the Federal Register on January 6, 2025 (90 FR 898). We looked for a final version on November 10, 2026 and found only the proposal, so everything above describes the rule as it stands today. This is general information, not legal advice, and your own counsel or compliance advisor decides what your practice must do.

Fax, Encrypted Email and Secure Connections Compared

Five ways records move between offices, and what the sources say about each.

ChannelWhat the sources sayWhere it fits, and what to watch (our view)
FaxHHS says a physician’s office may fax patient information to another physician’s office for treatment, with safeguards such as confirming the number.Referral packets and results to a known office. Watch for a number that changed and a machine in a public hallway.
Standard emailNot prohibited. You assess the risk of open networks, pick a protection and document the decision.Messages that carry no patient record. Watch for records in the body or an attachment with no protection in transit.
Encrypted emailEncryption is the addressable specification in 164.312(e). HHS’s breach-notification guidance lists TLS that follows NIST SP 800-52 as valid for data in motion.Records to offices and vendors who can receive it. Watch for a recipient whose system can’t accept it.
Encrypted connection to a vendorThat same HHS list also names IPsec VPNs (NIST SP 800-77) and SSL VPNs (NIST SP 800-113).Steady traffic between the same two organizations. Someone has to build and maintain both ends.
Direct Secure MessagingONC calls it a standards-based method to send health information between partners that resembles secure email.Exchange with hospitals and practices that already use it. Both sides need a Direct address.

Fax gets a bad name it doesn’t deserve. HHS’s fax FAQ, created in 2002 and last reviewed in January 2023, lists two reasonable safeguards: the sender confirming the number is the right one for the other physician’s office, and putting the fax machine in a secure location. Ask how yours actually travels before you rely on it.

According to an ONC blog post from July 2025, ONC helped launch the Direct Project in 2010, and DirectTrust, a non-profit standards organization, now supports over 2.7 million Direct addresses. Real option. We haven’t built our advice around it.

Fax machine on a shelf in a quiet clinic back room, out of public view
HHS's fax FAQ lists a secure location for the machine as a reasonable safeguard.

What We Tell Clients, and the Encrypted Connections We Build

Mike Stoveken at VJNetworks puts our practice this way:

“We tell everybody, when the transmission of PHI comes up, you have to use encrypted email, and we build encrypted transports between our customers and the IT departments of their vendors and companies that they deal with.”

That’s advice we give clients, and it runs stricter than the regulation’s wording. The Security Rule says to encrypt whenever deemed appropriate, and to assess and document that decision. We tell clients to treat the question as settled. Encrypt.

What is an encrypted transport? Plain version: an arrangement between two organizations’ systems so that traffic between them only travels over an encrypted connection. One common form is a Microsoft 365 connector set to always use TLS when it sends to a partner’s domain. Another is a VPN tunnel to a vendor. Either can work. Which one fits depends on what the vendor’s side supports.

HHS’s guidance on making protected health information unusable to unauthorized people was written for breach notification, so treat it as a benchmark, not a Security Rule checklist. It points to processes that comply, as appropriate, with NIST Special Publication 800-52 (TLS), 800-77 (IPsec VPNs) or 800-113 (SSL VPNs), and it treats PHI as unusable when it’s encrypted that way and the key hasn’t been breached. You can read the full list in the HHS breach guidance.

Open wall-mounted network cabinet with a network switch and a tidy cable bundle in an office closet
An encrypted connection to a vendor is built and maintained on both ends.

We’ve supported offices across Rockland, Westchester and Bergen since 2004 through our managed IT services. Nothing here replaces your compliance advisor. For the Microsoft 365 side of the same question, see how Microsoft 365 encrypts email. For the wider picture, what HIPAA requires of your IT provider covers it.

Where Records Go Wrong in Transit

The failures are mundane. Picture a front desk sending a referral on a busy morning. The specialist’s fax number changed when the practice moved and the old one still sits in the machine, or the email program offers an address for a similar name and Enter does the rest, or a billing file heads to a vendor over a connection nobody has looked at in three years.

No hacker required.

Mike has seen the pattern from the inside of small offices. “The smaller you are, the less oversight you have and the more corners you cut,” he says. He means passwords on sticky notes and printed pages left on desks, and it’s what he has seen, not audit data.

HHS’s fax examples are plain for the same reason. Confirm the number. Put the machine in a secure location. That’s it. For email, HHS asks you to document the decision.

Questions to Settle Before the First Record Goes Out

Five questions. Answer them once, in writing, and the rest gets easier.

  • Who is on the other end? A named person at a known office, or a shared inbox that six people read?
  • Can the receiving side accept encryption? If not, a message that can’t go securely shouldn’t go another way just because it’s quicker.
  • One transfer, or a standing flow? A lab or vendor you send to every week deserves a built connection, not a habit.
  • A vendor that handles patient information on your behalf may be a business associate, which brings a written agreement. Has your compliance advisor confirmed the status?
  • Where is the decision documented?

Things Practices Ask Before Sending Records

Is it actually legal to email a patient record to another doctor’s office?
For treatment, HHS says providers may share protected health information without patient authorization, by phone, fax, e-mail or otherwise, with reasonable safeguards. The Security Rule then asks you to protect the message in transit. We’d encrypt.
Does HIPAA force you to encrypt email?
Not in so many words. The Security Rule lists encryption as addressable, with the wording “whenever deemed appropriate,” so you assess, decide and document. That is a duty to think it through, and skipping the step is not an option. Our own advice to clients is to encrypt.
Fax or email, which is safer for a referral packet?
HHS accepts both for treatment with safeguards, so neither is banned. A fax to a confirmed number on a machine kept out of public view is HHS’s own example. Encrypted email is the one we advise. Whichever you pick, it has to be a channel the other office can receive securely.
Our email provider says it’s HIPAA compliant. Are we done?
Not by itself. HHS’s email FAQ puts the duty on the covered entity: assess the use of open networks, select a solution and document the decision. A provider’s badge doesn’t do that for you. Ask whether the provider will sign a business associate agreement, and have your compliance advisor read it.
What does a secure connection to a vendor look like?
A TLS-enforced mail route or a VPN tunnel are the usual forms, and either one aims to keep traffic between your systems and the vendor’s encrypted while it crosses the internet. It protects the message in transit only, not once it sits in a mailbox. HHS’s breach guidance names NIST SP 800-52 (TLS), 800-77 (IPsec VPNs) and 800-113 (SSL VPNs) for data in motion.
Will the proposed Security Rule rewrite change any of this?
A proposal isn’t a rule. HHS published one on January 6, 2025, and we found no final version in the Federal Register on November 10, 2026. Today’s wording applies.
How do your patient records travel today?

Talk with our team about how your practice sends records to other offices and vendors. No cost, no obligation.

Get Your Free IT Assessment →

Or call (845) 440-5000