Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2546
National medical authorities and NATO bodies implementing NATO's medical evacuation interoperability under AJMedP-2
STANAG 2546 is NATO's agreement committing member nations to implement AJMedP-2, the Allied joint medical doctrine for medical evacuation; it binds nations and NATO bodies, not suppliers, directly.
STANAG 2546 is a NATO Standardization Agreement, currently Edition 2, promulgated 29 August 2018. It is not a technical specification. It is the agreement by which NATO nations commit to implement AJMedP-2, Edition A, the Allied Publication covering the allied joint medical doctrine for medical evacuation. The document's own aim is to respond to an interoperability requirement: "to maintain their national evacuation procedures as far as possible and to plan for reliable, cost-effective medical evacuation by facilitating bi- or multilateral agreements and promoting common planning, programming and training." Read on its own, STANAG 2546 requires nothing of a supplier or contractor. Its obligations run to nations and to NATO's own bodies, and the substantive medical evacuation doctrine sits in AJMedP-2, not in this cover.
STANAG 2546 is explicit that it binds nations rather than organisations. Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Under "Agreement," participating nations agree to implement AJMedP-2, Edition A - a national commitment, made by ratification, not a duty a supplier signs up to by reading this document. Ratification and implementation are kept separate: nations that have not yet reported their position are invited to "advise the NSO of their intention regarding its implementation," and national decisions on both are recorded in the NSDD. So "is STANAG 2546 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and this cover names no supplier, manufacturer or contractor at all.
The interoperability requirement STANAG 2546 responds to is letting nations "maintain their national evacuation procedures as far as possible" while planning for "reliable, cost-effective medical evacuation by facilitating bi- or multilateral agreements and promoting common planning, programming and training." The STANAG states it "is effective upon receipt and ready to be used by the implementing nations and NATO bodies," and partner nations are separately invited to adopt it. That is national and operational machinery: a nation's medical authorities put AJMedP-2 into effect through their own orders and procedures, not a design or delivery obligation on a contractor.
A reader who only has STANAG 2546 in hand does not yet have the doctrine it points to. That sits in AJMedP-2, Edition A. STANAG 2546 also names the Geneva Conventions of 1949 (incorporating the Hague Protocols of 1907) and MC 0551, NATO's medical support concept for NATO Response Force operations, alongside ten further STANAGs, each paired with the Allied Publication it covers: STANAG 2087, covering AAMedP-1.5, forward aeromedical evacuation; STANAG 2228, covering AJP-4.10, allied joint doctrine for medical support; STANAG 2292, covering AJP-4.11, allied joint doctrine for NATO asset visibility; STANAG 2490, covering AJP-3, allied joint doctrine for the conduct of operations; STANAG 2523, covering AJP-3.5, allied joint doctrine for special operations; STANAG 2528, covering AJP-3.14, allied joint doctrine for force protection; STANAG 2560, covering AMedP-1.6, AMedP-1.7 and AMedP-1.8, evaluation of NATO medical treatment facilities; STANAG 2562, covering AJMedP-5, medical communications and information systems; STANAG 2563, covering AJMedP-6, the allied joint civil-military medical interface doctrine; and STANAG 3204, covering AAMedP-1.1, aeromedical evacuation. The list closes with AAP-06, the NATO glossary of terms and definitions. This edition supersedes STANAG 2546, Edition 1.
National decisions on ratification and implementation are provided to the NSO, and the responses are recorded in the NATO Standardization Document Database. Nations are invited to report on their effective implementation of the STANAG in accordance with AAP-03; partner nations are separately invited to report on the adoption of the STANAG, also in accordance with AAP-03. The STANAG itself is to be reviewed at least once every five years, with the result recorded in the NSDD, and nations and NATO bodies may propose changes at any time for the tasking authority to process during that review. The agreement is supervised by the Military Committee Medical Standardization Board (MCMedSB) and the Medical Standardization Working Group (MedStd). The custodian of the STANAG is Sweden.
STANAG 2546 names no clinical, organisational or command detail of its own - that content sits entirely in AJMedP-2. It also names no assessment or certification scheme: the only stated check is that the STANAG itself is reviewed periodically, not that a nation, an organisation or an individual is certified.
STANAG 2546 itself gives an organisation nothing to implement in software: it is an agreement between nations, and the medical evacuation doctrine sits in AJMedP-2. Where this occasionally touches an organisation working alongside NATO or a national defence customer is a role supporting medical evacuation logistics, training or equipment - and there, ComplyTrain's usual footprint applies: holding the procedure that describes how that role is carried out as a controlled document, the training record showing the people involved know the requirements they are working to, and the audit trail a customer's quality representative would ask for if that role were questioned.
ComplyTrain does not carry out medical evacuation itself or act as a medical authority - that is the day-to-day work AJMedP-2 governs, not something a compliance tool does on a nation's or a supplier's behalf. The applicable tier, and the standards that come with it, are set by the contract and the customer's quality clause. Our standards explorer shows what else sits alongside STANAG 2546, including the related STANAGs above - if you are weighing up what a tasking or contract actually requires of you, we're glad to talk it through.
Tell us how you need to work with STANAG 2546 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.
Not on its own. A STANAG binds a nation once that nation has ratified and implemented it, and this cover names no supplier, manufacturer or contractor at all. Whether it touches a given organisation is a question for the contract or tasking in front of you, not for this page.
STANAG 2546 is the cover agreement: it commits nations to implement AJMedP-2 but contains no medical evacuation doctrine itself. AJMedP-2, Edition A is the Allied Publication that sets out that doctrine.
No. STANAG 2546 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement's own currency, at least once every five years, with the result recorded in the NSDD. NATO does not certify a nation or an organisation against a STANAG.
Edition 2, promulgated 29 August 2018, which supersedes STANAG 2546, Edition 1.
STANAG 2546 names ten other STANAGs alongside AJMedP-2, the publication it covers, plus the Geneva Conventions of 1949, MC 0551 and the NATO glossary AAP-06. They span forward aeromedical evacuation, medical support, asset visibility, force protection, special operations, treatment-facility evaluation, medical communications, and the civil-military medical interface, each paired with the Allied Publication it brings into force.
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.