Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 7112
NATO member nations and NATO bodies that ratify and implement AAMedP-1.20 through this agreement, and partner nations invited to adopt it
STANAG 7112 is the NATO agreement by which member nations commit to AAMedP-1.20, the Allied Medical Publication on recommended medical equipment for aeromedical evacuation.
STANAG 7112 is a NATO standardization agreement, not a technical specification in its own right. It is the mechanism by which NATO member nations agree to use one publication, AAMedP-1.20, for recommended medical equipment for aeromedical evacuation, so that a casualty moved by air between different national forces is not handled against a different standard of equipment depending on whose aircraft carries them. The equipment detail itself lives in AAMedP-1.20; this agreement only commits nations to it.
The stated aim is to standardize the quality of the medical materials used so that aeromedical evacuation can be carried out securely from both a medical and an aeronautical standpoint, across forward, tactical and strategic evacuation, and so that nations can exchange comparable information about the equipment they use and interoperate. Participating nations agree to implement a single named standard to meet that aim: AAMedP-1.20, Edition A. This is Edition 2 of the STANAG, which supersedes Edition 1; the letter of promulgation does not record what changed between the two.
A nation ratifying STANAG 7112 and a nation implementing it are not the same event, and the agreement treats them separately. Ratification, and a nation's intentions regarding implementation, are recorded in the NATO Standardization Document Database (NSDD); nations that have not already done so are asked to examine their own ratification and advise the NATO Standardization Office (NSO) of their intentions. Implementation is a further, national act: a nation is treated as having implemented the agreement once it has issued the orders or instructions that put AAMedP-1.20 into effect domestically, and nations, together with any partner nation that adopts the STANAG, are invited to report that in accordance with AAP-03. Partner nations are invited to adopt the STANAG without incurring the ratification obligation that applies to member nations.
The practical consequence: there is no general answer to whether STANAG 7112 is mandatory. It binds a nation once that nation has ratified and implemented it, and it reaches anyone working under that nation's forces through whatever national instruction or contract then invokes AAMedP-1.20.
The agreement is reviewed at least once every five years, and the result of each review is recorded in the NSDD. Nations and NATO bodies can propose changes at any time, through a standardization proposal to the tasking authority, and any change is processed at the STANAG's next review rather than immediately. STANAG 7112 is supervised by NATO's Military Committee Air Standardization Board (MCASB).
STANAG 7112 covers AAMedP-1.20, the Allied Medical Publication it brings into force; that record covers what the publication itself requires, not this one.
The letter of promulgation also names four other STANAG/Allied Publication pairs as related documents, not as requirements this agreement itself imposes: STANAG 2040 / AMedP-2.1 on stretchers, bearing brackets and attachment supports; STANAG 2087 / AAMedP-1.5 on forward aeromedical evacuation; STANAG 3198 / AAMedP-1.3 on functional requirements of aircraft oxygen equipment and pressure suits; and STANAG 3204 / AAMedP-1.1 on aeromedical evacuation. Nations report their implementation of STANAG 7112, and partner nations their adoption of it, in accordance with AAP-03.
NATO's Standardization Document Database lists the catalogue and serves the unclassified documents free of charge. NATO does not sell STANAG 7112 and neither do we; find the record on the NSDD.
STANAG 7112 itself is nothing to implement in software: it is the agreement by which nations commit to AAMedP-1.20, not a specification. Once a national implementing instruction or a contract brings AAMedP-1.20 into force, the work is holding evidence that it has been met, procurement and maintenance records for the medical equipment carried on evacuation aircraft, training records for the aeromedical evacuation crews and medical staff who use it, and the audit trail a customer's quality assurance representative or a national inspector would ask to see. That work happens in the hangar and the medical stores, and ComplyTrain does not do it for you: it does not decide what the equipment list requires, procure equipment, or represent an organisation at a government quality assurance visit.
What ComplyTrain does is hold the procedures, training records and audit evidence that this kind of operational standard generates, and keep them current as instructions or contracts change. Which tier of documents actually applies to a given contract, and what sits alongside AAMedP-1.20, is set by the contract and the customer's quality clause, not by this page - use the standards explorer to see what else is in scope, and talk to us about how you would evidence it.
Tell us how you need to work with STANAG 7112 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 by itself. It binds a NATO member nation once that nation has ratified it and issued the instructions that put it into effect domestically; a partner nation is invited to adopt it rather than required to ratify it. Whether it reaches a given supplier or programme depends on whether a national instruction or a contract then invokes AAMedP-1.20.
STANAG 7112 is the agreement; AAMedP-1.20 is the Allied Medical Publication it brings into force and where the recommended medical equipment itself is specified. Nations ratify and implement the STANAG, and in doing so commit to using AAMedP-1.20.
Edition 2, promulgated 19 July 2018, is current. It supersedes Edition 1 of the same STANAG; the letter of promulgation does not record what changed between the two editions.
No one. Ratification and implementation are actions a government takes, recorded in the NATO Standardization Document Database, not an assessment an organisation is certified against. Any audit a supplier faces would be against AAMedP-1.20 itself, once it applies, not against this STANAG.
At least once every five years, with the result recorded in the NSDD. Nations and NATO bodies can propose changes at any time, but the agreement processes them at the next review rather than immediately.
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.