First Response Wins: Why Referral Speed Matters for Patients and Revenue

A hospital discharge planner has a patient going home tomorrow and a referral packet ready. They send it to several home health agencies at once, and the patient goes to the first agency that confirms. Until an agency says yes, the discharge plan isn’t final, and a patient who is medically ready to leave can spend another night in the hospital waiting. Families rarely weigh in, since they usually don’t know one agency from another. The referral goes to whichever agency answers first.

When a referral goes to more than one agency, response time often decides who gets the patient and how soon the patient gets home. Yet decision time rarely shows up in the reports that leaders of multi-branch home-based care organizations review.

Decision time is hard to report on

Leaders of multi-branch organizations tell us they want to track decision time but struggle to pull the data together. Referrals arrive by fax, portal, email, and phone, and each channel records arrival differently, if at all. Accepted referrals get entered into the EHR, while declined and unanswered referrals often stay in an inbox or a spreadsheet. Without a consistent record of when each packet arrived and when the agency answered, the hours between the two are hard to measure, even though that window is where agencies win or lose patients. A referral that went to a faster agency rarely shows up as a loss in any report.

Branches make the picture harder to see. Each branch often sets its own acceptance rules, such as which ZIP codes it serves and which payers it takes, so the same referral could get a yes at one branch and a no at another. Leadership usually has no view of how each branch performs against its own rules, including how long its referrals wait for a decision and how many expire before anyone answers.

Agencies affiliated with a health system have another reason to care, since every patient waiting on a post-acute decision is occupying one of the system’s own hospital beds. Those waits add up. In Florida alone, hospitals reported 243,000 medically cleared patients who had to stay in the hospital between mid-2024 and mid-2025 because of delays outside the hospital’s control. Hospitals also have to give patients a choice of agencies at discharge, so a slow answer can send a patient from your own system’s hospital to an outside agency.

In hospice, those hours matter even more. The median hospice stay was 19 days in 2024, and a quarter of hospice decedents had stays of 5 days or less. For those families, a referral that waits overnight for a decision uses up a real share of the time they have in hospice.

Saying no quickly protects margin

Speeding up acceptances can backfire. Some referrals fall outside the service area or need clinical capacity a branch doesn’t have this week. Others come from a payer that won’t cover the plan of care. Accepting those referrals quickly leads to visits the branch can’t staff and claims that don’t get paid. Holding a referral for most of a day before declining it is costly too. A coordinator spends their afternoon on a patient you won’t serve, and the discharge planner learns your answers come late. Meanwhile, the patient waits in a hospital bed for an answer that was always going to be no.

The financial effect of intake decisions shows up in payer mix. In 2024, freestanding agencies earned a 21.2% margin on traditional Medicare but only 5.0% across all payers. The difference reflects lower margins on patients covered by other payers, and every referral the intake team accepts adds to that mix. Prior authorization adds another risk. Across all services, insurers denied at least 1 in 8 standard prior authorization requests in 2025 in Medicare Advantage and other privately run plans. In home health specifically, many MA plans approve only the first visit or two and can take 7 to 10 days to approve the rest. With MedPAC recommending a 7% cut to the home health base rate, agencies have little room to absorb referrals that turn out to be unprofitable after the patient is admitted.

The goal for intake teams is a correct decision made quickly, whether the answer is yes or no. Reaching that kind of decision depends mostly on what the team already knows when a packet arrives.

Decide the rules before the referral arrives

Most referral decisions are slow because the coordinator has to gather information before they can decide. Organizations that decide quickly settle most of those questions ahead of time:

• Written acceptance criteria for each branch. List the ZIP codes each branch serves, the payers it accepts, the clinical services it offers, and the conditions that require a clinician’s review.
• Capacity that intake can see. Scheduling keeps a daily view of open visit slots by discipline and branch, so a coordinator can tell whether a referral can be staffed without calling the clinical manager.
• Payer rules at the point of decision. Record which plans need prior authorization, how many visits each typically approves up front, and which plans leadership has decided to limit.
• A clear escalation path. Referrals outside the written criteria go to a named clinician with a response deadline, so unusual cases also get a fast answer.

Finally, tell your referral sources what to expect. Set a response standard your branches can meet every time, including weekends, and tell discharge planners what it is. When the answer is no, send it as soon as you know, with the reason, so the planner can find an agency that can take the patient and get them home sooner.

Automate the work that slows the decision

Written rules only help if someone applies them, and today that someone is usually a coordinator working through packets by hand. They read a long faxed referral, re-key demographics and orders into the EHR, log in to a payer portal to check eligibility, and compare what they find against the branch’s criteria. That clerical work takes up most of the time between a packet arriving and a decision, and little of it requires clinical judgment. Hiring more coordinators adds capacity, but each new hire still works through the same manual steps.

Commure Orchestrator takes over those steps. It captures referrals the moment they arrive, whether by fax, portal, EHR, or email, which also starts the decision clock at the right moment. It extracts demographics, clinical notes, payer information, diagnosis codes, and physician orders into structured data, then checks each referral against the rules you’ve written for each branch.

Orchestrator matches the patient’s ZIP code against each branch’s active service area, so an out-of-area referral is flagged before anyone reads the packet. It runs a real-time insurance eligibility check as soon as the referral arrives and scores the payer against your payer scorecard. Low-margin plans and plans with a high risk of prior authorization problems get flagged automatically, which puts the payer mix decision in front of the coordinator before they make the call. Orchestrator also reads the ICD-10 diagnosis codes and scans the clinical notes for keywords that signal acuity, then moves high-acuity patients to the top of the queue.

By the time a coordinator opens a referral, the clerical work is done. Referrals that meet every rule are ready for a fast yes. Referrals that clearly fall outside the criteria are ready for a fast no, with the reason already documented. The unusual cases go into a single queue shared across teams, so the clinician who needs to weigh in sees them without a string of phone calls and emails.

Once a referral is accepted, Orchestrator writes it directly into the EHR, and AI Call Center Agents can contact the patient to schedule the first visit. A faster decision gets the patient out of the hospital sooner, and faster scheduling gets a clinician to their home sooner after that. Because Orchestrator checks eligibility and payer rules before a referral is accepted, each admitted patient also starts with clean payer data, which is where a clean claim begins.

Four numbers for the growth review

With rules behind each referral decision, decision time can be measured and managed like any other growth number. Four measures make it visible:

• Hours from receipt to decision, counted from when the packet first arrives in any channel, before it’s documented as a complete referral.
• Decision time by branch and by referral source, so you can see which branches are slow and which hospital relationships are slipping.
• Expired referrals, where the source placed the patient with another agency before you answered.
• Time to decline, tracked with the same rigor as time to accept.

These measures track growth, and they also track how long patients wait in the hospital for an answer from your agency.

Most organizations can’t produce these numbers today because a manual intake process doesn’t record when a fax landed or how long it sat before someone read it. Commure Orchestrator logs every referral from arrival to decision, so the timestamps behind decision time and time to decline already exist without a coordinator keeping a spreadsheet. Tracking expired referrals takes one more step: recording when a referral source tells you the patient went elsewhere.

Review the measures by branch every month, next to admissions. A branch with slow decisions and flat admissions has an intake problem, and fixing it will likely do more than adding liaison or marketing spend in that market. Pull a sample of expired referrals and walk through each one with the branch team. Each expired referral shows which question took too long to answer, and that points to the rule or process that needs to change.

The discharge planner will keep sending their packets to several agencies. The agencies they rely on will be the ones that answer quickly, yes or no, so the patient can go home. See how Commure Orchestrator shortens the time from first fax to decision.