---
title: "Referral Intake: From Faxed Referral to Booked Patient"
description: "Referral intake turns a faxed referral into a booked patient. The steps, what a complete referral needs, the exceptions, and a flow that does it end to end."
url: https://flowrunner.ai/blog/fax-referral-intake
date_published: 2026-11-12
date_modified: 2026-11-13T14:04:35-08:00
---

Articles November 12, 2026 Updated November 13, 2026 6 min read

# Referral Intake: How to Process Faxed Referrals Until the Patient Is Booked

Referral intake turns a faxed referral into a booked patient. The steps, what a complete referral needs, the exceptions, and a flow that does it end to end.

![Cream card headed Referral intake with the statement Faxed in. Booked out., the line What's missing goes back to the referring office., and a tally of 6 checks, 1 fax back, and 1 decision.](https://flowrunner.ai/images/blog/fax-referral-intake-hero.webp)

Referral intake is the work between a referral arriving and the patient having a first appointment. Your team reads each referral and checks that it has what you need, including active insurance. Then a coordinator accepts it and someone reaches the patient to book.

Reading the fax is the quick part. The hours go to chasing referring offices for whatever is missing and to reaching patients who don’t pick up. A FlowRunner flow does that work from your intake fax line and brings your coordinator only the decision.

1.  1 **Fax arrives** On your intake fax line
2.  2 **Agent reads it** Patient, referrer, reason, insurance
3.  3 **Checked and filed** In your EHR and with the payer
4.  4 **Coordinator decides** Accept, decline, or ask for more
5.  5 **Patient texted** To book, with a request for scheduling

## One referral, start to finish

Here is a sample referral fax from Lakeview Family Medicine to Northpoint Health, a telepsychiatry practice. The flow read the six-page PDF and checked it against Healthie and Stedi. Everything is there except the insurance card.

**Lakeview Family Medicine** Referral fax, 6 pages, received Nov 12, 9:12 AM

| Field | What the fax says |
| --- | --- |
| Patient | Jordan Reyes, born 07/22/1992, (614) 555-0182 |
| Referring provider | Priya Shah, MD, NPI 1234567893, fax (614) 555-0147 |
| Already in Healthie as a referring physician, matched by NPI. |
| Reason | Major depressive disorder, recurrent. Two SSRI trials. Psychiatric evaluation and medication management. |
| Insurance | Aetna PPO, member ID W284551093 |
| Stedi shows active coverage, checked at 9:13 AM. |
| Clinical notes | Office visit of Oct 28, medication list, PHQ-9 |
| Insurance card | Not attached |
| Your checklist requires a copy of the card, front and back. The member ID was enough to check eligibility. |

Jordan has no chart yet, so the flow creates one in Healthie and files the fax on it with the referral. It faxes Lakeview a one-page request for the card, then asks the intake coordinator in Slack with only what they need to decide.

Slack, the #referral-intake channel

F

FlowRunner 9:15 AM

**New referral from Lakeview Family Medicine**

J.R., 34, referred by Priya Shah, MD, for psychiatric evaluation and medication management after two SSRI trials. Aetna is active. The insurance card is missing and was requested from Lakeview by fax at 9:14 AM. The fax and notes are on the chart in Healthie.

Accept Decline Need more info

KT

Kim Tran 9:21 AM

Any safety concerns in the notes?

F

FlowRunner 9:21 AM

The Oct 28 note records no suicidal ideation and no psychiatric hospitalizations. PHQ-9 was 17. Current medication is escitalopram 10 mg.

Kim clicks Accept, and the flow texts Jordan. The text says who referred them and how to book, and nothing about why:

**Text message to Jordan Reyes** Sent by Twilio, Nov 12, 9:26 AM

Hi Jordan, this is Northpoint Health. Dr. Shah's office sent us a referral for you. Book your first visit at northpoint.example/book or call us at (614) 555-0100. Reply STOP to opt out.

It also creates an appointment request in Healthie for your scheduling team. At 11:02 AM Lakeview faxes the card back. That fax starts its own run: the agent sees an insurance card for Jordan Reyes, finds the chart, and files it. Jordan’s chart now shows:

**Healthie, Jordan Reyes** Referral, documents, and appointment request

Referred by Priya Shah, MD (NPI 1234567893), Lakeview Family Medicine, for psychiatric evaluation and medication management. Referral fax of Nov 12 filed in Intake › Referrals. Appointment request open: new referral, accepted by Kim Tran in Slack at 9:26 AM. Insurance card received by fax at 11:02 AM and filed.

If Jordan hasn’t booked two days later, the flow finds no appointment in Healthie, sends one reminder text, and tells the coordinator.

A complete referral skips the fax back to the referring office and reaches the coordinator ready to accept. Every run keeps a step-by-step record of what the flow read and who decided. When Lakeview calls to ask about Jordan, you open the run and see it.

The fax comes in through [Documo](https://flowrunner.ai/integrations/documo), [SRFax](https://flowrunner.ai/integrations/srfax), or [RingCentral](https://flowrunner.ai/integrations/ringcentral), and the chart is [Healthie](https://flowrunner.ai/integrations/healthie) or [DrChrono](https://flowrunner.ai/integrations/drchrono). Eligibility goes through [Stedi](https://flowrunner.ai/integrations/stedi), texts go out by [Twilio](https://flowrunner.ai/integrations/twilio), and the coordinator answers in [Slack](https://flowrunner.ai/integrations/slack) or by email.

## The referral intake process, step by step

1.  Receive the referral by fax, email, EHR message, or phone, and log it.
2.  Find the patient’s chart, or create one without making a duplicate.
3.  Check the referral against your intake checklist.
4.  Ask the referring office for anything missing.
5.  Check eligibility, and flag services that need prior authorization.
6.  Accept or decline, and tell the referring office either way.
7.  Reach the patient and book the first visit.

## What a complete referral includes

| Item | Why intake needs it |
| --- | --- |
| Patient name, date of birth, phone | To match the chart and reach the patient |
| Referring provider, NPI, fax number | To record the referral and send updates back |
| Reason for referral | To decide whether it fits your services |
| Insurance and member ID | To check eligibility before booking |
| Insurance card copy | For billing, if your checklist requires it |
| Clinical notes | For the clinical review before you accept |

## Exceptions that stall referrals

| Exception | What it looks like | What the flow does |
| --- | --- | --- |
| Missing item | No insurance card, no notes, no phone number | Faxes the referring office a request and files the reply on the chart |
| Inactive coverage | Stedi returns no active plan, or the payer rejects the check | Shows the coordinator the payer’s response before they decide |
| Prior authorization | Eligibility flags the service as needing approval | Tells the coordinator before the patient is booked |
| Possible duplicate | Same name, different date of birth | Asks the coordinator which chart, instead of creating another |
| Outside your services | A condition you don’t treat, or a state you don’t serve | The coordinator declines and the flow faxes the referring office |
| Unreadable page | A dark scan or a handwritten line | Marks the field unreadable and asks, instead of guessing |

For the authorization itself after acceptance, see [prior authorization](https://flowrunner.ai/use-cases/prior-authorization).

## Other ways to handle faxed referrals

| Approach | How it works | When it fits |
| --- | --- | --- |
| A FlowRunner flow | Reads each fax, checks it in your EHR and with the payer, and carries it through to the patient’s text | The work spans your fax line, EHR, and payer |
| Fax intake tools | Read, split, and route referral faxes into queues | Sorting the fax pile is your bottleneck |
| Referral platforms | Extract the referral, match the chart, and text the patient a scheduling link, as [Medsender](https://medsender.com/referral-management) describes | You want one product to own the referral |

Documo, whose fax line can start this flow, writes that intake automation [“removes the sorting, not the follow-up”](https://www.documo.com/blog/what-actually-changes-when-you-automate-referral-intake/) and that its product does not call patients or schedule appointments. The follow-up is where referrals get lost. It runs across the fax line, the EHR, the payer, and the patient’s phone, so it needs an orchestration layer that works across all of them. FlowRunner is built for that layer.

## HIPAA and what each person sees

FlowRunner signs a Business Associate Agreement on the Business plan and higher, and the BAA must be executed before any PHI flows through your workspace. Details are on our [Trust and Security page](https://flowrunner.ai/trust). Every other service in the path handles PHI too, so each needs its own BAA with you:

-   the fax service
-   the EHR
-   Stedi
-   Slack, or your email provider
-   the SMS provider
-   the AI provider whose model reads the fax

FlowRunner runs the agent on your own AI provider key, so the fax goes to that provider under your account. Our [HIPAA software checklist](https://flowrunner.ai/blog/hipaa-compliance-software-checklist) covers what to ask each vendor. Keep the Slack card short, as in the example, and keep diagnoses out of the patient text.

## How to start

Write down your intake checklist first, including what you accept and who decides. Then start with one fax line.

For the first two weeks, have the coordinator compare what the agent read with the fax before accepting. Once the readings stop needing corrections, let the flow fax referring offices and text patients on its own. Healthie’s API is an add-on on its Group and Enterprise plans, so confirm you have it. On DrChrono, which has no referral record, the flow files the referral as a chart document plus a task for intake. More for clinics and digital-health teams is on the [healthcare page](https://flowrunner.ai/industries/healthcare).

## We can build this for you.

It's custom work, built around how you do things by our implementation team at Midnight Flow, in your own FlowRunner workspace.

-   Every referral read, checked for what is missing, approved by your team, and the patient texted to book
    
    Built and tested by our team. Runs on your FlowRunner plan.
    
    [Have us build this](https://midnightflow.ai/packages/clinic-referral-fax-intake?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=healthcare-intake&utm_content=blog.aside&utm_term=fax-referral-intake)

## Frequently asked questions

### What is referral intake?

Referral intake is the work between a referral arriving and the patient being booked. The team checks that the referral is complete and the insurance is active, and a coordinator accepts it before the patient is contacted to schedule.

### What is the difference between referral intake and referral management?

Referral intake ends when the patient is booked. Referral management includes intake and goes on to track the referral through the visit and report back to the referring provider, which is how the loop gets closed.

### Can faxed referrals be automated under HIPAA?

Yes, as long as every service that touches the referral has a Business Associate Agreement with you. FlowRunner signs a BAA on the Business plan and higher, and the BAA must be executed before any PHI flows through the workspace. See [Trust and Security](https://flowrunner.ai/trust).

By [Mark Piller](https://flowrunner.ai/about), Founder of FlowRunner [Editorial policy](https://flowrunner.ai/editorial-policy)

---
Markdown version of https://flowrunner.ai/blog/fax-referral-intake. Site index: https://flowrunner.ai/llms.txt
