Skip to content
DispatchCare

Patient logistics infrastructure

Mission control for community care.

Refer a patient to community paramedicine from the chart. Know when the visit happened, before the readmission tells you. Hospitals, payers and states send one structured request; CP programs run the visit and send status and outcomes back.

Book a demoSee it in your EHR

Mission MSN-4821 · CHF 72-hour

Completed
  1. Received09:12

    Referral submitted from the patient chart at discharge.

  2. Scheduled10:04

    County EMS accepts and books a visit for tomorrow, 13:00–15:00.

  3. En route13:06

    Crew departs; patient receives an SMS with the arrival window.

  4. On scene13:34

    Assessment underway; a walker need is flagged as a child request.

  5. Completed14:11

    Outcome fields recorded; referrer notified; mission closed.

EscalatedAbortedException statuses notify the referrer immediately.

What is DispatchCare?

Not a 911 CAD. Not an ePCR. DispatchCare is the layer between the people who identify a patient need and the community programs who meet it in the home.

Request

A referral leaves the chart with the protocol, the visit window, the escalation rule and the sponsor fields already attached, no phone tag, no faxed packet.

Mission

Missions broadcast to programs by territory, skill and availability. Accept, schedule, run, close, with a live status the requester can read.

Proof

Every mission produces the fields a sponsor, a state office or a payer asks for later. The report is a by-product of the work, not a second job.

How it works

  1. 01

    Request

    A coordinator sends a structured mission from any SMART on FHIR chart or a secure web form.

  2. 02

    Broadcast

    The mission routes to qualified programs by territory, protocol and capacity.

  3. 03

    Schedule

    A program accepts, sets a visit window and confirms with the patient by SMS.

  4. 04

    Status

    Received, scheduled, en route, on scene, complete, visible to the requester.

  5. 05

    Logistics

    Equipment, supplies and mobility needs are attached to the mission, not chased.

  6. 06

    Report

    Outcome fields close the loop and roll up into the program scorecard.

What changes for you

You hand a discharged patient to a community program and then hear nothing until a readmission tells you how it went.

Refer from the chart in any SMART on FHIR EHR, watch the mission move through six statuses, and get notified the moment a visit is escalated or aborted.

For hospitals and health systems

Referral → first visit: median hours

Illustrative target; your data once live.

Inside the chart, whatever the chart is

DispatchCare deploys through SoFaaS, VectorCare's SMART on FHIR as a Service: one app, built once, deployed into Epic, Oracle Health, MEDITECH and any other SMART on FHIR–capable EHR. Patient, address and clinical context are pre-populated. No EHR IT project; a secure web form covers everyone else from day one.

  • Epic
  • Oracle Health
  • MEDITECH
  • athenahealth
  • CPSI / TruBridge
  • eClinicalWorks
  • NextGen
Community care referral
PatientMarla Whitfield, 68, synthetic record
ProtocolPost-discharge follow-up (72 hours)
Address412 Ridge Line Rd, Boone County
WindowThu 8:00 AM – 12:00 PM
StatusScheduled, Boone County EMS accepted
Illustrative, EHR-neutral view. Patient details shown are synthetic.
See the EHR workflowEpic Showroom listing

What do community paramedicine programs measure?

Illustrative targets programs set with us. Your numbers come from your own data once you are live.

0h

Post-discharge contact window

Common CHF and COPD target.

≥0%

Missions closed with sponsor outcome fields

Closure requires the sponsor fields; targets set with each program.

0 yr

Default record retention

Meets the RHT ≥3-year post-report requirement.

0%

Escalations recorded with a reason

Every abort or escalation carries a reason code the referrer sees.

Rural Health Transformation

The Rural Health Transformation Program directs $50B across FY2026–2030. States write plans; subrecipients build programs. DispatchCare is vendor infrastructure a subrecipient can budget as a subaward line, with the evaluation data the program will have to report.
Explore the RHT hubGet the budget kit

What does DispatchCare connect to?

DispatchCare reads what a referral needs and hands back status and outcomes, which keeps every connection small.

  • EpicListed
  • Oracle HealthAvailable via SoFaaS
  • MEDITECHAvailable via SoFaaS
  • athenahealthAvailable via SoFaaS
  • CPSI / TruBridgeAvailable via SoFaaS
  • eClinicalWorksAvailable via SoFaaS
  • NextGenAvailable via SoFaaS
  • VeradigmAvailable via SoFaaS
  • ImageTrendNEMSIS export
  • ESONEMSIS export
  • ZOLLNEMSIS export
  • NEMSIS 3.5NEMSIS export
  • SMART on FHIRLive

Questions buyers ask

DispatchCare is patient logistics infrastructure for community paramedicine and mobile integrated healthcare: request, broadcast, status, logistics and reporting between hospitals, payers and states on one side and CP programs on the other.

See a mission go from the chart to the home and back.

A 30-minute walkthrough with a coordinator view, a CP program view and the dashboard your sponsor will read.

Book a demoJoin the network