Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2558
National authorities and NATO bodies that ratify and implement NATO standardization agreements covering medical oxygen production on operations
STANAG 2558 is NATO's agreement covering AMedP-8.17, under which ratifying nations commit to a uniform, safe minimum standard for oxygen 93 per cent produced on operations, reviewed at least once every three years.
STANAG 2558 is a NATO Standardization Agreement, not a technical specification in its own right. It is the agreement by which NATO nations commit to implement a publication, and here that publication is AMedP-8.17, Edition A. The STANAG itself is short: a letter of promulgation, the agreement to implement, and the machinery for ratification, implementation and review. The substance, the actual minimum standards for producing oxygen 93 per cent, lives in AMedP-8.17, which has its own record.
The agreement responds to a stated interoperability requirement: to define the minimum standards for oxygen 93 per cent produced on operations. It is meant to contribute "to enhance the effectiveness of NATO forces when conducting joint operations, through the adoption of a uniform and safe level of production of oxygen 93 per cent for medical life-support applications" and "to facilitate the exchange of medical oxygen 93 per cent bottles between member nations." Neither the production process nor any purity, pressure or test figure beyond the 93 per cent named in the title is printed in this cover; that detail sits in AMedP-8.17.
Participating nations agree to implement "the following standard": AMedP-8.17, Edition A. They also agree "to use AMedP-8.17 as a manual for minimum standards for oxygen 93 per cent produced during field operations," and agree that "the installations for the production of oxygen 93 per cent during field operations shall meet the minimum requirements detailed in this AMedP-8.17." Their ratification and implementation decisions are recorded by NATO in the NATO Standardization Document Database, not restated here. Partner nations are separately invited to adopt the STANAG. This is Edition 1, and the cover states plainly that it "does not supersede any document."
A STANAG does not bind a supplier directly. It is "effective upon receipt and ready to be used by the implementing Nations and NATO bodies", meaning a nation's own instructions, or a contract that invokes AMedP-8.17, are what actually create a requirement for an organisation to meet. Nations report their effective implementation using the form in Annex H to AAP-03(J); partner nations use Annex G of the same publication. The STANAG "is to be reviewed at least once every three years", and any nation or NATO body can propose a change at any time to the tasking authority for processing at the next review. The tasking authority is named in the cover by its abbreviations, MCMedSB and MedStd; the custodian named is Germany, with a panel abbreviated MMMP.
This cover names AMedP-8.17 as the standard it puts into force; that is where the requirement itself lives, and it is not restated here. It also lists other related documents for context, with no further statement of how each applies: STANAG 2121 (cross-servicing of medical gas cylinders, covering AMedP-1.19), STANAG 1458 (diving gas quality, covering ADivP-04), STANAG 3198 (functional requirements of aircraft oxygen equipment and pressure suits, covering AAMedP-1.3), European Pharmacopoeia 8.0, the United States Pharmacopeia (USP 38) National Formulary (NF), two EU Council directives, and ISO/FDIS 10083. None of that last group is in our catalogue, so there is no page or explorer entry to link.
STANAG 2558 is the agreement, not the specification, so there is nothing in it to build software around. Where a nation's orders or a contract require AMedP-8.17, the work is physical and procedural: running production installations to a uniform minimum standard, holding the records that show they were checked, and training the people who operate them. ComplyTrain does not operate, test or certify oxygen-production installations itself.
What ComplyTrain does support is the paperwork trail an organisation needs once that requirement is live: the documented procedures for producing and handling medical oxygen, the training records for staff who operate the installations, and the audit trail showing the procedure was followed. That is the same kind of evidence any operational NATO publication requires, held in one auditable place rather than scattered across local files.
Which tier of this agreement applies to a given contract, and whether AMedP-8.17 is invoked at all, is set by the tasking authority and the customer's own quality clause, not by us. See the standards explorer for what sits alongside this agreement, and talk to us about how to evidence the standards a contract actually names.
Tell us how you need to work with STANAG 2558 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 once a ratifying nation's own instructions or a contract require it. A STANAG binds the nation that ratifies it; it reaches a supplier through a national order or a contract clause that invokes AMedP-8.17, not by existing on its own.
STANAG 2558 is the agreement: the ratification, implementation and review machinery. AMedP-8.17 is the Allied Medical Publication the agreement puts into force, and it is where the minimum standards for producing oxygen 93 per cent are actually set out.
No. The document describes no certification scheme. It is an agreement between nations, implemented through national orders and reported back to NATO, not something an organisation is audited or certified against.
Edition 1, promulgated 23 June 2017, is current. The cover states that it "does not supersede any document."
No. It names the interoperability requirement and the standard that answers it, but the minimum production requirements themselves are set out in AMedP-8.17, not in this cover.
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.