All Articles

Linear Health vs ReferralPoint: Compare Outbound Referral Workflows

Compare Linear Health and ReferralPoint by separating destination selection, transmission, returned status and staff follow-up with an outbound evidence worksheet.

A miniature evaluator compares two neutral outbound-referral models and their return-status cards.
A miniature evaluator compares two neutral outbound-referral models and their return-status cards.

This is a Linear Health comparison based on public material checked on October 22, 2026. It does not report independent product tests.

Separate destination discovery from ongoing outbound work

An outbound referral has two different jobs. The first is choosing where the referral goes. The second is everything after the choice: transmitting the packet, confirming receipt, learning whether the patient was scheduled and seen, retrieving the note, and recording a status your team trusts.

A destination-selection demonstration does not establish what happens after the referral is sent. Keep follow-up effort visible in its own part of the evaluation. When you compare Linear Health and ReferralPoint, keep the two jobs in separate columns so a strong matching demo does not stand in for follow-through evidence. The companion article on outbound referral management covers the full outbound lifecycle in more depth.

What each vendor documents about referral routing and follow-through

ReferralPoint, as described on its public site

ReferralPoint markets outbound and inbound referral automation. For outbound, it claims a specialist-matching step it calls IdealMATCH, which it says selects an in-network specialist using cost, quality and patient-need criteria; prior authorization submission from inside the referral flow; automated scheduling and patient outreach; and closed-loop tracking back into the referring EHR. The site lists several connection routes and distinguishes parent-company reach from ReferralPoint-specific listings. In particular, its Epic listing is described as a showroom connection via its parent. Ask which connection and actions are included for your organization rather than treating every logo as the same integration. These are vendor claims from referralpoint.ai. The site also presents customer metrics and case-study figures; this article does not repeat them because they cannot be checked from the public page.

Linear Health

Linear Health provides operational AI for healthcare, including referral coordination. Its stated pricing starts from $2,000 a month, as a flat fee per workflow sized to volume; monthly billing begins when the workflow is live and processing real work. Established integrations are athenahealth, eClinicalWorks, NextGen and Greenway Health. The referral coordination page provides the broader scope.

For this comparison, request a demonstration of destination selection, outbound record updates and any submission or status-tracking steps in the proposed workflow. The public material reviewed for this comparison does not establish that Linear offers a matching feature equivalent to ReferralPoint's IdealMATCH. That is an open scope question, not proof a feature is absent.

Where the overlap is meaningful

Both identify connections involving athenahealth, eClinicalWorks and NextGen. That gives a buyer a starting point, not proof of equivalent outbound actions. Ask which records and fields each proposal changes, which events trigger those changes and how the team handles a failed update.

Compare the evidence returned after a referral is sent

After transmission, what comes back, where is it recorded and who follows up when nothing comes back? Use the same evidence sheet for both vendors. The columns below distinguish the required result from the proof received.

StepResult to defineEvidence receivedOpen question and owner
Destination selectionApproved destination chosen or reviewedSelection explanation and supported correction path
Packet preparationRequired administrative items accounted forSource-to-packet trace and missing-item record
TransmissionPacket sent through the agreed channelDelivery event with destination and time
ReceiptReceiving office acknowledgement, when in scopeSeparate acknowledgement source
SchedulingAppointment state established or still unknownDated status source and EHR record
Follow-upUnanswered request assigned for actionVisible next action and responsible team
Returned noteDocument received and matched, when in scopeDocument provenance and matching evidence
Outbound referral evidence sheet. Template rows to complete for each vendor, not findings.

Record transmission and receipt separately. Keep booked, attended, note received and unknown distinct as well. A successful send is not evidence of attendance, and a missing note is not evidence the visit did not occur.

The Operational AI Evaluation Kit distinguishes not addressed, claimed, demonstrated and verified evidence. Apply that scale to your agreed endpoint. A delivery log may demonstrate transmission without proving the receiving office acknowledged the packet. Do not require every workflow to retrieve a note if that is outside the agreed scope; make the boundary visible instead.

Test the EHR record, unknown status and missing note

Use one synthetic referral with both vendors. First inspect the EHR record after transmission. Identify which fields changed and the source of each new value. Ask the team to demonstrate the supported correction path rather than assuming every action is reversible.

Next, withhold a receiving-office response. At a follow-up interval chosen for the evaluation, inspect the unresolved state, next action and owner. The test asks whether unknown work remains visible; it does not prescribe a clinical follow-up deadline.

Finally, supply an attendance confirmation but no consult note. If note retrieval is included in the proposal, inspect the open request and what happens when a document arrives that cannot be matched confidently. If retrieval is excluded, record who owns it outside the system.

Worked example: two different evidence gaps

In this synthetic exercise, Vendor A demonstrates the transmission log but only describes how staff handle unknown status. Vendor B demonstrates that unresolved queue but only describes note retrieval. Record A's unknown-status path and B's note-retrieval path as separate evidence requests. Neither is a measured customer result or an automatic failure of the entire product.

Before another demo, the buyer decides whether each disputed action is required for this deployment. For required actions, request the missing proof. For excluded actions, identify the retained owner. This produces a useful next decision without hiding a critical gap inside an average score.

Make the decision with an outbound workflow evidence table

Follow this sequence, which is proposed editorial method rather than a measured process:

  1. Complete the table for each vendor using the same test referral and the same three exception cases.
  2. Treat privacy, security, authorization and accountability gaps as gates, as the evaluation kit specifies; a high total does not offset them.
  3. Keep recurring fees, implementation expense and staff capacity separate. A baseline alone does not turn released hours into cash; identify which expense will change.
  4. Record every row scored 0 or 1 as an open evidence request with an owner and a date.
  5. Set acceptance evidence for the actions your deployment requires. Document any condition that prevents proceeding and any work deliberately retained by your team.

If you want to see how Linear Health handles the status-return and exception rows in your own EHR, you can book a demo and bring this table. Ask ReferralPoint for the same walk-through so the evidence is comparable. The broader context for this method lives on the referral coordination software page.

Frequently asked questions

Does ReferralPoint describe inbound as well as outbound referrals?

Yes. Its public site advertises an outbound workflow for sending practices and an inbound workflow for receiving practices. Treat those descriptions as vendor claims to verify for the proposed deployment.

Does Linear offer the same destination matching as IdealMATCH?

The reviewed sources do not establish an equivalent matching feature. Ask Linear to demonstrate the proposed destination-selection scope and record any work retained by your team.

Can EHR logos settle the integration comparison?

No. Inspect the exact connection and actions. ReferralPoint's page distinguishes some parent-company reach from its own listings, including an Epic showroom reference via its parent. Verify the route relevant to your EHR.

Does closed loop always mean a consult note was returned?

Define the endpoint before scoring it. Transmission, acknowledgement, booking, attendance and note receipt are separate events. Evaluate the specific endpoint and evidence included in the proposal.

What does Linear Health cost?

Pricing starts from $2,000 a month, with a flat monthly fee per workflow sized to volume. Monthly fees begin when the workflow is live and processing real work. Obtain a matched-scope proposal from each vendor before comparing cost.

Sources

Linear Health Editorial Team
Editorial, Linear Health

Linear Health publishes educational articles about operational AI for healthcare.

Share this article