Air medical mission coordination
Coordinate air medical missions from request to hospital handoff
AAMELF connects responders, dispatchers, aircraft operators, and receiving hospitals in one shared workflow for helicopter, eVTOL, remotely piloted, and autonomous medical missions.
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.
Three ways to use AAMELF
Each track has its own workflow, intended users, and listed limitations.
Track 1
Track 2
Track 3
How a dispatch mission moves
Step through a sample mission to see what each role records and sees.
Request
The responder submits scene location, mission type, and initial patient details.
People decide. AAMELF documents.
Required reviews come together in 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.
Full capability status, data handling, and security details are on the Trust page.
Evaluate AAMELF with your team
Pilot agencies get a walkthrough, a separate workspace, and a written data agreement before any real data is entered.
Join the pilot programFrequently asked questions
Common questions about AAMELF, decision authority, and the pilot program.
- What is AAMELF?
- AAMELF (Advanced Air Medical Emergency Life Flight) is mission-coordination software for air medical dispatch, medical cargo logistics, and disaster surge. It connects responders, dispatchers, aircraft operators, and receiving hospitals in one shared workflow, and is designed for helicopter, eVTOL, remotely piloted, and autonomous aircraft. AAMELF is a division of AAM Nation and is currently offered through a pilot program.
- Is AAMELF in live operations?
- No. AAMELF is in a pilot program and is not used in live operations by any agency, hospital, or operator yet. The hospital handoff API and live aircraft data feeds are built but not connected to any real hospital system or aircraft. The Trust page lists what is built and what is not.
- Who makes the launch decision?
- People do. Clinical decisions stay with the clinician and medical control, flight release stays with the operator and pilot in command, and dispatchers assign aircraft. AAMELF records each required review in one checklist and shows go, caution, no-go, or incomplete. Only a dispatcher or admin can proceed past a no-go, by entering a reason that is written to the mission audit ledger.
- What is the First Responder Disaster Emergency Program (FRDEP)?
- FRDEP is a proposed disaster surge module, using NIMS/ICS terminology, in which operators pre-pledge aircraft and UAV cargo drones and an Emergency Operations Center calls up ready capacity for non-clinical ambulatory evacuation and logistics resupply. FEMA, State EOCs, and the National Guard are intended users; none is a current customer or partner.