Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2561
National authorities implementing Allied joint medical force health protection doctrine, and defence suppliers who meet AJMedP-4 named in a contract or tender
STANAG 2561 is NATO's agreement committing member nations to implement AJMedP-4, Allied joint medical force health protection doctrine; it binds nations rather than suppliers, and the doctrine itself lives in AJMedP-4.
STANAG 2561 is the NATO standardization agreement by which member nations commit to implement AJMedP-4, Edition B, Allied joint medical force health protection doctrine. A STANAG is not itself a technical document: it is the agreement by which NATO nations commit to implement one, and the substance sits in the Allied Publication it covers. This cover's own aim is "to respond to the following interoperability requirements", stated here as the intent "to provide basic evidence-based information, standards and approaches to force health protection in support of military operations". Read plainly, that means the force health protection doctrine itself, evidence-based information, standards and approaches for protecting the health of a deployed force, is what AJMedP-4 covers, not this agreement.
Participating nations "agree to implement the following standard", named as AJMedP-4, Edition B. The cover lists no other related document beside the one it covers.
The mechanism that matters for a supplier: a STANAG binds a nation, not a company. "This STANAG is effective upon receipt for use by the participating nations and NATO bodies", but effective is not the same as implemented. Nations "are invited to examine their ratification of the STANAG and, if they have not already done so, advise the NSO of their intention regarding its ratification and implementation", with responses recorded in the NATO Standardization Document Database. A nation only gives the agreement domestic force once it "has issued the necessary orders or instructions to authorities and units concerned".
Reporting is not symmetric. Allies and NATO bodies "shall provide implementation details through the electronic reporting tool", a standing obligation, while partner nations are only invited to report the same way. No NATO effective date is set: the document records it as "Not applicable".
The agreement names no certification body, no notified body and no audit of any organisation. The only check it describes is of itself: it "is to be reviewed in accordance with AAP-03", with the result "recorded within the NSDD". That is a standardization review run through NATO's own machinery, not an assessment of a company, and nothing here sets an obligation directly on a supplier or a manufacturer.
This is Edition 3, promulgated 14 November 2025, and it "supersedes the following document: STANAG 2561, Edition 2, dated 27 July 2018". It covers AJMedP-4, Edition B, which has its own record in this catalogue; the substance of the doctrine, the evidence-based information, standards and approaches to force health protection, is described there, not repeated here.
The agreement is supervised under the authority of COMEDS, MCMedSB, MedStd and FHP. Comments on it go to the NATO Standardization Office, which also publishes it. STANAG 2561 itself is unclassified and free of charge - NATO's Standardization Document Database lists it, and we do not host a copy or sell it.
STANAG 2561 and AJMedP-4 describe operational doctrine, not a management system: the actual work, force health protection for a deployed force, sits in medical planning, training and command structures, not in software. What that leaves to evidence is the paperwork around it: procedures that correctly reference AJMedP-4 and this STANAG, training records that show force health protection practice has genuinely been folded into a unit's programme, and the trail an internal or customer audit asks for afterwards.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, training records tied to named individuals and dates, and corrective actions when a gap turns up, all searchable when a higher headquarters or a customer's quality clause asks for it. It does not deliver force health protection, does not write medical doctrine, and does not replace the ratification and reporting nations carry out themselves through the NSDD and NATO's electronic reporting tool.
The applicable tier here, and whatever else it comes with, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 2561, the standards explorer covers the related NATO doctrine, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 2561 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 in general. It binds a nation once that nation ratifies it, and it reaches a supplier or a unit through a national order or a contract, not by existing on its own. Whether it applies to a given programme is set by the tasking or contract in front of you, not by the STANAG alone.
STANAG 2561 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AJMedP-4 is the doctrine itself, the Allied joint publication for medical force health protection that the STANAG gives force to. The STANAG is the cover; AJMedP-4 is the content.
Edition 3, promulgated 14 November 2025. It supersedes STANAG 2561, Edition 2, dated 27 July 2018.
No. There is no accredited certification for STANAG 2561 or AJMedP-4 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around implementing and training against the doctrine, at an informational level.
Allies and NATO bodies report implementation details through NATO's electronic reporting tool as a standing obligation. Partner nations are only invited to report the same way, through the same channel, which is a lighter obligation than the one Allies carry.
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.