Read three fax vendor websites in a row and you will see the same phrases repeated: secure, HIPAA compliant, cloud-based, delivery confirmation, integrations, audit trail. On a feature comparison grid, the boxes all get checked. The grid hides the fact that each of those phrases can describe a capability that is solid or one that technically exists and does very little for your organization.
The differences matter most in regulated environments, where a feature that is present on paper but thin in practice shows up later as a compliance gap or a clinical delay. This post walks through the features that sound alike and offers the questions that separate them. It pairs well with the buyer’s guide to evaluating an enterprise fax platform and the questions every IT team should ask before switching fax vendors.
Encryption
Nearly every vendor says transmissions are encrypted. The useful question is which part of the path and to what standard.
- Is the transmission path encrypted, or only the connection to a web portal?
- Which TLS versions are supported, and are older versions disabled?
- What happens to content after delivery, and is deletion done to a recognized standard?
The post on encryption standards your fax platform should support covers what to ask for. Lane’s Fax 2.0 routes over the etherFAX network and destroys content after delivery, which is a different security posture from a service that stores every fax in a portal indefinitely.
HIPAA Compliant
This phrase is used loosely. No fax service is compliant on its own, because compliance depends on how the covered entity uses it. What a vendor can do is support compliance, and the clearest test is contractual.
- Will the vendor sign a Business Associate Agreement?
- Can they describe their technical safeguards in specifics rather than adjectives?
- Do they hold independent security certifications, and can you review them?
Consumer services frequently decline the first question, which settles the matter for any workflow involving PHI. The post on what makes a fax service truly HIPAA compliant goes deeper, and the FAQ Friday on BAAs explains how Lane handles them.
Cloud Fax
Cloud fax describes where the service runs, not how well it transmits. Some services adapt voice infrastructure for fax, which inherits the packet loss and timing problems that make fax over IP unreliable. Others use infrastructure built specifically for fax. Ask how transmissions are carried and how the service handles the protocol realities covered in the T.38 FAQ. The post on what makes Fax 2.0 different from traditional cloud fax lays out that distinction.
Delivery Confirmation
Confirmation can mean several different things:
- The document left your system
- The document reached the provider’s network
- The document was received at the destination fax number
Only the last one answers the question a sender actually has. Ask what event generates the confirmation, whether it is stored with a timestamp, and whether you can retrieve it months later. The post on delivery confirmation explains why this one feature carries so much weight.
Audit Trail
A log that shows a user’s last twenty faxes is not an audit trail. A compliance-grade record is persistent, searchable, centrally held, and retrievable for a defined retention period. Ask who can search it, how far back it goes, and whether it can be produced for a regulator or a legal request without manual reconstruction. The FAQ Friday on transmission record retention shows what that looks like in Passport.
Routing
Email forwarding of inbound faxes to a mailbox is sometimes described as routing. Real routing directs each inbound fax to the right team’s queue based on number and other rules, so nobody sorts a shared pile. The post on what good fax routing looks like shows the difference in practice.
Integrations
An integration can be a certified, maintained connection to your EHR or LIS, or it can be an email-to-fax workaround that technically moves a document. Ask whether the integration is listed or certified by the system vendor, how many customers run it, and how it is maintained through upgrades. Lane’s Epic integration and Clinisys integration are examples of the first kind.
Failure Handling
Every service retries a failed fax somehow. The difference is whether failures surface. Ask what happens when all retries are exhausted, who is alerted, and where an administrator sees it. The post on how Passport handles failures and retries covers this.
Using the List
A practical way to apply this is to turn each section into a question on your vendor questionnaire and ask for a demonstration instead of a yes or no. Vendors that run strong versions of these features tend to welcome the request.
Schedule a strategy call with the Lane team to walk through these questions against your own requirements.
