Air medical dispatch
One shared workflow from mission request to hospital handoff
Responders, dispatchers, aircraft operators, and receiving hospitals work from the same mission record, so each person sees the information they need without phone relays.
Pilot program. The software is built and available for agency evaluation, but no agency, hospital, or aircraft operator uses it in live operations yet. See what is built today.
Intended users
- Air medical and EMS dispatch centers
- Responders requesting air transport
- Aircraft operators, including eVTOL and remotely piloted operators
- Receiving hospitals
Workflow
- 1
Request
A signed-in responder submits location, mission type, and initial patient details.
- 2
Triage summary
Entered vitals are summarized into an informational acuity tier. The clinician decides.
- 3
Reviews
Clinical, risk, crew, and payload reviews are recorded in one checklist. The operator retains flight release.
- 4
Coordinate
The dispatcher assigns an aircraft; status and ETA appear on a shared map.
- 5
Handoff
The receiving hospital sees the inbound mission and handoff details before arrival.
Who decides
AAMELF brings required reviews into one documented workflow while each authorized professional keeps their decision-making responsibility.
| Decision | Who decides | What AAMELF does |
|---|---|---|
| Clinical assessment and destination | The treating clinician and medical control, under your agency protocols | Shows the entered vitals, an informational acuity summary, and hospital capacity. It does not diagnose or choose a destination. |
| Accepting and assigning a mission | The dispatcher | Shows the queue, available aircraft, and feasibility warnings. Assignment is a manual action by the dispatcher. |
| Flight release and go / no-go | The aircraft operator and pilot in command (or remote pilot in command) | Records that each required review was completed. It does not grant flight release and cannot override the operator. |
| Receiving the patient | The receiving hospital | Shares the inbound mission and handoff details with the hospital that is listed as the destination. |
| Activating disaster surge capacity | The authorized emergency-management coordinator for the incident | Records pledges, activation, check-in, and taskings. It does not declare incidents. |
Missing information
If a required review or a required field is missing, the checklist shows it as incomplete. The software does not fill it in or assume a value.
Overrides
Only a dispatcher or agency admin can proceed past a no-go, and only by entering a reason. The override, who made it, and when are written to the mission audit ledger.
Conflicting reviews
If any required reviewer marks no-go, the checklist shows no-go. Resolving the conflict stays with the people responsible.
Current availability
- Available in pilotBuilt and usable during a pilot evaluation. Not yet used in live operations.
- Built, not yet connectedThe integration exists, but no real external system is connected to it yet.
| Capability | Status | How it works today |
|---|---|---|
| Mission intake and dispatch queue | Available in pilot | Signed-in responders submit a mission request; dispatchers see it in a priority-sorted queue and assign an aircraft. |
| Triage acuity summary | Available in pilot | Entered vitals and mechanism of injury are summarized into an acuity tier with the contributing factors shown. Informational only; not a validated clinical assessment. |
| Pre-launch review checklist | Available in pilot | Clinical, risk, crew, and payload reviews are recorded in one place before launch. The software records each review; it does not grant flight release. |
| Battery / endurance feasibility check | Available in pilot | Compares the planned flight against reported battery energy or endurance minutes and warns when the reserve would be too low. |
| Tracking and ETA updates | Available in pilot | Mission status and positions update on the map from entries made in the app. Automatic position data needs a live aircraft feed (see below). |
| Live aircraft data feeds (ADS-B, Remote ID, MAVLink, OEM) | Built, not yet connected | Feed adapters and a secured ingestion endpoint are built. No real aircraft or operator feed is connected yet. |
| Hospital capacity board | Available in pilot | Hospital staff update beds, diversion status, and landing-zone availability manually in the app. |
| Hospital handoff API (FHIR R4) | Built, not yet connected | A hospital-scoped API that shares inbound mission summaries and vitals as FHIR R4 is built. No hospital system is connected yet, and it is not a certified EHR-vendor integration. |
Limitations
- Not a replacement for your primary 911 CAD system.
- The acuity summary is decision support, not a validated clinical scoring tool.
- Automatic aircraft positions require a live data feed; none is connected yet.
- The hospital handoff API is built but not connected to any hospital system, and is not a certified EHR-vendor integration.
- Patient fields are encrypted at rest. Do not enter real patient data outside a signed pilot agreement.