Integration
ePCR and NEMSIS and DispatchCare
Your ePCR stays your ePCR. We take mission status and sponsor outcome fields.
ePCR and NEMSIS
NEMSIS export- No double documentation goal
- NEMSIS 3.5 export compatible
- Direct vendor pulls on the roadmap
DispatchCare does not replace the ePCR and does not submit NEMSIS on a program's behalf. Field clinicians document care where they always have.
For reporting, any ePCR that produces a NEMSIS 3.5 export can be joined to mission data in the BI layer. Direct pulls through vendor partner programs are on the roadmap and are labeled as such.
At a glance
- No double documentation goal
- NEMSIS 3.5 export compatible
- Direct vendor pulls on the roadmap
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.