Integrations
Short integrations, because the scope is narrow.
DispatchCare does not replace an EHR, a CAD or an ePCR. It reads what a referral needs and hands back status and outcomes, and SoFaaS carries the same app into Epic, Oracle Health, MEDITECH and any other SMART on FHIR chart.
Built to work with what you already run
- 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
EHRs
One app, deployed through SoFaaS. Status labels show where each environment stands.
Epic
ListedLaunch a CP referral from the patient chart with context already filled in.
Oracle Health
Available via SoFaaSSMART on FHIR launch through SoFaaS, secure web form everywhere else.
MEDITECH
Available via SoFaaSA referral path that does not wait on an EHR project.
athenahealth
Available via SoFaaSRefer from athenahealth without a custom integration project.
CPSI / TruBridge
Available via SoFaaSRural-first EHR coverage without an integration budget line.
eClinicalWorks
Available via SoFaaSAmbulatory referrals into community paramedicine, structured from the start.
NextGen
Available via SoFaaSHealth center and practice referrals into the CP network.
Veradigm
Available via SoFaaSVeradigm coverage on the same SMART on FHIR framework.
Any SMART on FHIR EHR
Available via SoFaaSOne app, deployed into whatever chart your clinicians already use.
ePCR, data and the API
ePCR and NEMSIS
NEMSIS exportYour ePCR stays your ePCR. We take mission status and sponsor outcome fields.
OpenAPI
LiveEvery mission is available over the API, in both directions.
No EHR IT project required to start
How an integration actually works
For a SMART on FHIR EHR, SoFaaS launches the DispatchCare app from inside the chart the same way any SMART app launches: the EHR hands over a launch context and an authorization token scoped to the patient the clinician already has open. The clinician starts a referral without re-entering the patient's demographics or leaving the chart. SoFaaS handles the launch, authorization and FHIR resource mapping for that specific EHR, so your IT team is not building a custom integration from scratch.
For hospitals not yet on SMART on FHIR, or for a fast pilot, the secure web referral form covers the same referral intake without any EHR-side work: staff open a link, enter the referral, and the mission broadcasts the same way. Either path lands in the same mission record, so reporting looks identical regardless of how the referral came in.
On the ePCR side, DispatchCare does not pull the full clinical chart. A community paramedicine program exports the visit's NEMSIS 3.5 elements, and DispatchCare maps the fields a sponsor's reporting requires (visit completion, outcome, disposition) into the mission record. Programs that want a tighter loop can use the OpenAPI directly instead of the portal.
What's required from your team
Hospital IT
Approve the SMART on FHIR app launch (or skip this entirely and start with the web form). No new HL7 interface build.
CP program
Export NEMSIS 3.5 from your existing ePCR, or call the OpenAPI if you want programmatic status updates.
Security review
A standard BAA-covered vendor review: access controls, audit logging and retention are documented on the security page.
Questions buyers ask
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.