Solutions / Referral intake

Referral intake automation for matched, complete, routed work

Process referral documents, match the patient and referring provider, check service-line completeness, and route the next intake step.

VoiceAdminHealthcare operations infrastructure

Referral, intake, scheduling, eligibility, prior authorization, and specialty operations teams handling fragmented referral documents.

A referral matched to the correct patient, referring provider, service line, and record, with completeness status and the next work queue kept together.

Referral intake built around completed work.

Referral intake automation handles the intake stage of referral management. It turns faxes, portal PDFs, scans, uploads, and supporting documents into matched, complete, routed work.

  • Referral fax, portal PDF, scan, and upload intake
  • Healthcare OCR and structured field extraction
  • Patient, referring provider, referral, and account matching
  • Service-line completeness checks
  • Scheduling, eligibility, prior authorization, missing-item, and human-review routing

Start with one service line and representative documents. Validate classification, extraction, matching, completeness, duplicate handling, routing, and exception review against the intake team standard.

What to evaluate

How does the workflow avoid a wrong patient or referring provider match?

Define required identifiers, confidence rules, conflicting-data handling, and review conditions before any document attaches to a record.

Can it identify an incomplete referral?

The workflow uses configured service-line rules for required orders, notes, diagnosis, authorization, demographics, insurance, and supporting material.

What happens after intake?

A configured handoff can route the matched referral to scheduling, eligibility, prior authorization, missing-item follow-up, or human review. Broader lifecycle scope is confirmed separately.

Common workflows and use cases clients automate

Your dedicated project manager learns your workflow, then works with a forward-deployed engineer to customize the agents around your questions, channels, and handoffs.

Match the referral, check completeness, then route the next work.

This example follows an intake case from source documents through the configured handoff.

Example inputReferral documents to the next intake queue
  • Referral fax or portal PDF
  • Patient and referring provider
  • Service line
  • Supporting clinical documents
  1. 01 / decision

    Can the patient and referring provider be matched?

    Yes

    Check completeness against the service-line intake rules

    No

    Route the source and match evidence to human review

  2. 02 / decision

    Is the referral complete for this service line?

    Yes

    Select the configured operational destination

    No

    Route the named missing items to missing-item follow-up

  3. 03 / decision

    Is scheduling the next step?

    Yes

    Route the complete referral to scheduling

    No

    Route to eligibility or prior authorization based on the configured requirement

Structured resultWhat your team gets back
  • Destination queue
  • Routing reason
  • Match status
  • Completeness status
  • Missing items
  • Source evidence

A defined workflow contract.

The intake result can hand work to scheduling, eligibility, prior authorization, missing-item follow-up, system write-back, or human review when that handoff is configured.

  • Referral fax, portal PDF, scan, upload, or supporting document
  • Required fields and service-line completeness rules
  • Patient, referring provider, referral, and account matching data
  • Routing, missing-item follow-up, and exception policy
  • Referral classification and structured fields
  • Patient, referring provider, and record match status
  • Completeness and missing-item status
  • Destination queue, source evidence, and next action

The result includes the context behind it.

01Source linked

The original referral and extracted evidence remain attached to the structured intake record.

02Completeness visible

Missing fields and supporting documents become named follow-up items.

03Routing explained

The result records the match, completeness decision, destination, and reason for any exception.

Scope is explicit before work goes live.

Covers intake through configured handoff. Downstream lifecycle tracking is scoped separately.

Frequently asked questions

What part of referral management does VoiceAdmin cover?

This page covers the intake stage: document processing, patient and referring provider matching, completeness checks, routing, and configured missing-item follow-up.

Can VoiceAdmin process faxed referrals?

Yes. Configured workflows can classify faxed referrals, extract fields, attempt the record match, identify missing items, and route the intake or exception.

Does VoiceAdmin replace clinical referral review?

No. Administrative intake can be automated, while clinical review and decisions remain with the authorized care team.

Bring one real workflow. We will map the inputs, channel path, result, and exceptions with your team.

Book a demo