Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJMedP-2
NATO force commanders and the medical staff who plan and execute medical evacuation, and the nations whose own evacuation procedures it is designed to preserve
AJMedP-2 is NATO doctrine on the concept, organisation and command arrangements for medical evacuation (MEDEVAC) in Allied joint operations, agreed to by nations under STANAG 2546.
AJMedP-2 is NATO's Allied Joint Medical Publication on medical evacuation (MEDEVAC): the concept, organisation and command arrangements that let NATO nations move casualties from the point of injury or illness to a medical treatment facility during Allied joint operations. It sits under STANAG 2546, the agreement through which nations commit to use it. Its stated purpose is to describe an evacuation system that lets nations "maintain their national evacuation procedures as far as possible" while making bi- or multilateral agreement, and common planning, programming and training, easier. The current edition is Edition A, Version 1, promulgated August 2018. It does not name a superseded edition of itself; Annex B instead lists the STANAGs and Allied Publications it draws on for particular chapters.
AJMedP-2 is written for NATO force commanders and the medical staff who plan and execute an evacuation system, not for companies. Responsibility for planning and executing an effective evacuation system sits with "the Force's medical staff", working closely with nations and operational and logistics staff, and command responsibility runs through named NATO appointments: the Land, Maritime and Air Component Commanders and their Medical Directors, the Patient Evacuation Coordination Cell, and national Medical Liaison Teams. Nations are the other addressee, since the document exists to enable them to keep their own evacuation procedures. It binds through STANAG 2546, which nations ratify and can ratify with reservations. This edition carries recorded reservations from Denmark, France, the United Kingdom, Greece and the United States, several narrowing how they accept specific paragraphs - a reminder that even a ratified STANAG's provisions are not accepted identically by every nation. AJMedP-2 does not address suppliers or manufacturers as a class, and reaches one only where a nation's own arrangements, or a contract or tender built on top of them, calls for something the doctrine describes.
The document works through five chapters and two annexes. Chapter 1 sets out the shared MEDEVAC concept: what the term means, how it differs from Casualty Evacuation (CASEVAC) - which the document states "is not a part of medical evacuation" - and how command, coordination and communications responsibilities are distributed across the strategic, operational and tactical levels. Chapters 2 to 4 work through the same organisational questions - command and control, responsibilities, coordination - for ground evacuation by armoured and non-armoured vehicles, maritime evacuation between and from vessels, and aeromedical evacuation by rotary and fixed-wing aircraft, each with its own chain of command and coordination appointments such as the Medical Coordination Cell and the Aeromedical Evacuation Control Centre. Chapter 5 is a short chapter on special operations, noting the particular evacuation difficulties long or difficult extraction and austere or secretive locations create, and the specialised teams special operations forces are expected to have available. Annex A is a glossary of abbreviations and Annex B lists the document's references. Two technical points recur throughout: minimum ambulance equipment is set out in a separate publication, STANAG 2342 (outside our standards catalogue, named here and not linked), and evacuation platforms are expected to carry the distinctive emblem the Geneva Conventions prescribe for medical transports.
AJMedP-2 mentions civilian and contracted capacity in three places, each framed as a fallback rather than a plan of first resort. It says MEDEVAC solutions "may be sourced from civilian providers to support operations for which military capabilities are not available or when their use is impractical". For strategic evacuation out of the joint operations area, it says "consideration should be made for the use of civilian charter aircraft with the caveat on their ability to fly into the operational theatre" where military means are not available. And among the coordination tasks it lists for the Medical Coordination Cell is "liaison with civilian medical agencies and organizations providing medical services and resources". The document sets no requirements for what a civilian or contracted provider has to do or hold; it only notes that this capacity exists as an option nations and commanders can draw on.
AJMedP-2 does not describe a certification, accreditation or third-party assessment scheme, and it names no body that assesses a company or a product against it. It does not identify what edition or document it supersedes. And it treats CASEVAC, the non-medically-supervised movement of casualties, as a term it deliberately excludes from medical evacuation planning rather than a lesser form of it.
AJMedP-2 binds nations, not companies, and nothing here suggests otherwise. Where a company's work touches it is narrow and indirect: a manufacturer or contractor supplying ambulances, aircraft or vessels used for medical evacuation under a NATO or national contract, or a civilian provider engaged to fill a MEDEVAC gap the document treats as a fallback. For that kind of work, ComplyTrain gives you a place to hold the procedures a contract like that actually asks for - equipment records against a named specification such as STANAG 2342, marking-compliance evidence for the distinctive emblem the Geneva Conventions prescribe, training records for personnel, and the reporting trail a customer or a NATO command would want to see.
ComplyTrain does not plan or coordinate a medical evacuation, decide how patients are categorised or moved, or stand in for the command and medical judgement AJMedP-2 places with NATO commanders, Medical Directors and their staffs. That happens in the field and in the command chain, not in software.
Which arrangements and standards actually apply to a given contract is set by the contract and the customer's quality clause, not by this page. See the standards explorer for what sits alongside AJMedP-2, and talk to us about the evidence trail behind a contract that touches it.
Tell us how you need to work with AJMedP-2 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
No. AJMedP-2 binds nations, which agree to use it by ratifying STANAG 2546, and a nation can ratify with reservations - this edition carries reservations from five nations. A company meets it only indirectly, where a national MEDEVAC arrangement or a contract built on top of one requires something of it.
AJMedP-2 defines MEDEVAC as the medically supervised movement of casualties between medical treatment facilities as part of continuous treatment. It states that Casualty Evacuation (CASEVAC), the non-medically-supervised movement of a wounded, injured or ill person, "is not a part of medical evacuation" and is not to be treated as a medical capability in planning.
Edition A, Version 1, promulgated August 2018. The document does not name an earlier edition of AJMedP-2 that it supersedes.
It mentions them three times, always as a fallback: civilian providers where military capability is unavailable or impractical, civilian charter aircraft for strategic evacuation where military means are unavailable, and liaison with civilian medical agencies as one of a coordination cell's tasks. It sets no requirements for what a civilian provider has to do or hold.
No such certification exists. AJMedP-2 names no certification body, notified body or accredited scheme; it is operational doctrine for NATO nations, commanders and their medical staffs, not a standard a company is assessed against.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.