Champ AI
November 20, 2026

athenaOne Referral Triage: Automating Untethered Referrals

Turn untethered referrals in athenaOne into prepared patient records. Automate patient matching, registration, insurance entry, and routing, with clear follow-up for missing information.

Jagannath Putrevu
Jagannath PutrevuCo-Founder & CEO

Untethered referral triage in athenaOne can be automated by reading incoming documents, matching or registering patients, entering available insurance information, and routing referrals using the practice's rules. The result is a referral attached to the correct chart and delivered to the staff who can take the next step.

For referral coordinators and patient-access teams, the manual work starts when a fax arrives without a patient attached. Someone must read the pages, search the EHR, complete registration details, and decide where the document belongs. Those administrative steps can repeat for every incoming referral.

Automation can complete that preparation and identify unresolved questions. Staff receive the referral with its patient record and routing information in place, or a specific explanation of what needs attention.

What is an untethered referral?

Here, an untethered referral means an incoming referral document that has not yet been attached to a patient record. The document has arrived, but the receiving team still needs to identify the patient and prepare it for the appropriate staff.

athenahealth's admin-document documentation describes administrative documents that can exist without a patient ID. It also identifies incoming outside-provider referrals and supporting documents under the Admin - Referral category.

Receiving a referral document and completing its intake are separate steps. The exact inbox, status names, and routing configuration depend on the practice.

The work between fax receipt and a usable referral

Consider a referral containing patient demographics, an insurance section, the referring clinician's details, and a request for a specialty appointment. The receiving staff member may need to move between the document, patient search, registration, and routing screens.

Staff identify the requested specialty, check for an existing chart, and add the information needed for the next step. Staff may also need to find the referring provider, write an internal note, and request an insurance card or missing records.

Automation can carry those steps through the EHR using the practice's matching and routing rules. The broader referral intake automation guide covers intake across faxes, email, and portals. This workflow focuses on referrals already received in athenaOne that still need that preparation.

How to automate referral triage in athenaOne

1. Read and classify the incoming document

First, identify whether the document is a referral, supporting material, a records request, or another kind of correspondence. Those documents need different actions.

For a referral, extract the information actually present: patient identifiers and contact details, payer information, the requested specialty, the referring provider, and the stated referral reason. Preserve any urgency explicitly written by the referring clinician for the practice's review process.

Extraction should make missing or unreadable information visible. It should not fill gaps with plausible values.

2. Match the referral to the correct patient

Search the existing records using the identifiers on the referral. A practice might begin with name and date of birth, then compare other available details under its matching policy.

ASTP/ONC's transitions-of-care certification guidance lists full name, date of birth, address, and phone information among patient-matching data in structured referral summaries. The practice defines how to compare those fields and establish a confirmed match.

A confirmed match can be attached to the referral. Multiple plausible matches or conflicting identifiers should come back with the reason for review.

3. Create a chart when registration is needed

When the practice's search process confirms a new patient and the required information is available, the workflow can create the patient record and enter the supplied demographics.

Before creating it, check that the referral has not already been processed and that the matching process has been completed. If required registration details are missing, request them or leave a clear task for staff.

4. Enter available insurance details

The workflow can enter the payer, member identifier, group information, and other supplied details using the practice's insurance-entry rules.

A missing member ID calls for follow-up under that process. It does not, by itself, establish that the patient is uninsured or should be treated as self-pay. The request for the missing card or identifier should remain visible with the referral.

5. Apply the practice's routing rules

Use the requested specialty and the practice's approved mappings to select the destination department, provider, or staff group. Keep the referring provider separate from the receiving provider.

The rules should say what to do when the referral names a particular clinician, requests a specialty without naming one, or lacks a usable destination. Applying those rules automates administrative routing while preserving clinical review where needed.

6. Finish the document and confirm the result

Attach the patient record, complete the applicable fields, and add a concise internal note. The note should describe the preparation completed and any information still required.

Then send the document to the configured destination and confirm that the attachment and routing changes were saved. Staff can open the referral with the information needed to continue.

Handle incomplete referrals with a specific next step

An ambiguous match needs a different response from a missing insurance card. An unreadable page needs a document request, while a records-release request belongs in the practice's records process.

For each exception, preserve what was found and state what remains unresolved. Examples include conflicting demographic details, a missing member identifier, or an unclear destination. This lets staff resolve the question without rereading the entire packet to discover it.

Where the process calls for outreach, automation can request information from the referring office and bring the response back to the referral. Phone follow-up can support that work when the document or portal does not provide an answer.

Define what ready for scheduling means

A triaged referral should have a confirmed patient record, the required administrative information, and the correct destination. Any remaining clinical review, authorization, or scheduling requirement should be visible.

The receiving team can then act on a prepared referral. For one practice, that may mean contacting the patient. For another, a specialist must first review the request.

Start by validating the workflow against the referral types your practice receives. Check patient matching, new registration, insurance entry, and routing results before expanding automation. Measure how many referrals reach the intended destination with complete information and how many still require a specific follow-up.

Frequently asked questions

Can untethered referrals in athenaOne be triaged automatically?

The administrative steps can be automated using the practice's rules: document reading, patient matching, registration, insurance entry, and routing. Ambiguous or incomplete referrals can be returned with the information needed for review.

Can automation create a patient chart from a referral fax?

Yes, when the matching process establishes that registration is needed and the required information is available. The workflow should complete the practice's search and duplicate checks before creating the record.

What happens if several patient records could match?

The referral should remain unresolved until the identity question is settled. Staff should receive the conflicting details and the reason the workflow could not establish a match.

What if the referral is missing insurance information?

Request the missing information according to the practice's process and keep that request with the referral. A missing member ID should not automatically determine the patient's financial classification.

Does this require a custom athenaOne API integration?

Browser automation can perform administrative steps through the screens staff already use, with appropriate access. Available API capabilities are another option; the right approach depends on the workflow and practice configuration.

Does referral triage automation decide clinical urgency?

Administrative automation can preserve urgency stated in the referral and apply approved routing instructions. Decisions that require clinical judgment stay within the practice's clinical review process.

Still triaging referral faxes by hand?

Champ can automate the document reading and browser work behind this intake, with phone follow-up when information is missing. We set it up and run it, so your team receives prepared referrals and clear exceptions in its existing workflow.

For more examples, see our athenaOne automation guide. To walk through your referral-triage process, learn more here.

This post is general information about administrative workflows. Confirm patient-matching, routing, and review rules with your practice's athenaOne administrator and clinical leadership. Champ is not affiliated with or endorsed by athenahealth.

Continue reading

See all

Do the work of fifty
without hiring one more.

Eligibility
Verification
Claims
Payroll
Carrier check-in
Patient intake
Benefits
Credentialing
Credentialing