Specialty referral workflows vary, but the same operational gaps appear repeatedly: documents arrive without a complete history, information must be reconstructed, ownership changes and the downstream system does not show why a referral is waiting. This seven-stage model is a practical way to map those gaps. It describes work that must happen, not seven mandatory people or software screens.
Seven practical stages
1. Receive the referral
Capture the incoming package through direct upload, e-fax or an EHR-connected path. Associate typed documents, handwritten notes and later-arriving information with the same referral.
2. Assemble and identify
Keep the referral form, notes, reports and related documents together. Confirm patient and referral identity using the organization’s approved process.
3. Check completeness
Compare the package with the required information. Missing tests, radiology reports or relevant history should become explicit work rather than an informal note in an inbox.
4. Prepare a source-linked recommendation
Identify information relevant to the referral indication and suggest what should happen next. The recommended action might be urgent booking, a routine consultation, a request for missing information or routing to another service or physician. An editable, source-linked draft shows the findings and reasoning.
5. Review and decide
An authorized person compares the recommendation with the source, resolves ambiguity and approves the action under local policy.
6. Hand off the approved action
Move the referral into booking, follow-up, redirection or another agreed downstream workflow. Keep the destination, discussion, acknowledgement and exception path attached to the referral.
7. Monitor the queue
Track ownership, status, age, unresolved information and completion. Monitoring supports daily operations and creates the baseline needed to evaluate changes.
Map functions, then assign roles
Roles may be combined. In a smaller practice, one authorized nurse or medical assistant may interpret, review and decide in a single interaction. A larger organization may separate intake, clinical review, approval and booking across teams or sites. The important requirement is that responsibility, discussion and context remain visible when work changes hands.
Decide how much integration is necessary
A direct intake workflow can be the right first step when the immediate problem is document review and queue coordination. E-fax intake can reduce manual delivery. EHR or SMART on FHIR integration can reduce duplicate entry or connect downstream actions. Each layer should solve a defined problem rather than becoming a prerequisite by default.
For technical teams, the HL7 FHIR overview provides the standard’s official context, while the SMART Health IT documentation describes app-launch and authorization patterns used in SMART on FHIR environments.
Measure progress
Choose operational measures that correspond to the workflow: time to first review, queue age, time waiting for missing information, reviewer time, time to an approved action and percentage of referrals reaching the intended handoff.
Questions to ask in workflow discovery
- Where do referrals arrive today?
- What information is required before review?
- Who can review the recommendation and approve the action?
- What happens when information is missing or contradictory?
- Which system owns the approved action?
- How are discussions and failed handoffs preserved?
- Which metric would demonstrate a useful operational improvement?
Continue the evaluation
Read what referral triage means in specialty care, compare software categories in the buyer’s guide, or see how Elvra keeps ownership and status visible.