Key takeaways
- Fax is still how referrals, records requests and many payer forms move, even in fully electronic offices.
- Cloud e-fax replaces the paper tray with routed digital inboxes and an audit trail, but needs a BAA and access rules.
- Most fax risk comes from people, not lines: wrong numbers, unattended trays and shared logins.
- Port your numbers, run both systems in parallel for two weeks, and keep a written misdirected-fax playbook.
Why fax will not go away yet
Nearly every office-based physician now keeps records electronically: 91% used a certified EHR in 2024 and another 4% used a non-certified one[1]. Yet the fax line is still busy. Referrals from other practices, records requests from attorneys and patients, prior authorization forms, pharmacy refill requests, hospital discharge summaries and durable equipment orders often arrive by fax, because it is the one channel every office and agency can receive.
So the real choice is not fax or no fax. It is how you receive, route, store and send faxes: a machine on a phone line, a fax server in your office, or a cloud e-fax service that delivers faxes as digital documents. Each option changes who sees incoming documents, how quickly they reach the right person and how you prove what happened to them.
The three options side by side
| Factor | Fax machine | Fax server | Cloud e-fax |
|---|---|---|---|
| Where faxes land | Paper tray in the office | Shared folder or email on your network | Web inbox or EHR document queue |
| Who can see them | Anyone near the machine | Anyone with folder access | Users given access to that inbox |
| Routing | Someone walks it over | By number or rules, if set up | By number, department or rules |
| Audit trail | None for inbound paper | Server logs, varies | Logs of receipt, views and actions |
| Outbound errors | Typed numbers, easy to misdial | Typed or from address book | Saved contacts and send from EHR |
| During a power or internet outage | Works on an analog line with power | Stops if the server stops | Keeps receiving; you need web access to read |
| Vendor agreement | Phone carrier only | Software and support vendor | Business associate agreement required |
| Ongoing cost type | Line, paper, toner, maintenance | Server, licenses, IT time | Subscription and page volume |
Most small practices end up with cloud e-fax for daily work and keep one analog line or machine only if they have a specific backup need. Fax servers make sense mainly where an IT team already runs on-site systems.
Where fax risk really comes from
Fax gets a reputation as insecure, but the line itself is rarely the problem. The common incidents are human: a referral faxed to a wrong digit, a lab result left in a tray at the front desk, a shared login to an e-fax inbox used by staff who left months ago. Moving to e-fax removes the paper tray. It does not remove wrong numbers or weak access control.
Misdirected faxes can become reportable breaches. Breach notifications to affected individuals must be made without unreasonable delay and no later than 60 calendar days after discovery[2]. Breaches affecting fewer than 500 individuals must be logged and reported to HHS no later than 60 days after the end of each calendar year[3]. Your risk assessment for each incident, and your policies, are documentation you must keep: HIPAA requires covered entities to retain required policy and compliance documentation for six years[4].
Records requests still arrive by fax
Requests from patients, and from third parties acting on a patient's written direction, frequently come by fax. The clock starts when you receive the request, not when someone finds it. A covered entity must act on a patient's access request no later than 30 days after receipt, with one extension of no more than 30 days[5]. A request that sits in a paper tray over a long weekend has quietly used up part of that time.
Source: Legal Information Institute, Cornell Law School, current[5]
Show the data
| Item | Value |
|---|---|
| Standard limit after receipt | 30 days |
| Maximum with one extension | 60 days |
E-fax helps here because every inbound document has a receipt time stamp, and you can route a dedicated records-request number straight to the person who handles release of information.
What to require from a cloud e-fax vendor
A cloud fax service receives and stores protected health information for you, so it is a business associate. A covered entity may let a vendor handle that information only with satisfactory assurance, in a business associate agreement, that the vendor will safeguard it[6]. Do not port your numbers until the agreement is signed.
- Individual user logins with multifactor authentication; no shared inbox passwords.
- Separate inboxes or folders by department, each with its own access list.
- Logs that show when each fax arrived, who opened it, who forwarded or filed it and when.
- Encryption in transit and at rest, stated in the security documentation.
- A retention setting you control, plus the ability to delete after filing to the chart.
- Direct delivery into your EHR document queue, so staff index faxes without downloading them.
- Number porting support and a written timeline for moving existing fax numbers.
Designing the inbound workflow
The biggest gain from e-fax is routing. Instead of one tray that someone sorts, each fax number can deliver to a different queue. Many practices give referrals, records requests and pharmacy requests their own numbers, then publish the right number to the right senders.
Map senders to queues
List who faxes you and why: referring offices, hospitals, pharmacies, payers, attorneys, patients. Group them into three to five queues.
Assign owners
Each queue gets a named owner and a backup, with a time target for first review, such as within two business hours.
Index to the chart
The owner matches each fax to a patient, assigns a document type and files it, or flags it as unmatched.
Handle unmatched faxes
Keep a short daily list of faxes that could not be matched and call the sender the same day.
Delete from the inbox
Once filed in the EHR, remove the fax from the e-fax inbox according to your retention policy so copies do not pile up.
Sending faxes without wrong numbers
- Send from inside the EHR where possible, using the provider directory rather than typed numbers.
- Keep a verified contact list of frequent recipients and review it every quarter.
- Call to confirm a new number before the first fax that contains patient information.
- Use a cover sheet that states the fax is confidential and asks the recipient to call if received in error.
- Send the minimum necessary: the pages the recipient needs, not the whole chart.
Migration plan: machine to e-fax in four weeks
- Week 1: sign the BAA, list every fax number you own and who uses it, and request number porting.
- Week 2: build inboxes and access lists, connect the EHR document queue and train queue owners.
- Week 3: run in parallel. New numbers or ported numbers go live while the old machine stays on, and staff compare what arrives.
- Week 4: confirm porting is complete, update your website, referral forms and letterhead, then retire or repurpose the machine.
Example: a fictional six-provider OB-GYN practice moved three fax numbers to a cloud service. During the parallel week it found that a hospital still sent discharge summaries to an old number nobody remembered owning. It ported that number too, rather than lose those documents.
Misdirected fax playbook
- Stop: confirm what was sent, to which number, when, and which patients are involved.
- Contact the recipient, ask them to destroy or return the pages, and record their confirmation.
- Tell your privacy officer the same day.
- Complete and document a risk assessment to decide whether it is a reportable breach.
- If it is reportable, notify affected patients within the required time and add it to your breach log.
- Fix the cause: update the contact list, retrain, or switch the sender to EHR-based faxing.
Keep this playbook next to the fax workflow and practice it once a year. The most damaging incidents are the ones nobody reported because nobody knew what to do.
Measuring the change
Pick three numbers before you switch and check them a month after. First, time from receipt to filing: how long a referral or records request waits before it is in the chart. Second, unmatched faxes per week: documents nobody could tie to a patient. Third, incidents: wrong-number sends and documents found in the wrong place. A cloud service should shorten the first, make the second visible and reduce the third. If filing time does not improve, the queues probably lack clear owners rather than better software.
How to decide
Choose cloud e-fax if more than one person handles faxes, if you have more than one location, or if you want faxes filed in the EHR without printing and scanning. Keep a fax machine only for a specific reason, such as an analog line that keeps working during an internet outage, and lock its tray area. Choose a fax server only if you already have on-site IT staff who will maintain it. In every case, the decisions that matter most are who can see incoming documents and how quickly they reach the right person.
Frequently asked questions
Is e-fax HIPAA compliant?
A cloud fax service can be used in a HIPAA-compliant way if the vendor signs a business associate agreement and you set up individual logins, access controls, audit logs and a retention policy. The service alone does not make you compliant.
Can we keep our existing fax numbers?
Usually yes. Most cloud fax services can port existing numbers. Ask for a written timeline and run the old machine in parallel until porting is confirmed.
Is a misdirected fax always a breach?
Not always, but it must be assessed. Document a risk assessment for each incident. If it is a reportable breach, notify affected patients within the required time and log it for your annual report to HHS.
Should we keep a fax machine as a backup?
Only if you have a reason, such as an analog line that keeps working when your internet is down. If you keep one, restrict access to the tray and include it in your workflow.
References
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.404 - Notification to individuals (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.408 - Notification to the Secretary (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.524 - Access of individuals to protected health information (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑