Trust and product status

What exists today, who is responsible for each decision, and what is not in place yet.

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.

Capability status

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.

AAMELF capability status
Capability	Area	Status	How it works today
Mission intake and dispatch queue	Air medical dispatch	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	Air medical dispatch	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	Air medical dispatch	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	Air medical dispatch	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	Air medical dispatch	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)	Air medical dispatch	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	Air medical dispatch	Available in pilot	Hospital staff update beds, diversion status, and landing-zone availability manually in the app.
Hospital handoff API (FHIR R4)	Air medical dispatch	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.
Chain-of-custody records	Medical cargo logistics	Available in pilot	Each handoff of an organ or medical shipment is recorded with who handed it over, who received it, and when.
Cold-chain temperature log	Medical cargo logistics	Available in pilot	Temperature readings are logged against the shipment and flagged when out of range. Readings are entered or posted to the API; no specific sensor hardware is certified with AAMELF.
Medical supply delivery coordination	Medical cargo logistics	Available in pilot	Cargo missions use the same intake, assignment, and status workflow as patient missions, with payload details instead of patient details.
Reserve fleet pledges and activation	Disaster surge (FRDEP)	Available in pilot	Operators pledge aircraft in advance; an authorized coordinator activates pledged capacity for a declared incident.
Responder credentials and incident check-in	Disaster surge (FRDEP)	Available in pilot	Responders hold position qualifications in the app and check in to an incident before receiving taskings.
Surge operations console and resource requests	Disaster surge (FRDEP)	Available in pilot	A live board for evacuation and resupply taskings, with resource requests and a tasking history.

Decision authority

Who makes each decision, and what the software does
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.

Operating entity and contact

Operator: AAMELF is a division of AAM Nation.
Accountable contact: contact@aamnation.com

Product maturity and intended use

Maturity: Pilot program. Not used in live operations by any agency, hospital, or operator.
Intended use: Coordination and documentation software for air medical dispatch, medical cargo, and disaster surge. It is not a medical device, does not provide clinical care, and does not grant flight release.

Data collected and access

Collected: Account details, mission and shipment records, aircraft and crew details, hospital capacity, and patient fields entered by responders.
Patient fields: Patient name, age, injury, and clinical notes are encrypted at rest. Decryption is limited to users entitled to the mission, and every read is logged.
Access: Database row-level security limits each user to their own agency’s records. Roles (responder, dispatcher, hospital, operator, admin) limit what each user can do.
Retention and deletion: A retention schedule has not been published yet. It will be agreed in writing with each pilot agency before real data is entered.

Security controls

Documented controls: Encryption of patient fields, row-level security, PHI access logging, hashed API tokens, signed outgoing webhooks. Details on the Security page.
Independent assessments: None yet. AAMELF has not completed a third-party audit, penetration test, SOC 2, or HITRUST assessment.
HIPAA: Designed around HIPAA privacy principles. This is not a certification.

Integrations

Live connections: None. No hospital system, aircraft feed, or third-party CAD is connected.
Built, not connected: Hospital handoff API (FHIR R4), aircraft data feeds (ADS-B, Remote ID, MAVLink, OEM JSON), outgoing webhooks.

Support and limitations

Support: Pilot support is by email. There is no 24/7 operations desk.
Incident escalation: Report security or data issues to contact@aamnation.com. Do not rely on AAMELF as your only means of emergency communication.

Basis for NIMS references

What it means: The disaster surge module uses NIMS/ICS terminology for position qualifications, incident check-in, and resource requests. FEMA has not reviewed or endorsed AAMELF.