Changing Medical Fax Services: Preserve the Number and the Intake Trail
Plan a fax-service transition through number ownership, forwarding, parallel receipt checks, referring-office communication and recovery.

Referring offices store your fax number in their own systems, printed referral forms, speed dials and staff memory. The plan should account for directories and instructions that may continue to send traffic to an old destination. Test the actual route and explain any required sender action.
Define continuity for the number and the intake record
The transition goal, stated plainly, is continuity of inbound receipt plus an unbroken record of what came in and what was done with it. Both halves matter. A number that keeps ringing on the new service but drops the link between a received packet and the queue that works it has not preserved the intake trail.
This article is scoped to the service cutover only. If you are planning to move referral intake off fax altogether, see moving from fax to electronic referrals. If you are replacing the tracking system behind intake, see referral management system migration. Those are larger projects with their own risks.
Step 1: Inventory fax numbers, ownership and the channels still in use
Start with a list, not a vendor demo. For each number, record:
- The number and the line it serves (central intake, a specialty department, a satellite site, records requests).
- Who holds the account: your organization, a practice group, a landlord, a managed-services firm, or a prior vendor.
- The current carrier or service, authorized account contact and written provider confirmation of the options, dependencies and procedures for a change. This checklist does not determine legal number rights or portability rules.
- What arrives on that number today: referrals, prior authorization correspondence, records, pharmacy traffic, vendor noise.
- Who monitors it, on what schedule, and where received faxes are logged.
The last two rows matter because they define the intake trail you must preserve. If a number receives referrals that are then entered into your EHR or a referral platform, the transition has to keep that chain intact.
Decide what each number will do after cutover
For each number, ask providers to document the feasible options: retaining it with the new service, using a supported forwarding arrangement, or moving senders to a different number. Record prerequisites, expected interruption, who confirms completion and what happens if the transition is delayed. Treat retirement as a separate authorized decision after traffic, communications and history requirements have been reviewed. A quiet sample period alone does not establish that a number is no longer needed.
Step 2: Map the transition and who confirms each connection
For each stage, name the receiving destination and an owner who can verify it. A useful transition record contains:
- The number callers or referring offices use, and the receiving service before the change.
- The provider-confirmed action, schedule, dependency and completion evidence.
- Any supported temporary route, including the conditions under which it can be enabled or stopped.
- The destination service that stores the document and the intake queue staff work.
- Available transmission identifiers, source attributes, timestamps and page counts at each step.
Retain the meaning of each timestamp. Original receipt, forwarding receipt and intake creation can be different events. Preserve source attributes as recorded; a displayed sender number alone is not proof of who created the document.
Linear Health's Operational AI Evaluation Kit distinguishes claimed, demonstrated and production-verifiable evidence. Apply that distinction to the exact transition step. A successful test supports that test case; it does not establish uninterrupted service for every future transmission.
Step 3: Run receipt checks before redirecting referring offices
Agree a proposed test set with the transition owners. Use synthetic documents and approved sending endpoints. Include the document types and routing conditions the new service must support, such as:
- One-page and multi-page transmissions, with expected page order and count.
- A deliberately repeated transmission, to inspect how receipt records and intake work are distinguished.
- Applicable business-hours and off-hours routes.
- Documents whose legibility can be compared with the known source.
- A missing or delayed intake event and the recovery task it creates.
For each test, record the sending event, destination receipt, stored document and intake-queue entry. Inspect the full received pages instead of treating equal page counts as proof that content is complete or legible.
Only expect both services to show a receipt if the agreed routing design supports that behavior. For a sequential transfer, retain the old history and test the new path at the relevant stage. A failed test is evidence to resolve before the dependent change proceeds.
Plan advance communications when staff or referring offices need time to prepare. Distinguish a planned effective date from confirmation that a new destination is live; do not instruct senders to use an unverified route as though it is ready.
Step 4: Reconcile both inboxes during the change window
Reconcile every receiving path used during the transition, whether receipt is simultaneous or sequential. Choose a review cadence and coverage that the responsible team can operate. Daily totals can identify a question, but they cannot locate a missing document on their own.
Proposed fax transition reconciliation sheet
| Field | Record |
|---|---|
| Number and transition stage | Which route was expected at that time |
| Receipt identifiers | Old or new service event IDs, with their source |
| Document evidence | Received time, page count and preserved document reference |
| Packet relationship | New intake, duplicate transmission, supplement or unresolved match |
| Intake result | Worked queue or case reference, and what is still unknown |
| Investigation | Evidence checked, owner and next action |
| Resolution | Confirmed disposition, time and corrective action |
Keep an unknown cause unknown. Do not classify a mismatch as a carrier failure, wrong number or dropped page merely because counts differ.
Synthetic reconciliation example
An invented transition review finds 41 old-service receipt events and 39 new-service events. Item-level investigation establishes that one old event repeated a packet already represented and one other unique transmission has no matching new-service receipt. That reconciles 40 distinct expected packet units to 39 represented units and one open question under this example's defined matching rule.
The old service retains the unmatched document. The team checks the destination and intake queue before using the approved recovery route, to avoid creating duplicate work if the event arrives late. The cause remains unknown until evidence establishes it. The counts are invented, not a customer result, and the example does not claim that a particular provider dropped a page.
Step 5: Keep a recovery plan and update office instructions
Document contingency options while provider support is available. Ask what is possible at each transition stage rather than writing a generic instruction to reverse the transfer.
- Which approved destination or procedure receives work if the planned route is unavailable?
- Who is authorized to activate it, and how is its status confirmed?
- Which provider and internal contacts cover the transition and off-hours exceptions?
- How will staff access prior receipts and documents, and reconcile work received through a contingency route?
- What evidence, retained history and communications must be accepted before the old service is closed?
Number changes require a coordinated update of the relevant website, referral instructions, directories and other maintained sources. An unchanged number may still require internal operating instructions or a service notice. Agree the audience, timing, owner and completion check rather than assuming that no communication is necessary.
Make history access and export part of the plan. Do not close the previous account solely because the first new-service fax arrived. Confirm the agreed intake reconciliation, outstanding-work ownership and retention/access responsibilities with the designated owners.
A practical evaluation method for the new service
If you are choosing the new fax service, or a referral coordination layer that sits on top of it, score the vendor against the same evidence tiers used in the Operational AI Evaluation Kit. The kit asks vendors to name the systems live in production, show how automated actions are logged and corrected, and define completion in observable terms. For a fax cutover, the questions become:
- Can you show a timestamped trace of a fax from receipt to intake record?
- What happens when a page is missing, duplicated or unreadable, and who owns that exception?
- Can we export our full received-fax history, with original timestamps, if we leave?
- What is the written procedure when forwarding or porting fails?
A high overall score does not cancel an unresolved data-handling or accountability gap; the kit treats those as gates that go to the responsible reviewer. That same discipline applies here.
If you are evaluating whether referral intake coordination should run alongside the new fax service, book a demo and bring your reconciliation sheet; a useful demo should be able to show the receipt-to-queue trace, not just the dashboard. Linear Health describes its approach as operational AI for healthcare that does not replace clinical judgment, with established integrations with athenahealth, eClinicalWorks, NextGen and Greenway Health; field-level actions and a buyer's configuration still need demonstration (Linear Health referral coordination).
Fax transition checklist
- Inventory numbers, authorized account contacts, traffic types and staff coverage.
- Obtain written provider confirmation of options and dependencies for each number.
- Map the expected receiving path at every transition stage.
- Define test cases, acceptance evidence and the owner of each decision.
- Prepare communications that distinguish a planned change from a verified live route.
- Test synthetic transmissions through receipt, document storage and the worked intake queue.
- Reconcile individual receipts, duplicates and supplements using their evidence.
- Resolve blocking gaps or keep the dependent transition step on hold.
- Confirm the supported contingency path, history access and outstanding-work owners.
- Close the former service only after its agreed shutdown gates are accepted.
For the wider workflow, see referral coordination software. To investigate how intake coordination would connect to your selected fax service, talk with the Linear team using a synthetic receipt-to-queue trace.
Frequently asked questions
Do we have to change our fax number when changing services?
Must both services receive the number at the same time?
What should reconciliation capture beyond counts?
When should referring offices be notified?
What is the most important recovery question?
Sources
Sources accessed November 4, 2026.
Linear Health publishes educational articles about operational AI for healthcare.



