Fixed quote after a free call

Referral management and patient intake automation for clinics

Referrals arrive by fax, e-referral, email and portal, and intake paperwork depends on staff remembering to send and chase it. We build a workflow that logs every referral against the patient, sends the right intake and consent forms for the appointment type, chases what is missing, lists gaps a few days before the visit and drafts the closing-the-loop note to the referring provider. A typical build costs $1,000 to $2,500 per workflow and takes four to five weeks.

The problem

Why referrals and intake paperwork stall

A referral is a promise to another clinician. It might arrive as a fax, an e-referral, a scanned letter in an email or a portal message, and it has to be matched to a patient, triaged by a clinician, booked and acknowledged. When referrals sit in a tray, patients wait and referrers stop sending them.

Intake has its own chase: demographics, insurance or self-pay details, health questionnaires, consent forms and policies. When forms come back late, the first appointment starts with paperwork and the clinician sees the history minutes before the patient.

What we build

What our referral management and intake automation includes

Referral log

Every incoming referral recorded with referrer, date, reason and status, from fax inbox, email or e-referral feed.

Clinician triage queue

New referrals listed for the clinician who triages them, with the documents attached. Priority is set by the clinician.

Forms by appointment type

The right intake, questionnaire and consent forms sent automatically once the visit is booked.

Polite chasing

One or two reminders for missing forms, then a flag for the coordinator.

Pre-visit gap list

A daily list of upcoming visits with missing forms, referral letters or unverified details.

Close the loop

A draft acknowledgement to the referring provider once the patient is booked or seen, sent after staff approve it.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Referral received

    A fax, email or e-referral is logged and matched to an existing or new patient record.

  2. 02 Clinician or medical director decides

    Clinician triages

    The triaging clinician reviews the referral and sets priority and appointment type.

  3. 03 Automated

    Forms sent and chased

    Once booked, the patient gets secure links to the right forms, with up to two reminders.

  4. 04 Coordinator review

    Coordinator checks gaps

    The pre-visit list shows what is missing, and the coordinator fixes it with the patient or referrer.

  5. 05 Clinician or medical director decides

    Clinician reviews history

    The clinician reviews the completed history and decides what it means for care.

How it behaves

How the referral and intake workflow behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the patient sees

  • A booking confirmation once the referral is triaged
  • Secure links to forms a few days before the visit
  • Up to two reminders, then help at the desk if needed

What staff see

  • A referral log with status for every referral
  • A triage queue for the clinician
  • A daily pre-visit gap list

What the automation does

  • Logs and matches referrals from every inbox
  • Sends the right forms for the appointment type
  • Drafts the referrer acknowledgement for approval

Edge cases and fallbacks

Referral cannot be matched to a patient
Goes to the coordinator unmatched; nothing is guessed.
Referral is marked urgent by the referrer
Flagged to the triaging clinician at once and handled under the clinic's urgent process.
Patient never completes forms
Appears on the pre-visit list and completes them on arrival.
EHR write-back fails
A clean PDF goes to staff and the failure is logged and retried.
Fax or form service outage
Referrals are still received by the existing route and the practice manager gets an alert.

Architecture

Referral and intake workflow for a clinic at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Referrals in Fax, email, portal n8n workflow Log and match Document read Key fields only Clinician Triage, priority Intake forms Sent and chased Coordinator Pre-visit gaps EHR record Docs attached
  • Input
  • Logic and services
  • AI step
  • People
  • Output
  • Data

How it flows

  1. 1 Referrals arrive by fax inbox, email or e-referral and are logged by the workflow.
  2. 2 Key fields such as patient name, date of birth and referrer are read so staff can match the record; the clinician sees the original document.
  3. 3 After clinician triage and booking, intake forms go out and are chased automatically.
  4. 4 The coordinator clears pre-visit gaps and completed documents are attached to the EHR record.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Referral management & patient intake project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How referrals arrive, who triages, forms per appointment type and what the EHR accepts.

  2. 02

    Design

    2 to 3 days

    Referral statuses, matching rules, form sets, reminder timing and the referrer note.

  3. 03

    Build

    About 2 weeks

    Referral intake, document reading, form sending, gap list and EHR connection.

  4. 04

    Shadow run

    About 1 week

    Referrals are logged in parallel with the current tray while staff check every match.

  5. 05

    Launch

    1 to 2 days

    Go live for one service line, then widen.

  6. 06

    Support

    Ongoing

    New referral sources, form changes and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Cloud fax or e-referral inbox (confirmed per project) HIPAA- or GDPR-suitable form tool, or the EHR's own intake module EHR via FHIR API or vendor API Claude or OpenAI for field extraction (under a BAA or processor contract) Slack, Teams or email for staff alerts

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Workflow mapping with the clinic team, wording, data flows and a written specification.

    $200 – $400

  • Build

    The n8n workflow, rules, AI step where useful, logging and error handling.

    $500 – $1,300

  • Integrations

    EHR or practice management access, messaging and staff alert channels.

    $150 – $400

  • Testing and shadow run

    Acceptance tests and a side-by-side run while staff keep the old process.

    $100 – $250

  • Launch and training

    Go-live, front-desk walkthrough and a short run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Writing documents back into some EHRs needs a vendor partner route; if so, we quote that part separately. Form and fax services are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Fax and form tools: Your fax and form providers' own plans, unless the EHR's intake module is used.
  • n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • AI model usage: Billed by the provider per use under its own healthcare terms; short sorting and summary steps are usually a small monthly amount at clinic volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: business associates

Fax services, form tools, automation hosts and AI providers that handle referral documents need a business associate agreement before patient information flows.

Source: www.law.cornell.edu

US: patient right of access

Patients can request their records and covered entities must act within 30 days, with one 30-day extension, so intake documents must be filed where staff can find and export them.

Source: www.law.cornell.edu

EU and UK: health data

Referral letters and health questionnaires are special category data under Article 9 GDPR and UK GDPR, so collection is kept to what the clinic needs and processors are under contract.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Referral management & patient intake questions, answered.

It tracks each incoming referral from receipt to booking and back to the referrer. Our workflow adds that tracking around your existing EHR and fax or e-referral inbox, rather than asking you to buy a separate system.

No. It reads a few identifying fields so staff can match the patient. The triaging clinician reads the referral and sets the priority.

Yes, if your fax service delivers documents by email or API. The workflow extracts identifying fields for matching and attaches the original for the clinician.

Some EHRs have their own intake module and we trigger it; otherwise we use a form tool that signs a BAA or processor agreement and file completed forms through the EHR's API or as a clean PDF.

The paper or tablet route stays. The pre-visit list shows who has not completed forms so staff can help on arrival.

Days from referral received to triage and to first visit, share of visits with complete intake the day before, and referrals acknowledged to the referrer.

Free 20-minute call

Want this for your healthcare clinic?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call