Skip to content
DispatchCare

Integration

Epic community paramedicine referrals via SoFaaS

Launch a CP referral from the patient chart with context already filled in.

Book a demoInside your EHR

Epic

Listed
  • SMART on FHIR launch from the patient chart
  • Pre-populated patient, address and encounter context
  • Read scopes only: demographics and encounter
  • BAA, audit log and role-based access

How the launch works

DispatchCare's Epic deployment runs on SoFaaS, VectorCare's SMART on FHIR as a Service framework. VectorCare's patient-logistics apps have been live in Epic since 2025, and the same launch, authorization and FHIR-mapping layer carries DispatchCare into the chart.

SoFaaS is VectorCare's SMART on FHIR as a Service layer: DispatchCare is built once as a single app, and SoFaaS carries it into Epic and every other supported chart, handling launch, authorization and FHIR-resource mapping per environment. It is not an HL7 interface engine, and it is not a module bought from the EHR vendor.

The coordinator never leaves the patient record. They open DispatchCare in the patient context, confirm the address and contact details already carried across, choose a protocol template (post-discharge follow-up, CHF or COPD check, falls assessment, behavioral health outreach, treat-in-place follow-up), set the visit window and the escalation rule, and submit. The mission broadcasts to the community paramedicine programs that cover the territory, and the coordinator moves on to the next discharge.

Data in

Read scopes are limited to what the referral needs: Patient, Encounter, Coverage and Condition where available. No write scopes are requested at launch.

Scopes are read-only and limited to the launch context. Every read and every mission action is written to an audit log the organization can review.

Data out

DispatchCare returns mission status through its full lifecycle, received, scheduled, en route, on scene, completed, with escalated and aborted as exception statuses that notify the referrer with a reason code. A completion summary carries the sponsor-required outcome fields. Clinical write-back into the chart is on the roadmap and is not a launch commitment; nothing on this page should be budgeted as though write-back exists today.

Deployment

Epic organizations can start from VectorCare's Epic Showroom listing and the standard app-request process. Because the app is already built on SoFaaS, there is no custom interface project to fund.

  1. 01

    Scope

    Confirm the environment's SMART on FHIR support and the resources it exposes.

  2. 02

    Register

    Register the DispatchCare app and map SSO and roles for referring staff.

  3. 03

    Sign

    Execute the BAA and confirm retention and audit settings.

  4. 04

    Go live

    Walk coordinators through one referral end to end, then start with one protocol.

Not ready for an in-chart launch?

No hospital has to wait on an integration to start referring. The secure web referral form produces exactly the same structured mission, the same status lifecycle and the same reporting as the in-chart path, and a coordinator can be trained on it in a few minutes. Sites commonly start on the web form and move into the chart once the SoFaaS deployment is scheduled.

Deployment status shown as “Listed”. See Inside your EHR for the full SoFaaS picture across Epic, Oracle Health, MEDITECH and the rest.

Questions buyers ask

No. SoFaaS deploys the app into your EHR; Epic hospitals can start from the Showroom listing; a secure web referral form covers everyone else.

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 demo