Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 6532
NATO nations and NATO bodies implementing patient evacuation coordination under AMedP-2.3
STANAG 6532 is NATO's agreement committing member nations to implement AMedP-2.3, the Allied Publication on a Patient Evacuation Coordination Cell's tasks and responsibilities; it binds nations and NATO bodies, not suppliers, directly.
STANAG 6532 is a NATO Standardization Agreement, currently Edition 1, promulgated 9 July 2026. It is not a technical specification. It is the agreement by which NATO nations commit to implement AMedP-2.3, Edition A, the Allied Publication covering the tasks and responsibilities of a Patient Evacuation Coordination Cell (PECC). The document's own aim is to respond to an interoperability requirement: "to advise NATO nations on the common standard for the responsibilities, composition, organizational structure, personnel and equipment requirements of a Patient Evacuation Coordination Cell (PECC)." Read on its own, STANAG 6532 requires nothing of a supplier or contractor. Its obligations run to nations and to NATO's own bodies, and the substance of what a PECC does and how it is staffed sits in AMedP-2.3, not in this cover.
STANAG 6532 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 Documents Database (NSDD), is promulgated herewith." Under "Agreement," "Participating nations agree to implement the following standard": AMedP-2.3, Edition A - a national commitment, made by ratification, not a duty a supplier signs up to by reading this document. The STANAG "is effective upon receipt for use by the participating nations and NATO bodies," and it carries no NATO Effective Date, stated plainly as "Not applicable." So "is STANAG 6532 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.
Ratification and implementation are kept as separate steps. National ratification responses "are recorded in the NATO Standardization Documents Database (NSDD)," with allies reporting ratification details through NATO's electronic reporting tool (e-Reporting). Implementation follows later: the STANAG "is implemented when nations issue direction that the principles contained within AMedP-2.3 are considered for the coordination of patient evacuation." Allies and NATO bodies report implementation details through e-Reporting, and partner nations are separately invited to do the same. That is national and operational machinery: a nation's medical command puts AMedP-2.3 into effect through its own orders, not a design or delivery obligation on a contractor.
A reader who only has STANAG 6532 in hand does not yet have the standard it points to. That sits in AMedP-2.3, Edition A. STANAG 6532 also names four other related documents: STANAG 2546, covering AJMedP-2, the allied joint medical doctrine for medical evacuation; STANAG 2560, covering AMedP-1.6, AMedP-1.7 and AMedP-1.8, evaluation of NATO medical treatment facilities; STANAG 2627, covering ATP-97, the NATO land urgent voice messages (LUVM) pocket book; the Allied Command Operations revised patient flow management guideline; and the United Nations Office for the Coordination of Humanitarian Affairs (OCHA) civil-military coordination material, the last two named without a NATO standardization code. "This STANAG does not supersede any document."
"This STANAG is to be reviewed in accordance with AAP-03," with the result recorded in the NSDD; the text sets no fixed review interval of its own. The agreement is supervised by the Military Committee Medical Standardization Board (MCMedSB) and the Medical Standardization Working Group (MedStd). Unlike some STANAGs, this one names no separate custodian nation; comments on the STANAG go to the NATO Standardization Office (NSO).
STANAG 6532 names no clinical, organisational or staffing detail of its own for a PECC - that content sits entirely in AMedP-2.3. It also names no assessment or certification scheme: the only stated checks are procedural, on ratification, implementation reporting and the periodic review of the agreement itself.
STANAG 6532 itself gives an organisation nothing to implement in software: it is an agreement between nations, and the PECC's tasks and responsibilities sit in AMedP-2.3. Where this occasionally touches an organisation working alongside NATO or a national defence customer is a role supporting medical evacuation coordination, 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 coordinate patient evacuation itself or act as a medical authority - that is the day-to-day work AMedP-2.3 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 6532, including AMedP-2.3 and 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 6532 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 6532 is the cover agreement: it commits nations to implement AMedP-2.3 but contains no PECC tasks or responsibilities itself. AMedP-2.3, Edition A is the Allied Publication that sets those out.
No. STANAG 6532 describes no certification or accreditation scheme. Its only stated checks are procedural: ratification and implementation reported through NATO's electronic reporting tool, and a periodic review of the agreement's own currency under AAP-03. NATO does not certify a nation or an organisation against a STANAG.
No. The document states plainly that "this STANAG does not supersede any document."
Alongside AMedP-2.3, the publication it covers, STANAG 6532 names STANAG 2546 (covering AJMedP-2, medical evacuation doctrine), STANAG 2560 (covering AMedP-1.6, AMedP-1.7 and AMedP-1.8, evaluation of NATO medical treatment facilities), STANAG 2627 (covering ATP-97, the NATO land urgent voice messages pocket book), plus a patient flow management guideline and UN OCHA civil-military coordination material named without a NATO code.
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.