Integration
OpenAPI and DispatchCare
Every mission is available over the API, in both directions.
OpenAPI
Live- Create, update and read missions
- Event log and outcome export
- Scoped tokens with full audit trail
Missions can be created, updated and read over the VectorCare OpenAPI. Hospitals push cohort lists, payers push member batches, programs update status from their own tools, and data teams pull the event log into a warehouse.
Authentication is token-based and scoped per organization. Every API action lands in the same audit log as web app actions, so data lineage holds for reporting.
At a glance
- Create, update and read missions
- Event log and outcome export
- Scoped tokens with full audit trail
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.
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.
VectorCare's proprietary tool for building SMART on FHIR apps once and deploying them into any EHR, handling launch, authorization and FHIR mapping per EHR so the hospital doesn't run an integration project.
No. The ePCR remains the record of care. DispatchCare captures the mission status and the sponsor-required outcome fields only.
The CP program updates status in the DispatchCare web app or mobile app, or over the API. The hospital sees it in the DispatchCare app inside the chart or in the web app, and is notified on abort or escalation.
See a mission go from the chart to the home and back.
A 15-minute walkthrough with a coordinator view, a CP program view and the dashboard your sponsor will read.