be Smart.
be Secure.
Phone: 800-441-6612

Is a FAX document HIPAA-Secure?

Many organizations, especially in the healthcare industry, have an urgent need to send important and sensitive information, like protected health information (what constitutes PHI?), to organizations via FAX (facsimile).

Why?  Because this is how it has always been done, and everyone is “set up” to be able to handle FAXes quickly and efficiently.

However, with HIPAA security regulations ever-present, our clients are concerned that their use of FAX is compliant, similar to making sure that their email and web sites meet HIPAA security standards.

Update – for electronic FAXing options, see: HIPAA Faxing: How to Send and Receive FAXes in a Secure and Compliant Way.

Beyond compliance issues, a FAX is not really useful — you essentially get a printout or an image and not an electronic document that can be efficiently used.  This is not good for productivity or for meeting other standards.

Can data sent via FAX be “secure enough” for HIPAA?

You might think that the answer is simple “no”, unless the FAX is sent over some type of secured phone line.  Why?  Because anyone with physical access to the phone lines and some technical expertise can eavesdrop on phone calls and FAXes and thus obtain any protected health information by fax.  It is acknowledged that sending email messages containing PHI insecurely is prohibited, so it follows that FAXing might also be “not a good idea”.

But, it turns out that “no” is too simple an answer and not practical or accurate.

How does HIPAA actually apply to FAXes?

The area of HIPAA that applies to FAXes is the “SafeGuards Principle“.

SAFEGUARDS PRINCIPLE: Individually identifiable health information should be protected with reasonable administrative, technical, and physical safeguards to ensure its confidentiality, integrity, and availability and to prevent unauthorized or inappropriate access, use, or disclosure.

HIPAA is interesting in that it lays out many requirements, rules, and principles, but they are all flexible and do not prescribe any specific practices or actions that must be taken.  This permits organizations to “adequately” protect the privacy of PHI as appropriate to their circumstances.

With email, there are many physical, technical, and administrative safeguards that are easy to apply.  Using end-to-end email encryption and good security policies is not difficult and is considered “low hanging fruit” on the path to meeting all of the HIPAA requirements.  Since securing email is relatively easy, it becomes essentially mandatory under the Safeguards Principle — it is reasonable to take the straight-forward step of using email encryption to protect personal health information (PHI), especially with the significant insecurities of Internet use in general.

With FAXes, the situation is very different.

  • There is no easy way to secure a “regular” FAX transmission between between two parties unless they are both setup with special encrypting fax machines or other special services. Few organizations have such tools. They are expensive, and to be useful, everyone must have compatible machines.
  • Everyone already uses insecure FAX machines that talk over regular phone lines
  • People are familiar with communication of protected health information (PHI) on an as needed basis verbally over the [insecure] phone.
  • Use of these same [insecure] phone lines to send a FAX is not much less secure than talking over the line.
  • Most organizations have a strong business need to communicate using FAX.

Since speaking over insecure phone lines, when needed,  is “OK” as far as HIPAA goes, how can a FAX be less secure?

  • FAXes are often left on the FAX machine for some period of time after they arrive.  This makes the sensitive information available to anyone walking by the machine.
  • FAX machines often save copies of received FAXes internally.  This makes it possible for anyone with access to the FAX machine to print out additional copies of the sensitive material.
  • FAX machines generally print out the transmitted messages on paper.  This paper, if not destroyed, could be placed in an insecure location.
  • If the fax machine actually transmits the fax digitally anywhere (e.g. fax-to-email), then that digital transmission must be properly encrypted for HIPAA.  Most fax machines do not support that; and most small offices do not bother to set this up securely even if it is possible for them.

What should you do to be HIPAA compliant?

Option #1: Don’t send any FAXes

This is probably not realistic for most organizations; however, it will guarantee that you are HIPAA compliant.  It is, increasingly, the way to go these days — with it being easier and easier to send information over secure email or through other secure electronic means. Eliminating the paper trail and the insecure FAXes can be an important step in cleaning up your HIPAA risk analysis.

Option #2: Use sensible policies

If you decide its worth the risk to send FAXes over insecure phone lines, you should utilize sensible policies to mitigate the insecurities of the facsimile and help ensure that you are abiding by the Safeguards Principle in a reasonable manner.  Some suggested policies include:

  • Do not send PHI over FAX unless it cannot be sent over other, more secure, channels.  I.e. delivery by hand, secure email, etc.
  • Only send the PHI actually needed; do not send additional information.
  • Always use a cover letter to prevent casual reading of the first page of the FAX.
  • Use saved speed-dial numbers for common FAX recipients to prevent numbers being mis-dialed.  Test these numbers periodically.
  • For any new recipient, verify the FAX number with a test send of a facsimile before sending the actual protected health information.
  • Develop policies on what to do if a FAX was sent to the wrong place.  This would be a HIPAA breach.
  • Configure your FAX machines to never save copies of sent or received FAXes
  • Make sure that PHI FAXes never remain on the FAX machine after receipt, and that they are promptly delivered to the intended recipient.
  • Develop policies on the storage, copying, and disposal of PHI FAXes.
  • Locate your FAX machines in a secured room where only staff who are authorized to use ePHI that may be transmitted trough that machine can use access it.
  • Use a dedicated FAX machine for ePHI and keep it well separate and secured, compared to any other FAX machines in use.

Development of policies along these lines will help to mitigate security issues associated with FAXing.  These guidelines are common in institutions having to abide by HIPAA … especially if they are not aware of better solutions.

Option #3: Send the FAX data via “Email”

If you search the internet for “Secure FAX” services, you will find many companies that advertise securing FAXing.  Some of these vendors never actually describe security at all — they just get your attention with the “Secure” keyword.  Some of them offer FAX services and instruct you to follow the steps described in Option #2 to make FAXes “secure”.  The few that actually offer a truly secure FAX service do something like this:

  • You access their web site using a secure (SSL) connection.
  • You login and upload the materials to be “FAXed” (i.e. possibly after first scanning and saving it on your computer).
  • You enter an email address and possibly a FAX number of the recipient.
  • The pages that you are “FAXing” are encrypted and saved in a database at your FAX service provider.
  • The “FAX” recipient gets an email or FAX notifying them that they have a “FAX” and that they need to go to a web site to “pick it up”.
  • The recipient goes to the web site and downloads the “FAX” over a secure (SSL) web connection.

This transmission of information is secure end-to-end because:

  • The transmission from the sender to the server is secured.
  • The temporary storage is secured.
  • The transmission from the server to the recipient is secured.
  • An audit trail may be available to track the process, for improved compliance.
  • Authentication of the sender and/or recipient may be present, for improved compliance.

This is obviously a more secure method of transmitting PHI than a classical FAX.  However, the use of “FAX” in this process is really a misnomer.  Except for some services which “FAX” the recipient a notice instead of an email notification, no actual FAXing is involved. Secure FAX services offer nothing more than a “drop off and pick up” process.  However, for most purposes, that is the solution …. not the FAXing in and of itself.

LuxSci offers just this kind of drop off and pick up service as part of its SecureLine email encryption service — you can securely and compliantly transfer files to any organization using any email address.  It’s easy to send and easy to pickup PHI and SecureLine is HIPAA-secure.  It is not a “FAX” per-se, but it delivers the same result.

What is the right choice for you?

As with everything HIPAA — the choice is yours to:

  1. Abandon FAXes if you don’t need them frequently.
  2. Use FAXes with good policies if you have the demand, your staff can’t easily make electronic copies of the data, and/or if your recipients do not have email access.
  3. Use something like LuxSci’s SecureLine Escrow service if:
    1. you have introduced end-to-end email encryption for sending private information over the Internet, or
    2. most of your PHI data is already digital or can be easily scanned, or
    3. most of your recipients use email and would prefer this data in a more useful format than a FAX, or
    4. the risk of breach due to continued insecure FAX usage is too great for your company’s HIPAA compliance requirements

3 Responses to “Is a FAX document HIPAA-Secure?”

  1. HIPAA 2010 and Beyond: Impact on Email and Web Outsourcing | LuxSci FYI Says:

    […] Is a FAX document HIPAA-Secure? […]

  2. Faxing to Golden Rule Says:

    […] Here are a couple of places that offer HIPAA secure faxing so there must be something to it. Is a FAX document HIPAA-Secure? | LuxSci FYI SafetySend Secure Email, HIPAA-GLB […]

  3. HIPAA Faxing: How To Send and Receive FAXes in a Secure and Compliant Way | LuxSci FYI Says:

    […] We have previously discussed how it may be OK according to HIPAA to send and receive FAXes with ePHI over standard analog phone lines.  See: Is a FAX document HIPAA-Secure? […]

Leave a Comment

You must be logged in to post a comment.

• Access Anywhere
• Fast and Robust
• Super Secure
• Tons of Features
• Customizable
• Mobile Friendly

Send and receive email from your favorite programs, including:

 Microsoft Outlook
 Mozilla Thunderbird
 Apple Mail
 Windows Mail

... Virtually any program that supports POP, IMAP, or SMTP

Keep your email, contacts, and calendars in sync:

 Apple iPhone and iPad
 Android Devices
 Windows Phone

... Any device with Exchange ActiveSync (EAS) support

Relay your server's mail through LuxSci via smarthost:

• Resolve issues with ISP sending limits and restrictions
• Improve deliverability with better IP reputation and IP masking
• Take advantage of Email Archival and HIPAA Compliance
• Even setup smarthosting from Google Apps!

Free web site hosting with any email account:

• Start with up to 10 web sites and MySQL databases
• DNS services for one domain included
• Tons of features and fully HIPAA capable

LuxSci's focus on security and privacy:

• Read The Case for Email Security
• Read Mitigating Security & Privacy Threats
• Review our Privacy Policy

The most accurate, flexible, and trusted filters in the business:

• Premium protection with Intel Security Saas
• Realtime virus database guards against the latest threats
• Seven-day quarantine lets you put eyes on every filtered email
• Supplement with our Basic Spam Filter for even more features

End-to-end secure email encryption — to anyone, from anyone:

• No setup required — encryption is automatic and easy to use
• Secure outbound email with TLS, PGP, S/MIME, or Escrow
• Free inbound encryption via our SecureSend portal
• Independent of your recipient's level of email security
• Widely compatible and fully HIPAA Compliant

Add an extra layer of security with an SSL Certificate:

• Secure your web site
• Debrand LuxSci WebMail with your own secure domain
• Access secure email services via your own secure domain

Encrypt your service traffic via secure tunnel:

• Add another layer of security to your SSL connections
• WebMail, POP, IMAP, SMTP, web/database access
• SecureForm posts, SecureLine Escrow, SecureSend access
• Restrict your account to VPN access only

Secure long-term message archival:

• Immutable, tamperproof email retention with audit trails
• No system requirements — minimal setup, even less upkeep
• Realtime archival of all inbound and outbound messages
• Works anywhere — even with non-LuxSci email hosting

Free data backups included with all email hosting accounts:

• Automatic backups of all email, WebAides, web/database data
• Seven daily backups and up to four weekly backups
• Unlimited restores included at no additional cost
• Custom backup schedules for dedicated servers

Automate your email management:

• Save messages to specific folders or to LuxSci WebAides
• Advanced text scanning with regular expressions
• Tag messages, alter subject lines, or add custom headers
• Filter by message charset, type, TLS status, DKIM status
• Chain filters together for even more complex actions

• Bulk add and edit users, aliases and more
• Control sharing and access globally or on a granular level
• Delegate user roles through permissions
• Configure account-wide taglines, sending restrictions, and more
• Remotely administer account via SOAP API

Share, collaborate, organize, synchronize:

• Calendars, Contacts, Documents, Notes, Widgets, Workspaces
• Fine-grained access control and security
• Access anywhere via secure web portal or smartphone
• Save over solutions like Microsoft Exchange

Free folder sharing for all email hosting accounts:

• Share mail folders with other users in your account
• Subscribe to only the folders you want to see
• Set read-only or read-write access control
• View all personal and shared folders via unified web interface

Color code and label your email messages:

• Define and assign multiple IMAP keywords to each message
• Filter, search, and sort by tags
• Compatible and synchronizes with any IMAP email client
• Also usable with WebAide entries