Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 6529
NATO nations and NATO bodies that ratify and implement shared principles for evacuating highly infectious patients and transporting potentially infectious samples
STANAG 6529 is NATO's agreement committing member nations to implement AMedP-2.2 Edition A, setting shared principles for evacuating highly infectious patients and transporting potentially infectious samples between capabilities and medical treatment facilities.
STANAG 6529 is the NATO standardization agreement by which participating nations commit to implement AMedP-2.2, Edition A. Like every STANAG, it is not itself a technical specification: it is the ratified agreement between NATO nations to put a named Allied Publication into effect, and the working requirements sit in that publication, not on this cover. AMedP-2.2 carries the interoperability principles for evacuating highly infectious patients and transporting potentially infectious samples; this page describes what the STANAG cover itself says, and points to AMedP-2.2 for that substance.
The agreement responds to an interoperability requirement: advising NATO nations on interoperability principles between capabilities, equipment, and medical treatment facilities for the movement of the patients and samples it covers. Participating nations agree to implement one standard, AMedP-2.2, Edition A. This is a first edition; the cover states it supersedes no earlier document.
A STANAG binds a nation through ratification, not automatically on publication. Nations are invited to examine their own ratification position and advise the NATO Standardization Office of their intentions, and national responses are recorded in the NATO Standardization Documents Database (NSDD). A nation implements the agreement by issuing its own direction that AMedP-2.2's principles should be considered for the evacuations or transfers it covers, and both ratification and implementation details are reported through NATO's electronic reporting tool. A NATO effective date is stated as not applicable. The STANAG is reviewed in accordance with AAP-03, with the result recorded in the NSDD, and it is supervised under the authority of COMEDS, MCMedSB, MedStd and FHP.
The cover lists a set of other NATO Allied Publications and STANAGs as related reading: STANAG 2546 (AJMedP-2, allied joint medical doctrine for medical evacuation), STANAG 2596 (AJMedP-7, allied joint CBRN medical support doctrine), STANAG 2461 (AMedP-7.1, the medical management of CBRN casualties), STANAG 2873 (AMedP-7.6, a commander's guide on medical support to CBRN defensive operations), and STANAG 3204 (AAMedP-1.1, aeromedical evacuation). None of these is described as a binding requirement of this agreement.
The cover also lists international civil and public-health material as related reading, including guidance from the World Health Organization and the International Air Transport Association, and the dangerous-goods regimes for carriage by sea and by road (the International Maritime Organization's IMDG Code and the UNECE's ADR agreement). It names this material without saying what any of it requires, and this page follows the cover in that respect.
This cover carries no technical clause of its own: no isolation, handling, packaging, equipment or transport procedure appears on it. The substance of evacuating and transporting the patients and samples it covers belongs to AMedP-2.2; a reader looking for that detail needs that publication, not this agreement.
STANAG 6529 is a NATO non-classified document. NATO publishes it free of charge and does not sell it, and we do not host a copy. It can be retrieved from the NATO Standardization Documents Database or through national standardization authorities.
STANAG 6529 itself is an agreement between nations, not a document a supplier works to directly, and the interoperability principles it commits to sit in AMedP-2.2. Where a contract or a tender brings those principles into an organisation's own procedures, the work is operational: defining the procedures that reflect what the contract requires, training the people who carry them out, and holding evidence that they were followed. That work happens in day-to-day handling, not in software.
ComplyTrain gives that kind of evidence a controlled place to live: version-controlled procedure documents, training records that show who was briefed and when, and an audit trail that shows a procedure was followed on a given occasion. It does not perform or manage the evacuation or transport of patients or samples, and it does not hold or substitute for AMedP-2.2 itself or for a nation's own implementing direction.
The applicable tier, and which other NATO medical and CBRN publications come with it, is set by the contract and the customer's quality clause. The standards explorer shows what sits alongside STANAG 6529; if a contract has brought it into scope for you, we are glad to talk through what that means for your documentation.
Tell us how you need to work with STANAG 6529 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.
Only where a nation has ratified it and a contract or tender says so. A STANAG binds a nation once ratified and implemented; a supplier meets it because a customer's contract requires the principles it covers, not because the STANAG exists on its own.
STANAG 6529 is the agreement: the cover by which NATO nations commit to implement a named publication. AMedP-2.2, Edition A is that publication, and it carries the interoperability principles for evacuation and sample transport. The STANAG names AMedP-2.2 and commits to it; it does not repeat its content.
No. The cover names no certification or audit scheme. It describes nations ratifying the agreement and reporting their implementation through NATO's own electronic reporting tool, which is a governance mechanism between NATO and its member nations, not an assessment of a supplier or a product.
No. The cover states plainly that it supersedes no earlier document, which makes this a first edition.
Participating NATO nations and NATO bodies. The cover is effective on receipt for their use; a supplier or contractor is reached only indirectly, through a nation's implementing direction or a contract that reflects it.
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.