Key facts
- Federal health privacy officials permit faxing protected health information for treatment when reasonable and appropriate safeguards are in place.
- A fax machine, app or cloud service cannot be compliant on an organization's behalf; the covered entity must implement administrative, technical and physical safeguards.
- Once a faxed page becomes digital, Security Rule obligations extend to storage, OCR, extraction, routing and audit logging.
- Cloud fax platforms that store electronic protected health information are generally business associates; transmission-only carriers may fall under the conduit exception.
- Encryption, multifactor authentication, access controls, audit logs and business associate agreements are core controls, but policies, training and risk analysis remain with the practice.
- Proposed Security Rule changes would make encryption mandatory, require multifactor authentication and asset inventories, and explicitly address AI risk analysis.
Federal health privacy officials have never instructed hospitals and clinics to abandon the fax machine. Under the HIPAA Privacy Rule, a physician may disclose protected health information to another provider by fax for treatment, provided reasonable and appropriate safeguards are in place. The compliance question is not whether fax exists, but how the document is handled before and after it arrives.
The distinction becomes visible when two identical referral forms leave the same office on the same morning. One travels through an encrypted, logged channel covered by a signed business associate agreement, and an optical character recognition system indexes it into the correct chart. The other lands in an output tray in a shared hallway. The document is the same. The legal posture is not.
HIPAA regulates the safeguards around a fax, not the machine
A fax machine, a mobile app or a cloud service cannot be compliant on an organization's behalf. HIPAA asks whether a covered entity or business associate has implemented reasonable administrative, technical and physical safeguards around each disclosure. Health and Human Services guidance points to practical steps such as confirming the recipient's fax number and pre-programming frequently used numbers to reduce dialing errors.
Once a faxed page becomes a digital file, the Security Rule's safeguard standards follow the data. That shift matters because fax is no longer only a telephone-line transaction. Modern workflows scan, store, route, read and extract information from faxed pages. Each of those steps can create or expose electronic protected health information.
Industry experts say the common question — whether a fax service is HIPAA compliant — starts in the wrong place. A better question is who can open the document, whether every action is logged, and whether the business associate agreement covers the software reading the page, not just the line carrying it. Those questions concern the workflow, not a product label.
The digital page pulls the Security Rule into the workflow
OCR engines, extraction models and routing rules now handle much of the work that once belonged to a person standing beside a fax machine. A page may be converted to text, matched to a patient, filed to an electronic health record and routed to a specialist without anyone touching paper. Each automated step carries the same obligation as the transmission itself.
Encryption is the obvious starting point. Under the current Security Rule, encryption is an addressable specification, a term that has led some organizations to treat it as optional. It is not. For cloud fax and AI-assisted document handling, encryption should protect stored images and OCR text at rest and in transit. Every send, receipt, view and routing decision should also generate an audit entry that authorized staff can retrieve later.
That audit trail is not administrative decoration. It is evidence that the organization can reconstruct who saw a document, when it moved, and which automated process touched it. Without that record, a practice cannot reliably investigate a misdirection or demonstrate that safeguards were operating.
Business associate agreements must follow the data
The business associate agreement holds the arrangement together legally. Federal sample provisions outline what a contract must require of a vendor, including Security Rule safeguards, breach reporting and matching terms for subcontractors. Cloud guidance adds an important distinction: a cloud provider that stores electronic protected health information is a business associate even if it does not hold the encryption key. The conduit exception is limited to transmission-only services.
By that logic, a telephone carrier moving a fax signal can be treated as a conduit. A cloud fax platform that stores copies of documents generally cannot. If OCR or data extraction runs at a separate company, that company needs coverage too, usually through a subcontractor agreement with the primary vendor. The agreement must reach the software that reads the page, not merely the network that delivers it.
This is where procurement can go wrong. A buyer may confirm that the fax line is encrypted and that the vendor will sign a business associate agreement, then discover that the OCR component is provided by another company outside the contract. The compliance chain breaks at the point where the data is most useful — when it is converted into searchable text and matched to a patient record.
Routing errors are the new misdialed numbers
Federal guidance on misdialed fax numbers applies with equal force to automated routing rules. If a rule misfires and files a referral under the wrong patient, the result is no different from a call placed to the wrong number. The information has been disclosed to someone who should not have received it.
Automation can reduce human error, but it can also scale a mistake. A single bad rule can misroute dozens of documents before anyone notices. Staff should review uncertain matches before anything is filed. The system should flag low-confidence OCR results, ambiguous patient identifiers and unusual routing patterns. A vendor that offers automation without a human review step is offering speed without a control.
The same principle applies to access. Role-based permissions should limit who can open, download or reroute faxed records. A shared queue in a hallway is an obvious physical risk, but a shared digital queue with broad permissions can be just as exposed. The control has to match the workflow.
Access control and multifactor authentication have documented stakes
Access control rounds out the list of core safeguards, and skipping it has a documented cost. A 2024 attack on a major healthcare payment processor began with compromised credentials on a system where multifactor authentication was not turned on. The breach ultimately affected approximately 193 million individuals.
That case illustrates why identity controls belong in any discussion of fax and document workflow. A fax platform that stores patient records is an access point. If staff can log in with a reused password and no second factor, encryption and audit logs may not be enough. Multifactor authentication, least-privilege access and periodic access reviews are not optional extras for systems that hold protected health information.
The broader breach environment is already severe. One industry count recorded 772 large healthcare data breaches on the federal OCR portal for 2025 as of early January 2026, a record. The number reflects a reality that fax workflows share with every other health IT system: the point of exposure is often a process, not a single device.
The Security Rule is catching up with software that reads
Federal regulators have started writing AI into the rules, though the biggest changes remain proposals. A Security Rule overhaul published on January 6, 2025 would make encryption of electronic protected health information mandatory with limited exceptions, require multifactor authentication and call for an annual technology asset inventory and network map.
The proposal also names AI directly. A risk analysis would have to consider the type and amount of protected health information accessed by an AI tool, to whom the data is disclosed and to whom the output is provided. That language reflects a simple reality: when software reads a fax, the software becomes part of the disclosure pathway.
Timing is uncertain. After nearly 5,000 comments, final action is now targeted for July 2027. The federal estimate put first-year compliance costs at $9 billion, and the proposal would give organizations 240 days after the final rule to comply. Regardless of the timetable, the division of responsibility is unlikely to change. Vendors provide tools. Practices still run the program.
Shadow AI complicates the inventory
That division gets blurry when staff bring in AI tools on their own. In a survey of 250 health security and AI leaders, 72% said AI tools or agents are being deployed without formal IT approval. Tools that IT never approved are unlikely to appear in an asset inventory, let alone be checked against a business associate agreement.
An inventory requirement like the one proposed is meant to surface those tools. The same survey found that 28% of organizations have agentic AI in production already, while 44% are piloting or testing it. The pressure to adopt AI is not waiting for the rulemaking process. Staff may use a transcription tool, a summarization service or an OCR add-on before anyone in compliance knows it exists.
For fax workflows, shadow AI is especially dangerous because the page often contains unstructured referral notes, lab results and identifiers. A tool that reads a fax may send text to an external model, retain it for training or store it outside the covered entity's control. The business associate agreement must cover that processing, and the organization must know where the reading actually happens.
What buyers should ask before shortlisting a vendor
A practice can buy a compliant document stack. Compliance is not sold that way. It has to be run from inside the practice, with written policies that are updated and staff who are trained on them. A fax vendor that cannot produce encryption, access controls, audit logs and a signed business associate agreement should not make the shortlist.
For the AI layer, buyers should push further. They should ask where the reading happens, whether the business associate agreement extends that far, whether automated actions are logged and who checks the matches the software is not sure about. They should confirm that OCR text, not just the fax image, is protected at rest and in transit. They should find out whether the vendor uses subcontractors and whether those subcontractors are covered by matching terms.
They should also test the audit trail. Can the practice pull a report showing every time a document was viewed, re-routed or exported? Can it identify which automated rule filed a referral and why? Can it prove that a low-confidence match was reviewed by a person before it reached the chart?
The answers separate a document-handling service from a compliance program. Federal health privacy officials have never banned fax. They have required reasonable safeguards, and those safeguards now extend to the software that reads the page. The practical test is not whether a fax machine is labeled compliant, but whether the organization can show who opened the document, what automated tools processed it, whether those actions were logged, and whether a signed agreement covered every vendor in the path.
Source: TNW | Contributed News