Skip to main content
Dialysis ride logistics

Recurring dialysis transportation from the clinical workflow

VectorCare is the coordination layer for a prescribed, repeating dialysis ride. Staff place a standing order from the clinical workflow. They rebook the return when the session runs long. Status stays on the record. VectorCare does not run vehicles. It does not replace the dialysis EHR.

What it is

Dialysis ride coordination, not a transport company

A dialysis ride is a prescribed trip that repeats. The clinician sets the days. The clinic still has to get the patient to the chair and home again.

Many dialysis records do not schedule that ride. Staff book it by phone and by fax. The ride then lives outside the record. The floor cannot see it.

VectorCare turns that work into one order. Staff build the order from the clinical workflow. Contracted vendors receive it. The care team sees status until the trip is done.

This is the same rails hospitals use for hospital patient transportation software. It is patient logistics for a repeating ride, not a new clinical system.

  • A coordination layer

    Staff place the standing order, send it to vendors, and track it. One system holds the request. Where the record supports SMART on FHIR, staff open the order from the chart. Where it does not, staff still place the order on VectorCare.

  • Not a broker

    The clinic or the hospital contracts with its providers. VectorCare does not take the trip and subcontract it. A broker may still run as one provider in the network. VectorCare is not that broker.

  • Not vehicles and not the dialysis EHR

    VectorCare does not operate vans or ambulances. It does not replace the dialysis record. It sits between the workflow and the vendor network. It can read status from a provider dispatch system. It does not become the clinical chart.

The problem

The chair is lost before anyone can use it

Clinics still book a prescribed, repeating dialysis ride by phone and by fax. Then the plan breaks in one of two ways. The patient arrives late, and the chair is gone. Or the crew arrives before treatment is over, and the return fails.

The session length is not fixed. A late start moves the end time. The ride home was booked for the old end time. Staff call the vendor again. The patient waits. The next chair waits too.

Discharge planning can start this ride. A patient who leaves the hospital on a standing order still needs that order tracked. See hospital discharge transport delays.

The loss is not a missing fleet. VectorCare does not add vehicles.

The loss is the empty chair, the crew that arrives too early, and the staff time on the phone and the fax.

You do not fix this by replacing the dialysis EHR. You close the gap between the prescribed ride and the vendor who runs it.

How it works

From the standing order to the ride home, without the phone tree

1

Place the standing order from the workflow

Staff start from the clinical workflow. The order carries the patient, the level of service, the pickup, the clinic, and the days the clinician prescribed. Where SMART on FHIR is available, staff launch from the chart and do not retype the demographics. See it in the EHR.

2

Send the ride to contracted vendors

A.D.I. (Automated Dispatching Intelligence) sends the request to providers credentialed for that service and zone. Your rules pick the vendor. If a vendor declines, the request moves on. Staff do not redial. This is the same end of broker-and-fax handoffs, applied to a ride that repeats.

3

Rebook the return when the session runs long

When treatment runs past the planned end time, staff update the return. VectorCare sends the new pickup time to the vendor network. The patient is not left on the old booking. The crew is not sent before the session ends.

4

Keep status on the record

Status comes back from the vendor. The clinic sees that the ride is set, en route, or done. The team messages on the request. They do not chase a callback to learn where the patient is.

Who it is for

Built for clinics and the teams who book the ride

Dialysis clinic staff, social workers, and transport coordinators use this pattern. Hospital discharge teams use it when the standing order starts on the way out of the hospital. Health plan and state teams use the same rails when they already coordinate non-emergency trips on VectorCare.

Infrastructure

SOC 2 Type II, HIPAA, Epic-listed

VectorCare has completed a SOC 2 Type II audit, is HIPAA compliant, signs BAAs with every covered entity, hosts on AWS in the United States, and is listed on Epic's Connection Hub. See security details.

A dialysis record does not have to be Epic. The order still runs on VectorCare when the launch is outside the chart.

Frequently asked questions

  • It is a trip to dialysis that a clinician prescribes and that repeats on set days. The patient goes to the clinic and needs a ride home after treatment. The ride is logistics. It is not the dialysis treatment itself.
  • Many dialysis records store the treatment and do not schedule the ride. Staff then call or fax a vendor for each trip, or for a standing order that nobody can see. The chair and the crew fall out of step when the session time changes.
  • Staff update the return time on the order. VectorCare sends the new pickup to the vendor network. The old return does not stay in force. Status stays visible to the team.
  • No. The dialysis record remains the clinical system. VectorCare does not chart the treatment. It orders and tracks the ride.
  • No. A broker takes the trip and subcontracts it. A transport company runs the vehicle. VectorCare does neither. It coordinates the providers you contract with, and it tracks each trip.
  • Yes. Discharge staff can place the repeating ride when the patient leaves, on the same coordination layer as other discharge transport. The clinic then sees status and can rebook the return. See discharge delays.

Keep the chair and the ride on one order

See a standing dialysis ride placed from the workflow, with the return rebooked when the session runs long.