Scheduling with referral rules
How do we check the referral, network and payer rules before an appointment is confirmed, so the visit is not denied for a missing referral or an out-of-network provider?
Run the payer's rules at booking, not at billing. When a visit is requested, Callvu prefills the patient's coverage and the plan's rules from the EHR and the eligibility response, classifies the visit (the specialty, the visit type, the provider, the location) against the plan's referral requirement, the network status of the provider and the location, the authorization requirement and the benefit limits, chases the referral from the primary care office or the authorization through its process on a clock set from the requested date, routes a visit that fails the rules to the scheduling desk in the Decision Desk with the options (another provider in network, a different date after the referral, a self-pay estimate with the patient's acknowledgment), and confirms the appointment in the scheduling system and the EHR only when the rules pass or the patient has chosen with the facts.
In scopeComplex: multi-party handoffsCallvu moves: prefill, classify, chase and verify, write back
Last updated November 7, 2026.
The problem today
The patient waited six weeks for the specialist, and the claim denied because the plan needed a referral nobody had requested.
A patient books a specialist visit. The scheduler confirms the slot. Weeks later the visit happens, the claim denies for no referral or an out-of-network location, and the patient receives a bill for the whole charge. The scheduler had the plan on screen but not the rules, and the referral the primary care office could have sent in a day was never asked for.
Payer network and referral rules are checkable at booking: whether the plan requires a referral for the specialty, whether the provider and the location are in network for the plan's product, whether the visit type needs authorization, whether a benefit limit (visits per year) is reached. The referral is a document the primary care office produces; the authorization is a process with a clock; the patient's choice to proceed without them is a disclosure the rules require.
A rule checked at booking costs a text to the primary care office; a rule checked at billing costs the patient the visit.
How it runs
From the requestto the system of record.
A visit is requested by the patient in the portal or the app, by a referring office, by the call center or by an AI assistant. Callvu prefills the coverage and opens the booking check.
- Patient
- Chooses the slot, sees the rules' result, and acknowledges a self-pay choice where they make one.
- Primary care or referring office
- Sends the referral through its link or the e-referral channel.
- Scheduling desk
- Decides visits that fail the rules in the Decision Desk with the options.
- Callvu
- Prefills, classifies the visit against the rules, chases the referral and the authorization, routes and writes.
Prefill the coverage and the rules
The patient's active coverage and the eligibility response, the plan's product and network, the referral and authorization requirements by specialty and visit type, the benefit limits used, the provider's and the location's network status for the plan, and any existing referral or authorization on file are prefilled from the EHR and the payer data.
Classify the visit
The requested visit (the specialty, the visit type, the provider, the location, the date) is classified against the rules: referral required and present, missing or expired; provider and location in or out of network; authorization required (routed to the authorization process); benefit limit reached; the result is shown to the scheduler and the patient in plain terms before the slot is held.
Chase and verify
A missing referral is requested from the primary care or referring office through its link or the e-referral channel with the specialty, the reason and the requested date, chased on a clock set from the date, read on arrival and checked (the patient, the specialty, the number of visits, the validity period); an authorization runs through its process on the same clock; the appointment is held pending the result where the policy allows.
Decide and write back
A visit that passes confirms by rule; a visit that fails goes to the scheduling desk in the Decision Desk with the options and only those outcomes: rebook with an in-network provider or location, move the date after the referral or authorization, or proceed as self-pay with the estimate and the patient's written acknowledgment; the confirmed appointment with the referral or authorization reference and the rule result is written to the scheduling system and the EHR, and the patient receives the confirmation with what to bring.
Where it ends: The referral, network and authorization rules were checked before the slot was confirmed, the referral was chased from the office that issues it, and the patient either booked a visit the plan will pay or chose with the facts. The Decision Trace shows the rules applied and any decision; the Audit Trace shows the referral request and arrival, the authorization and the confirmation with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The portal, the app, a referring office, the call center or an AI assistant; the patient sees the rules' result before the slot is held.
The back office
The scheduling desk decides only failing visits with the options; the referral and authorization chases run on their own.
The Decision Desk
- A visit that fails the referral, network or authorization rules goes to the scheduling desk in the Decision Desk with the options and only rebook in network, move the date, or proceed as self-pay with the estimate and the patient's written acknowledgment.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
23 hospitals in the Ministry of Health network run on Callvu.
Across Callvu customers
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
What is checked before the appointment is confirmed?
Whether the plan requires a referral and one is on file and valid, whether the provider and the location are in network for the plan's product, whether the visit type needs authorization, and whether a benefit limit is reached.
How is a missing referral obtained?
It is requested from the primary care or referring office through its link or the e-referral channel at booking, chased against the visit date, and checked on arrival for the patient, the specialty, the visits and the validity.
Can the patient proceed without a referral?
Only through the scheduling desk, with an estimate and a written acknowledgment, and with the No Surprises Act notice and consent where an out-of-network provider is involved.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.