It happens in every organization that sends fax at volume. A digit is transposed, a directory entry is out of date, a number gets reassigned to a different business, or a speed-dial entry points to the wrong place. The fax goes through, delivery is confirmed, and someone realizes a few minutes or a few days later that it reached a stranger.
What happens next matters more than the error itself. A calm, documented response limits harm and gives your compliance team what it needs. A scramble, or worse, silence, turns a routine mistake into a larger problem. This post gives staff and administrators a practical sequence to follow. It is meant to sit alongside the post on how fax fits into your incident response plan, which covers the broader planning.
Step 1: Report It Immediately
The first action is not fixing the problem. It is telling the right person. Staff should know exactly who to contact, whether that is a privacy officer, a compliance mailbox, or a supervisor, and should feel safe doing so. Organizations that treat reporting as blame discourage it, and unreported errors are the ones that grow.
Record the moment of discovery. Many notification timelines run from the date an incident is discovered, so an accurate discovery time is worth capturing at once.
Step 2: Identify What Was Sent and Where
Before anyone calls the recipient, gather the facts:
- The number the fax was sent to
- The date and time of transmission
- Who sent it and from which system
- What the document contained, including how many patients are involved and what kinds of information
The transmission record answers the first three. In Passport, the Enterprise Status Manager shows when a fax was sent, from which number, to which number, and whether delivery was confirmed. It will not show you the document itself, because content is destroyed after delivery, as the FAQ Friday on fax content after delivery explains. To learn what was in the fax, go back to the source system, such as the EHR, LIS, or document management platform, and use the timestamp and sender to find the original.
Step 3: Contact the Unintended Recipient
Once you know the number, try to reach the person or business that received the fax. Staff should use a script so the conversation stays consistent:
- Explain that a document was sent to their fax number in error
- Ask them to confirm they received it and to keep the contents confidential
- Ask them to destroy it securely, or to return it if they prefer, and to tell you when that is done
- Record who you spoke with, when, and what they agreed to do
Some recipients will be cooperative. Some will not answer. Document every attempt, including unsuccessful ones. If the number belongs to another healthcare organization, your privacy officer may want to handle the contact directly.
Step 4: Hand the Assessment to Compliance
Whether a misdirected fax is a reportable breach is a determination for your privacy officer and legal counsel, not for the sender or the IT team. The HHS breach notification guidance describes the factors involved, including the nature of the information, who received it, whether it was actually viewed, and how far the risk was reduced. Facts that matter include whether the recipient was another covered entity, whether they have confirmed destruction, and what the document contained.
Give compliance everything you gathered in the earlier steps. If the determination is that notification is required, timelines apply, and they are measured from discovery. That is why the first step carries so much weight.
Step 5: Find the Root Cause
Every misdirected fax has a cause, and the cause usually points to a fixable gap:
- A typo. Consider whether the workflow could verify the number before sending, especially for high-sensitivity documents.
- An outdated directory entry. Clean up the entry and review neighboring entries. The post on how fax number management works at the enterprise level describes keeping directories accurate.
- A reassigned number. This is common with old destinations. Failed or unusual transmissions can prompt review.
- A manual step that automation could remove. Where a workflow sends to the same destination repeatedly, automated transmission with a verified destination reduces the chance of a typing error.
Step 6: Document and Learn
Keep a short record of each incident: what happened, how it was found, who was contacted, what the recipient said, what compliance concluded, and what was changed. The searchable history in Passport provides a reliable backbone for that record. Patterns across incidents are often more useful than any single one. If the same department or destination appears repeatedly, that is where to focus training and process changes.
Preventing the Next One
Prevention is mostly about reducing manual number entry and keeping directories current:
- Use verified contact entries instead of free-typed numbers for frequent destinations
- Review high-volume destinations, such as payers and referral partners, on a schedule
- Treat failed transmissions as a signal to verify the number
- Limit who can send from sensitive workgroups, as described in the post on role-based access controls in Passport
- Include fax in your periodic review, using the post on how to conduct a fax security audit as a guide
A misdirected fax is an error worth taking seriously and a situation worth being prepared for. Staff who know the first three steps by heart will handle it better than any policy binder can.
Schedule a strategy call with the Lane team to discuss how Passport’s transmission records and monitoring support your response process.



