Mission broadcast
The right program gets the mission.
A mission is offered to programs credentialed for the protocol and covering the patient's address. The first qualified accept takes it, and everyone else sees it close.
Mission MSN-4821 · CHF 72-hour
Completed- Received09:12
Referral submitted from the patient chart at discharge.
- Scheduled10:04
County EMS accepts and books a visit for tomorrow, 13:00–15:00.
- En route13:06
Crew departs; patient receives an SMS with the arrival window.
- On scene13:34
Assessment underway; a walker need is flagged as a child request.
- Completed14:11
Outcome fields recorded; referrer notified; mission closed.
How matching works
Territory
County and service-area coverage the program declares and the sponsor confirms.
Protocol and skill
Only programs credentialed for the requested protocol are offered the mission.
Capacity
Programs signal availability windows so missions land where they can actually be run.
Escalation path
Online medical control and escalation contacts are attached before anyone leaves the station.
From referral to accepted mission
- 01
Referral submitted
A hospital, payer or state office sends a structured mission request.
- 02
Eligibility filter
Only programs whose declared territory and protocol match the mission are considered.
- 03
Capacity check
Among eligible programs, missions are offered where a visit window is actually open.
- 04
Offer sent
Qualifying programs see the mission in their queue at the same time.
- 05
First accept wins
The first qualified acceptance locks the mission; other queues update immediately.
- 06
Status flows back
The referrer sees every state change without calling the program.
Status the requester can trust
Every state change is timestamped and visible without a phone call.
Exceptions are the point
What happens when the first attempt does not work
Matching is only as good as its handling of the cases that do not go smoothly on the first try. If no credentialed program in the mission's territory has open capacity, the mission does not disappear into a queue; it sits in Received with a visible elapsed timer, and after a configurable window it can widen to a broader territory, route to a program coordinator, or return to the referrer for manual handling.
If a program accepts and then finds it cannot complete the visit, that gets recorded as an explicit exception rather than silence: patient declined, no answer at the address on file, needs escalation, or transported to a higher level of care instead. Each of those closes the mission with a reason attached, and the referrer is notified the moment it happens rather than at the next status check.
Connectivity in the field
What broadcast is not
Mission broadcast routes scheduled, non-emergency care missions between credentialed CP and MIH programs. It is not a 911 CAD system and does not triage emergencies: anything emergent goes through 911 and CAD, not through this queue. It is also not an ePCR; the mission record carries status, territory, protocol and outcome fields, while clinical documentation of the visit itself stays in the program's own ePCR.
Getting started
Programs join by declaring the counties or service areas they cover, the protocols they are credentialed for, and their escalation contacts; missions matching that profile start arriving in the portal. Referrers connect through their EHR via SoFaaS, an Epic Showroom listing, or a secure web referral form if a SMART on FHIR connection is not available yet. Either side can start with a demo to see a live mission move through the statuses above before committing to anything.
Questions buyers ask
No. Emergency calls stay in CAD. DispatchCare handles scheduled, non-emergency care missions in the home.
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.