The Modernization Program
Built for the air medical missionthat is coming next
Legacy HEMS dispatch systems were designed for today's crewed helicopters. AAMELF is architected for electric, remotely piloted, and autonomous air medical operations, scales into NIMS-aligned disaster surge when local capacity is overwhelmed, and interoperates with the emergency intake and in-flight hardware you already trust.
Legacy HEMS dispatch
Systems like Flight Vector and FL3XX are mature, certified, and deployed at scale — but they were built around fuel-powered, crewed rotorcraft and fixed-wing aircraft. Electric range, remotely piloted crews, and BVLOS operations are outside their original design.
AAMELF: AAM-native dispatch
AAMELF is purpose-built for Advanced Air Mobility medical missions: State-of-Charge feasibility, RPA and C2 coordination, BVLOS awareness, and one unified taxonomy across AAM/UAM/UAV/UAS/RPA — while integrating with proven emergency-intake and in-flight systems rather than replacing them.
Capability comparison
An honest, side-by-side look at where legacy HEMS platforms lead, where AAMELF leads, and where we integrate rather than compete.
| Capability | Legacy HEMS systems | AAMELF |
|---|---|---|
| CAD / mission dispatch | Yes. Mature, certified, deployed at scale | Yes. Modern real-time dispatch queue |
| Live aircraft tracking | Yes. Established GPS flight-following | Yes. Position, heading, speed, altitude telemetry |
| AAM / eVTOL native design | No. Built for crewed rotorcraft & fixed-wing | Yes. Core architecture across AAM/UAM/UAV/UAS/RPA |
| Pre-flight clinical triage & acuity | Partial. Acuity handled verbally / outside the CAD | Yes. Transparent CDC/ACS field-triage scoring with destination matching |
| Unified launch authorization | Partial. Separate checklists, no single gate | Yes. One go/no-go fusing clinical, risk, crew FTL & cold-chain |
| State-of-Charge dispatch | No. Fuel-based, manual range judgement | Yes. GO / MARGINAL / NO-GO energy feasibility scoring |
| Remotely piloted (RPA) operations | No. No remotely piloted concept | Yes. Operating mode, RPIC, C2 link status, BVLOS |
| Credential-aware crew matching | Partial. Limited or manual | Yes. Clearance / FAA / experience matching engine |
| Disaster surge & mutual-aid mobilization | No. No pledge / EOC call-up or NIMS credentialing model | Yes. Pre-pledged capacity, EOC-approved call-ups, NIMS qualifications & responder check-in |
| PHI encryption & access logging | Yes. Established, BAA-backed | Yes. Encryption at rest, RLS-scoped, PHI access log |
| In-flight connectivity hardware | Yes. Onboard sat-comm & vital-sign transmission | No. Integration target (see below), not built in-house |
| 911 / NG911 emergency intake | Yes. Direct emergency-call ingestion | Partial. Integration-ready inbound pipeline; activates when a source is connected (see below) |
| Certification & operational history | Yes. Years of deployed operations | Partial. Early-stage; built for the aircraft that are coming |
Comparison reflects general categories of capability for planning purposes. Product names are trademarks of their respective owners and are referenced for comparison only; no affiliation or endorsement is implied.
Where AAMELF leads
The capabilities the fuel-and-helicopter era was never designed to handle.
State-of-Charge-aware dispatch
No fuel-era CAD reasons about battery range, reserve, and landing energy. As electric medevac arrives, energy feasibility becomes mandatory — and AAMELF scores every candidate aircraft GO / MARGINAL / NO-GO before it is ever recommended.
RPA & BVLOS coordination
Operating mode, Remote Pilot in Command, command-and-control (C2) datalink health, and BVLOS authorization are first-class in AAMELF. Legacy HEMS systems have no concept of a remotely piloted air ambulance.
One platform, full AAM spectrum
AAMELF unifies AAM, UAM, UAV, UAS, and RPA medical operations under a single taxonomy and dispatch surface — rather than bolting drones onto a helicopter-era system.
First Responder Disaster Emergency Program (FRDEP)
Beyond day-to-day dispatch, AAMELF scales into a NIMS-aligned mass-casualty surge operation: operators pre-pledge aircraft, an EOC approves and calls up capacity on a declared event, and responders carry NIMS position qualifications and a PIV-I-style credential for incident check-in. Legacy HEMS CAD has no mutual-aid mobilization model.
Integrations & roadmap
We don't reinvent proven emergency-intake or onboard hardware. AAMELF is designed to be the AAM-native dispatch layer that connects them together.
Integration-ready
RapidSOS (NG911 intake)
The inbound pipeline and RapidSOS adapter are built and standing by: once an agency connects a source, 911 / NG911 emergency data flows in to create a mission and pre-seed triage automatically — no re-keying. It stays inactive until credentials are supplied and the source is switched on.
Integration target
Flightcell DZMx (in-flight connectivity)
Ingest in-flight satellite connectivity, vital-sign transmission, and automated flight-data monitoring from onboard hardware to enrich live telemetry and the patient picture in transit.
On the roadmap
Hospital & EHR handoff
Structured patient handoff and bed/capacity coordination with receiving facilities, extending the chain of custody from scene to bedside.