Automated Patient Outreach for Specialty Referrals: Design the Stop Rules First

Automated patient outreach for specialty referrals should begin with a valid administrative purpose, approved contact rules, current referral status and a staffed handoff path. Recheck those conditions before each attempt, stop pending outreach when the task changes, and record what happened. Measure reached patients and verified scheduling outcomes separately from messages sent or calls attempted.

Define the job of the outreach sequence

Specify one task: help the patient take the next approved administrative step for a particular referral. That might be selecting an appointment, providing an administrative clarification through an approved route, or arranging a staff callback.

Do not combine all three into a generic "engagement" goal. Each has different completion evidence and a different destination for unresolved work.

The sequence belongs to the referral episode, not just a telephone number. A person may have multiple requests, and a repeat transmission should not automatically create another campaign.

Use the referral intake guide to establish the episode and source information before outreach begins. For broader tooling across many patient-access tasks, see AI scheduling and outreach.

The campaign design below is an original proposed operations model. Your organization must supply its approved contact policies, message content, timing and escalation rules.

Create an eligibility check that is evaluated again before sending

At enrollment, record the episode, task, current state, approved contact route, relevant preference information, and assigned owner. Identify any conditions that make the task unavailable for automated outreach.

Examples of administrative checks include whether a booking already exists, a staff callback is in progress, the contact information is unresolved, or the episode has been superseded by an approved change.

Recheck at send time. A list built earlier can become stale. Someone might book through another channel or ask a coordinator to call them back while an automated attempt is pending.

The check should use the most current source available in the configured workflow. If a necessary source is unavailable, define whether the attempt pauses and which owner investigates.

Do not infer permission to contact from the existence of a phone number. This article addresses execution of your approved policy, not the legal policy itself.

Write the stop rules before choosing the cadence

A cadence describes when another attempt might happen. Stop rules describe when it must no longer happen.

These rules must operate across channels. A booking made by phone should stop an unnecessary text sequence for the same scheduling task. A staff callback should not compete with an automated call simply because the two systems use different lists.

Test the timing explicitly. Change the episode state after enrollment but before the scheduled attempt, then verify whether the attempt is suppressed.

Choose channels by the task and approved preference

There is no universal sequence in which every patient should receive a text, then an AI call, then a human call. Use the organization's approved preferences, available communication methods and operational capabilities.

A channel is useful only if the patient can take the next step or reach appropriate support. An invitation to schedule needs a workable booking path or a clear staffed alternative.

Keep the administrative identity of the message clear under your approved template. Avoid adding clinical details or unreviewed explanations of the referral to improve response.

For patients who need a supported language or assistance route, use the approved process. Do not infer a person's preference from age or other demographic assumptions.

A request for communication is not evidence that communication occurred. HL7 makes that distinction in its CommunicationRequest resource.

Apply the same discipline to your operations report: planned, attempted, delivered, interacted and completed are different states.

Design the human handoff as a complete task

A handoff should tell staff what the patient is trying to do, what happened already, and what remains unresolved. Include the referral reference, attempt history, approved responses, current task state and reason for the handoff.

Name the receiving queue and backup coverage. Confirm that the task arrived there. Marking "escalated" in the outreach platform is insufficient if staff cannot find the work.

Give staff a way to pause or take ownership of the sequence. Manual intervention should be recorded in the same operational history so automation can act on the changed state.

Clinical questions should go through the organization's approved clinical escalation process. Administrative outreach should not improvise diagnosis, urgency assessment, coverage advice or treatment instructions.

If your team wants to inspect how this would work, bring an outreach handoff scenario to Linear Health. Ask to see the attempted contact, stopped sequence and receiving task together.

Use a small, reconciled campaign example

Hypothetical outreach exercise: An intake cohort contains 120 unique referral episodes. Before enrollment, 20 have a confirmed booking, 10 need contact-information review, and 10 are assigned to staff under the approved process. The remaining 80 enter the automated scheduling sequence.

The pre-enrollment counts reconcile: 20 + 10 + 10 + 80 = 120. The 40 episodes not enrolled have documented reasons; they are not missing from the report.

By the observation checkpoint, the 80 enrolled episodes are in mutually exclusive states: 40 have a verified booking, 15 are in an active staff callback workflow, 15 have no two-way interaction yet, and 10 have stopped under a documented disposition.

The campaign issued 140 attempts. That is 1.75 attempts per enrolled episode, but it does not mean 140 patients were reached.

Suppose 60 of the 80 episodes recorded at least one two-way interaction. The interaction rate is 75%. Verified booking among enrolled episodes is 40 divided by 80, or 50%. Booking among interacted episodes is 40 divided by 60, or approximately 66.7%.

Keep those denominators visible. A campaign can reach many people while still leaving a difficult scheduling task unresolved.

The report does not attribute every booking to automation. To estimate incremental effect, the team would need an appropriate comparison method and to account for bookings through other channels. This example describes operational accounting only.

Measure the distinction between sent and resolved

Use a short set of measures tied to the task:

• Enrollment eligibility: which episodes qualified and which were excluded, with reasons.
• Two-way interaction: unique episodes with a documented patient interaction.
• Verified task completion: the intended booking or other administrative outcome confirmed in the destination system.
• Unresolved handoffs: staff tasks without an accepted owner or next action.
• Suppression failures: attempts that occurred despite a stop condition.

For scheduling, use the referral-to-appointment conversion guide to define the broader receipt cohort. Campaign conversion and whole-cohort conversion answer different questions.

For attendance after booking, use reducing specialty-clinic no-shows. Do not count a booked appointment as an attended visit.

Review failure reasons alongside the totals. A low completion rate may reflect unavailable appointments, unclear messages, contact-data problems or a handoff queue that is not being worked. Sending more attempts does not diagnose those problems.

Test collisions before increasing volume

Use synthetic episodes to test what happens when human and automated actions occur close together.

Create an enrolled episode, have a scheduler book it, and let the pending attempt reach its planned send time. Verify suppression and record the booking reference.

Create another episode, allow an automated attempt, then have the patient request a callback through a different supported channel. Confirm that the receiving task exists and that overlapping attempts pause according to the approved rule.

Test an invalid contact route, an unavailable booking system, an exhausted attempt sequence, and a changed referral. For each, write the expected owner and resulting state in advance.

Also test recovery. When a held dependency becomes available, the system should reconsider current eligibility rather than blindly replay every previously planned attempt.

The useful output is a passed or failed operational test with evidence, not a reassuring conversation recording.

Launch with staffed recovery and visible ownership

Choose a defined cohort whose task, data and receiving team are ready. Limit the release to what your staff can monitor and support.

During evaluation, keep one production actor responsible for each attempt. A shadow comparison can inspect what another workflow would do without independently contacting the same patient.

Review unresolved handoffs and suppression failures promptly through your approved operational process. Keep a named person able to pause the sequence and route the held work.

Change one element at a time where practical. If you alter message content, eligibility, timing and booking availability together, a later improvement will be harder to explain.

For a broader view of the workflow, explore referral coordination software. Book an outreach design discussion with the eligibility worksheet and the collision tests you want to observe.

FAQ

Sources

• HL7 FHIR R4 CommunicationRequest, distinction between a request to communicate and communication activity. The campaign design and the reconciled example in this article are original editorial tools.