The phrase “referral management software” covers several different product categories. A practice trying to organize incoming referral documents does not have the same requirement as a health system coordinating referrals across a provider network. Shortlisting begins with the workflow, not the broad category label.
Separate the product categories
| Category | Primary job | Question to ask |
|---|---|---|
| Specialty intake and triage | Recommend and support an inbound referral action | How are the recommendation, evidence and human approval handled? |
| Referral network management | Route and track referrals between providers | Is the workflow inbound, outbound or both? |
| Patient access platform | Coordinate scheduling and access | How deeply does it support clinical review? |
| Fax or document automation | Receive, classify or extract documents | What operational workflow follows extraction? |
Ten criteria that reveal real fit
- Problem fit: Does the product solve the actual inbound or outbound referral problem?
- Next-action support: Does it produce a clear recommended action rather than stopping at extraction or summary?
- Human control: Can authorized users verify, refine, escalate and approve the action?
- Source visibility: Can the reviewer see the evidence behind it and return to the referral source?
- Exception handling: What happens with poor scans, contradictions and missing information?
- Queue operations: Are status, ownership and unresolved work visible?
- Integration options: Can the team start directly, and what is required for e-fax or EHR connectivity?
- Security and privacy: Can the vendor support the organization’s privacy and security evaluation?
- Implementation effort: What can begin immediately and what requires customer-specific work?
- Proof and measurement: Which baseline and outcome measures will be used?
Compare pricing in the context of implementation
A seat price is only useful when the buyer knows what the seat can do and what is included. Ask whether intake users and approvers are priced differently, whether implementation is separate, whether integrations carry additional cost and whether there is a minimum contract. Review Elvra’s current structure on the dedicated pricing page.
Understand the market map
Products in this market are not interchangeable. Some focus on inbound specialty review, some on patient access or network routing, some on document transport, and others provide referral functions inside a broader EHR platform. Compare each option against the category and workflow you actually need rather than relying on a shared label.
What to look for in a demonstration
Ask the vendor to show one representative referral from receipt through an approved action. Look for the recommendation, the evidence behind it, the original source, ownership, exceptions, human approval and downstream handoff. Avoid relying on a feature list that never demonstrates how the work fits together.
How to evaluate AI-assisted referral review
Ask what action the AI recommends, who verifies it, how users return to the supporting source, what happens when the model is uncertain and how the authorized team approves the action. The NIST AI Risk Management Framework Core offers general guidance on governance, oversight and accountability; it is not evidence that any product is clinically effective.
Where Elvra fits
Elvra focuses on complex incoming specialty referrals. It combines flexible document intake, a recommended next action, editable source-linked reasoning, queue ownership and authorized human approval. Practices can start without integration; health systems can add customer-specific e-fax, EHR, identity and rollout scope.