Chloe Williams

T.38 is a telecommunications protocol developed specifically to handle fax signals over internet-based connections. If you have encountered reliability problems with fax over VoIP, or if you are evaluating enterprise fax solutions and want to understand why some platforms perform more reliably than others, T.38 is worth understanding. The Problem T.38 Was Designed to Solve

Most organizations have business continuity plans that cover their EHR, their network infrastructure, and their core clinical and operational systems. Fax infrastructure is less consistently included, partly because it is often managed as a utility rather than a critical system and partly because its failure modes are less dramatic than an EHR outage: fax failures

There is a significant gap between enterprise fax as most organizations are running it and enterprise fax as it should be run. Most organizations running fax poorly are not doing so because they have made a deliberate choice to underinvest in it. They are doing so because fax infrastructure was set up years ago, it

Fax infrastructure costs in most organizations are distributed across budget lines in ways that make the total difficult to see clearly. The PSTN line charges appear on the telecom invoice. The server hardware maintenance appears in IT capital or operating expense. The software license appears in the application portfolio. The IT staff time appears nowhere

Every few years, organizations revisit their communication stack and ask whether fax still belongs in it. The question is reasonable. The cost of maintaining fax infrastructure is visible. The alternatives, EHR messaging, secure email, Direct Trust, FHIR-based APIs, are getting more capable. And fax carries a reputation as a legacy technology that sophisticated organizations are

Yes, and it is one of the areas where Lane’s four-decade track record gives organizations a meaningful advantage over newer fax providers. Lane supports fax transmission across more than 50 countries, with implementations ranging from large financial institutions to healthcare networks operating across multiple international markets. International faxing through Passport works through the same platform

When a fax does not reach its intended recipient, most organizations record it as a minor operational inconvenience. A document is resent, a phone call is made, and the workflow continues with a brief delay. The assumption built into that response is that a missed fax is a self-contained event with a bounded, manageable cost.

Switching fax vendors is not like switching a SaaS productivity tool. Fax infrastructure is embedded in clinical workflows, compliance programs, and operational processes in ways that make a poorly managed vendor transition expensive and disruptive. A vendor that looked good in a demo but cannot deliver on BAA requirements, does not support the routing complexity