Network
Get missions in your territory.
Tell us the counties you cover, the protocols you are credentialed for and who to contact. Joining costs nothing, and you only see missions that match what you declared.
How a mission reaches you
- 01
You declare coverage
Counties, protocols and hours you're credentialed and staffed for.
- 02
A mission broadcasts
Only missions matching your declared coverage reach your queue.
- 03
You accept or decline
Accept what fits your capacity today; decline the rest with a reason.
- 04
You report back
Update status in the portal or API as the visit happens, through completion.
Who joins
EMS agencies, fire departments, hospital-based EMS services, private ambulance operators, DME vendors, home health agencies and non-emergency mobility providers.
No cost to join
Joining and receiving missions costs nothing. Confirm current pricing with us before budgeting.
You set coverage
Counties, protocols and hours are yours to declare and change.
Your ePCR stays yours
Clinical documentation does not move. NEMSIS 3.5 export bridges reporting.
What's required to join
Onboarding is a credentialing and contact exercise, not a technology project. You tell us the counties and protocols you're credentialed for, the hours you can realistically staff, and who on your team should be notified when a mission comes in. There is no equipment to install and no ePCR migration: missions are worked from the vendor portal on whatever device your team already uses, and your ePCR stays the system of record for the clinical visit.
Once you're in the network, you don't see every mission everywhere: you only see missions that match the coverage you declared, so a rural single-crew agency and a multi-county provider get very different queues by design. If your coverage changes, hours shift, a protocol lapses, you can update it yourself rather than waiting on a change request.
Questions programs ask before signing up
"Will this add paperwork on top of our ePCR?" No: status updates in the portal are a handful of fields per mission, and your ePCR export handles the clinical documentation you already do.
"What if we can't cover a mission we accepted?" You can hand it back with a reason; the program owns its own schedule and capacity, not DispatchCare.
"Who pays for the visit?" That's set by the referral source's program or contract, not by DispatchCare; joining the network itself costs nothing.
What kind of work shows up in the queue
Missions in the network cover the same range of scheduled, non-emergency work most CP and MIH programs already run: post-discharge check-ins, chronic disease monitoring visits, falls-risk assessments, medication reconciliation support and social-needs screening. None of it is an emergency response; anything emergent still goes through 911 and CAD, not through the DispatchCare queue. A single-crew rural agency and a multi-county mobility provider both work from the same mission structure, they just see different volumes and different mixes depending on the coverage they declared.
Multiple staff at one agency can be added to the same account, so a mission does not have to funnel through one dispatcher's inbox. Whoever is logged in and covering that territory sees the mission, accepts it, and carries it through to completion.
Questions buyers ask
Nothing to join the network and receive missions. Confirm current pricing with us before you build it into a budget.
Prefer to see it first?
We will walk your team through the program portal before you commit to anything.