Skip to content
DispatchCare

Inside your EHR

Refer from the chart. Read status in the chart. Whatever the chart is.

DispatchCare deploys through SoFaaS, VectorCare's proprietary SMART on FHIR as a Service tool for building and deploying apps into any EHR.

See it in your EHRAll integrations

Supported EHRs

Deployment status is confirmed per organization before contracting. Statuses shown are current as of the last review of this page.

What is SMART on FHIR as a Service (SoFaaS)?

SoFaaS is VectorCare's proprietary build-and-deploy layer for SMART on FHIR applications. DispatchCare is built once as a single app. SoFaaS then handles what normally makes in-chart software expensive: the launch sequence for each EHR, the authorization and scope negotiation each vendor expects, and the mapping between that EHR's FHIR resources and the fields a community paramedicine referral actually needs.

The practical effect is that the EHR name stops being the deciding factor in whether a hospital can run a community paramedicine program well. A critical access hospital on MEDITECH or CPSI gets the same referral workflow as an academic system on Epic, and neither has to fund a custom integration project to get it.

SoFaaS is not an HL7 interface engine, and it is not a module bought from your EHR vendor. It sits alongside the chart on the SMART on FHIR standard, reads only what the referral requires, and writes nothing clinical back.

Which EHRs does DispatchCare work inside?

One app, deployed per environment. Each card links to the deployment detail for that EHR, including what the app reads and what a go-live takes.

What does the coordinator see in the chart?

The frames below are EHR-neutral. The sequence is the same in Epic, Oracle Health, MEDITECH or any other supported chart; only the surrounding chrome differs.

  1. 01

    Launch in patient context

    The coordinator opens DispatchCare from the open patient record. No second login, no re-keying a medical record number.

  2. 02

    Context pre-populated

    Patient name, date of birth, address, phone and the encounter that triggered the referral carry across from the chart.

  3. 03

    Choose a protocol

    Post-discharge follow-up, CHF or COPD check, falls assessment, behavioral health outreach or treat-in-place follow-up, each with its own required fields.

  4. 04

    Set the window

    A visit window and an escalation rule, so the program knows both when to go and what to do if they find something.

  5. 05

    Submit

    The mission broadcasts to programs covering that territory. The coordinator returns to the chart and gets status back as it changes.

Community care referral, launched in patient context
PatientMarla Whitfield, 68, synthetic record
EncounterInpatient discharge, 09:42
ProtocolPost-discharge follow-up (72 hours)
Address412 Ridge Line Rd, Boone County
WindowThu 8:00 AM – 12:00 PM
Illustrative, EHR-neutral view. Patient details shown are synthetic.

What data does DispatchCare read and write?

Data in

DispatchCare reads Patient and Encounter, plus Condition where the environment exposes it. Scopes are read-only and limited to the launch context. Where an organization restricts a resource, the coordinator fills that field on the referral instead; the mission model does not change.

Every read and every mission action is written to an audit log the organization can review, and access is role-based through your existing single sign-on.

Data out

DispatchCare returns mission status across its lifecycle: received, scheduled, en route, on scene and completed, with escalated and aborted as exception statuses carrying a reason code the referrer sees immediately. Closing a mission produces a completion summary with the sponsor-required outcome fields.

Clinical write-back into the chart is on the roadmap. Do not budget or plan around write-back today.

What we do not claim

DispatchCare is not an EHR, a 911 CAD or an ePCR, and it does not write clinical documentation into your chart. It coordinates the mission and captures the fields your sponsor asks for afterwards.

How long does deployment take?

Available in minutes, deployed in hours, because the app already exists and SoFaaS handles the per-EHR work.

01

Scope the environment

Confirm SMART on FHIR support, the resources exposed and who will refer.

02

Register and authorize

Register the app, map SSO and roles, set audit and retention preferences.

03

Sign the BAA

A business associate agreement is in place before any patient data moves.

04

Train and go live

One protocol, one unit, one week, then widen once coordinators trust the status view.

The precedent matters here: VectorCare patient-logistics applications have run inside Epic since 2025 on this same framework, and the Lyft SMART on FHIR app reached Epic's App Market in December 2025. DispatchCare is not a first attempt at putting a logistics workflow next to a chart, it is that workflow, pointed at community paramedicine.

Rural hospitals and critical access sites

A large share of critical access hospitals run something other than Epic, MEDITECH, CPSI / TruBridge, or an ambulatory system serving an attached clinic. Community paramedicine matters most in exactly those places, so an EHR-specific product is the wrong shape for the problem.

SoFaaS reaches those charts natively wherever SMART on FHIR is supported. Where it is not, the secure web referral form covers the workflow from day one: same structured mission, same status lifecycle, same reporting, about ninety seconds for a coordinator who has done it once. Sites frequently start on the form during the RHT planning period and move into the chart later, without changing how the program runs or how it reports.

No hospital waits on an integration queue

The web referral form is not a downgrade path, it produces the same mission object the in-chart launch does. Nothing about the program design or the reporting depends on which door the referral came through.
See it in your EHREpic deployment detail

EHR questions

Any SMART on FHIR–capable EHR via SoFaaS, VectorCare's SMART on FHIR as a Service: Epic (Showroom-listed), Oracle Health, MEDITECH, athenahealth, CPSI/TruBridge, eClinicalWorks, NextGen and others. Hospitals without SMART on FHIR use the secure web referral form.

Last reviewed:

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.

See it in your EHR