Referral Management Software Buyer Guide: From Requirements to a Decision
Turn your referral workflow into software requirements before booking demos. Identify which work must move, who owns exceptions and what evidence will support the decision.

Step 1: Write the problem and its completion boundary
A request such as "we need better referral tracking" leaves several different problems open. It might mean inbound packets go missing, follow-up is unassigned, status updates are inconsistent, or a returned specialist note is hard to find. Those needs may require different changes. Establish the requirement before deciding whether a dashboard, a workflow change or another tool addresses it.
Use one sentence to force specificity: "We need the person responsible for [task] to complete [action], using [information], with [evidence] visible to [next owner]." If the team cannot fill it in, observe the current work before buying anything. The referral management process guide walks through mapping those handoffs before technology enters the conversation.
Then define the completion boundary: the action, the system where its result appears and the person who can verify it. A request capture tool may legitimately finish with a staff task. A booking workflow needs a different result. The concern is a mismatch between the promised outcome and the demonstrated one. Linear Health's Operational AI Evaluation Kit provides questions for making that distinction.
A hypothetical specialty practice might write: "We need the intake coordinator to identify an incomplete inbound referral, request the missing item, and show the receiving team who owns follow-up until the packet is complete." That is a requirement about unfinished administrative work. It does not ask software to make a clinical decision or choose the missing documentation without local instructions.
Step 2: Separate mandatory requirements from preferences
Classify requirements before scoring vendors. For each proposed launch requirement, record why it matters and who can accept the evidence. Some requirements come from the workflow; others come from the organization's designated governance reviewers. An unanswered requirement is not automatically a preference simply because the project team cannot yet explain it.
A useful test is to ask three questions of each line item:
- Which handoff breaks if this is absent?
- Who notices, and how quickly?
- What would staff do by hand in the meantime, and is that acceptable for the first workflow?
Also look inside vague items. "Send status updates" hides at least three different requirements: the coordinator can see whether the destination acknowledged receipt, the sending office can tell a booked appointment from a completed visit, and a failed update creates a task someone can find and resolve. Each needs its own demonstration. One screen showing a green status does not establish all three.
Some requirements are not yours to settle in a workflow review. The Evaluation Kit treats privacy, security, safety, authorization and accountability issues as gates that a high score cannot offset, and routes them to the responsible reviewer. Keep those lines on the list, but assign them to security, legal or compliance owners rather than scoring them from a demo.
The decision record, one page
This worksheet is an original format offered as editorial guidance. The example is hypothetical, not a customer implementation or a claim about any product.
| Field | What to record | Hypothetical example |
|---|---|---|
| Need | The work that must become possible | Follow up on an incomplete inbound referral |
| Current owner | Who handles it today | Intake coordinator |
| Observed problem | A specific event in the current process | Missing-item requests are stored outside the shared queue |
| Completion evidence | What the next person can observe | Missing item, request history and responsible person appear together |
| Demonstration evidence | What the vendor must show | Process an incomplete packet and reopen the assigned task |
| Decision owner | Who can accept the result | Referral operations lead |
| Priority | Launch requirement or later preference | Required for the first workflow |
| Unresolved dependency | What still needs another team's decision | Which EHR location holds the final record |
Do not fill an unknown field with an optimistic assumption. An unresolved dependency tells the project team which conversation has to happen before a requirement counts as feasible.
Step 3: Collect comparable demonstration evidence
Vendors prepare their own demonstrations around their strongest cases. Comparable evidence comes from your scenario, shown to every vendor the same way. The Evaluation Kit recommends one representative case with normal complexity, missing data and at least one exception, and notes that a scripted happy path is not enough.
Ask for evidence suited to each question. For workflow behavior, request the agreed scenario end to end. For data exchange, ask which fields are read, created, updated and returned to each system of record, and how a failed write is exposed and recovered. For commercial scope, rely on the written proposal rather than a spoken assurance.
Record one of four outcomes beside each requirement, mirroring the Kit's scale: not addressed, claimed, demonstrated, or verified in production. Keep the reason. A "claimed" answer may be acceptable during discovery, but it must not silently become a pass when the shortlist is reviewed.
Integration deserves particular care. Linear Health lists athenahealth, eClinicalWorks, NextGen and Greenway Health as established EHR integrations. An integration logo does not tell you which fields move, in which direction, or where staff see a failed transfer. Ask every vendor to demonstrate field-level behavior against your configuration rather than inferring it.
If you want to test this against a working example, book a Linear Health demo and bring synthetic versions of one complete administrative case and one exception. Keep the test close to your actual workflow while using an approved demonstration environment.
Step 4: Document retained staff work and costs
Ask each vendor to identify the work your team will retain. Linear Health's stated scope is up to 80% of coordination work automated, with the team staying in the loop on the remainder. That ceiling is not evidence of the share your organization will automate. Follow the proposed workflow through its exceptions and document the staff tasks you observe.
Follow one exception until a named person has enough information to act. Who receives it? Can they see previous attempts? What happens if that person is out? Which system records the resolution? Use bounded administrative examples: a destination does not acknowledge receipt, a contact field is inconsistent, or the record is already being worked by another coordinator.
A retained-work ledger
Keep these four types of entry separate so staff capacity is not double-counted as cash:
| Item | Example entry (illustrative) |
|---|---|
| Staff work retained | Exception review, clinical questions routed to providers, policy decisions |
| Internal implementation effort | Configuration decisions, training time, an owner for the dependency register |
| Recurring vendor cost | Linear Health states pricing from $2,000 a month as a flat fee per workflow, sized to volume, with no monthly charge until the workflow is live and processing real work. Confirm your own figure in a written proposal. |
| Projected contribution | Record separately, with baseline period, denominator and data source |
The Evaluation Kit asks buyers to separate activity metrics from operational outcomes and financial assumptions, and to treat a business case built on a percentage or customer result without its scope and denominator as a red flag. Apply that to every vendor's numbers. Linear Health's proposal target of 3x or better is a vendor-stated build target, not a measured result for your organization.
Step 5: Make a decision with named unresolved conditions
Name the decision being made. Advancing a vendor to a local test is different from signing a contract or authorizing production use. The decision record should state the permitted next step, the evidence supporting it, the remaining conditions and who can close them.
Use three explicit outcomes: proceed to the named next step, hold for specified evidence, or decline because the proposed scope does not fit. An owner and a target date make an open condition trackable; they do not resolve it. Required gates must be satisfied before the action they govern.
At this point the earlier tools apply. Use the category comparison to confirm you compared like with like, and the RFP template if you need structured written responses on the open items. Linear Health's referral coordination automation runs on top of an existing EHR; the fair question for it, as for any option, is which documented handoffs it supports, which need configuration, and which stay with staff.
A practical evaluation method
This sequence is editorial guidance, not a measured procedure.
- Pick one referral journey and write the problem sentence and completion boundary.
- Build the one-page decision record for the handoffs that determine the purchase.
- Mark each line launch or later, with a reason and an owner.
- Give every shortlisted vendor the same scenario with missing data and one exception.
- Score each requirement as not addressed, claimed, demonstrated or verified, and send gate items to their reviewers.
- Fill the retained-work ledger before reading any savings projection.
- Record the authorized next step, its evidence and the conditions that still block later commitments.
Bring one workflow to the demonstration
You do not need a perfect requirements document to start. You need a specific task, an owner and a way to judge the answer. Book a demo to walk through that task with Linear Health and see which steps it handles, which need configuration and which stay with your team.
Frequently asked questions
What should we define before comparing referral software?
How does a requirement differ from a feature request?
Which capabilities need a live demonstration?
Who should own the requirements?
Can we decide before every question is answered?
Sources

Sami founded Linear Health after spending a decade at the intersection of clinical operations and scaled healthcare technology. Connect on LinkedIn.


