Sources and review notes
These links support definition-level research and do not establish the regulatory status, safety, or suitability of any product.
AHRQ's patient-safety summary of the ambulatory referral guide describes a referral as a multi-step process from the initial order through communication of the treatment plan to patients and families, and highlights standardized handoffs, interoperability, clear follow-up accountability, and patient communication. ONC's 2025 SAFER materials recommend reliable EHR-based clinician communication for referrals and care transitions, patient-level status tracking, necessary information exchange, proactive risk assessment, and explicit follow-up responsibility; these are recommended safety practices rather than certification of a product or guarantee of a safe outcome. CMS's Closing the Referral Loop eCQM measures whether the referring clinician receives a report from the clinician to whom the patient was referred, using a specific measure version and logic. Receipt of that report is one process measure and does not by itself establish that the referral was clinically appropriate, authorized, scheduled, attended, reconciled, communicated to the patient, or acted on. CMS's interoperability and prior-authorization final rule applies to specified impacted payers and non-drug items and services, with operational and API dates that vary; it should not be generalized to every payer, drug authorization, referral, or jurisdiction. The ONC Interoperability Standards Platform identifies standards and implementation approaches for referral care coordination, but standards availability does not prove that two organizations exchange complete, timely, correctly matched, or actionable information. A referral workflow should identify the requesting clinician, clinical question and urgency, receiving specialty or service, patient identity and preferences, destination selection, required records, coverage and authorization dependencies, scheduling responsibility, expected response, follow-up owner, escalation clock, and closure criteria before automation. Statuses should be explicit and non-overlapping, such as ordered, clinically reviewed, patient informed, sent, received, accepted or redirected, authorization pending, ready to schedule, scheduled, attended, report pending, report received, reconciled, patient notified, care plan updated, closed, and closed incomplete, with timestamps and reason codes. Automation may extract documents, check required fields, route queues, send permitted reminders, reconcile acknowledgements, and surface aging, but it should not infer urgency, specialty appropriateness, patient consent, medical necessity, denial response, or clinical closure without qualified review. Teams should preserve the original order and attachments, source and destination identifiers, transport and acknowledgement records, document versions, authorization reference, outreach attempts and channel, patient response, appointment and attendance evidence, consultant report linkage, clinician review, patient communication, actions taken, exceptions, overrides, and final rationale. Testing should include urgent and routine referrals, wrong or unavailable destinations, duplicate patients, multiple referrals on the same day, missing documents, external organizations, language and accessibility needs, patient refusal or unreachable status, payer changes, authorization delays or denials, cancellations, no-shows, report mismatches, source outages, and staff turnover. Metrics should distinguish order-to-send, receipt acknowledgement, acceptance, authorization, scheduling, attendance, report receipt, clinical reconciliation, patient notification, complete and incomplete closure, aging and escalation, leakage reason, duplicate and misrouted referrals, false automated matches, staff work, and results by site and relevant patient strata. Buyers should verify directory freshness, interface and fax failure handling, role-based access, minimum necessary data flow, message and document integrity, audit logs, downtime procedures, vendor and subcontractor roles, retention, export, support, and exit continuity. A closed status, high completion rate, standards-based interface, or automation claim must not be treated as evidence of clinical appropriateness, safety, coverage, compliance, equity, or improved outcomes without case-level validation and accountable human review.
