Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2535
Defence forces and national military medical authorities operating under a contract or tasking that invokes STANAG 2535 or the AMedP-4.1 publication it covers
STANAG 2535 is NATO's agreement committing ratifying nations to implement AMedP-4.1, Edition B, on deployment health surveillance; it supersedes Edition 2, dated 24 July 2014.
STANAG 2535 is the NATO Standardization Agreement covering deployment health surveillance. It is not itself a technical specification: it is the agreement by which NATO nations commit to implement one, and the actual surveillance content sits in a separate publication, AMedP-4.1, Edition B, which this STANAG names as the standard participating nations agree to implement. This is Edition 3, and it supersedes STANAG 2535, Edition 2, dated 24 July 2014. Anyone working through what deployment health surveillance actually requires needs AMedP-4.1's own record, not this cover agreement.
The stated interoperability requirement is to enhance interoperability for deployment health surveillance in support of NATO operations, taking account of the developments that have taken place in this domain since 2010. Under the agreement clause, participating nations agree to implement AMedP-4.1, Edition B. Ratification and implementation are separate, tracked steps, as with any STANAG, and a nation can ratify with reservations; this document names none of its own.
STANAG 2535 binds nations, not suppliers. The enclosed agreement is one which has been ratified by member nations, as reflected in the NATO Standardization Documents Database, and is promulgated on that basis; it is effective upon receipt for use by the participating nations and NATO bodies. Nations that have not already done so are invited to examine their own ratification and advise the NATO Standardization Office of their intention regarding ratification and implementation. A supplier meets AMedP-4.1, or STANAG 2535 itself, only where a contract or a national instruction says so; the document sets no obligation reaching a supplier directly.
The publication this STANAG covers is implemented once a nation has issued the necessary orders or instructions directing the forces concerned to put its content into effect. In doing so, the minimum planning and organizational, functional, information and communication requirements, and training and personnel requirements, along with evaluation and re-evaluation, must all be considered. Allies and NATO bodies report their implementation details through NATO's electronic reporting tool; partner nations are separately invited, rather than obliged, to do the same. A NATO Effective Date is not applicable to this STANAG.
STANAG 2535 is reviewed in accordance with AAP-03, and the result is recorded in the NATO Standardization Documents Database. No fixed review date is printed in this edition. It is supervised under NATO's medical standardization committee chain (COMEDS, MCMedSB, MedStd, FHP), and published by the NATO Standardization Office (NSO) in Brussels, which also takes any comments on it.
STANAG 2535 covers AMedP-4.1, the publication that carries the deployment health surveillance content itself. Its cover also names eighteen further related NATO documents, presented as related reading rather than as requirements of this STANAG:
AJP-4.10 is not in our standards catalogue, so it appears above by name only. STANAG 2535's own periodic review follows AAP-03.
STANAG 2535 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status to NATO for the record, and a periodic review of the STANAG itself under AAP-03. Nobody is certified against STANAG 2535, and the document never uses that language. Where a nation's own deployment health surveillance activity is checked in practice, the assessor and the evidence required are set by that nation's own orders and instructions, or by a contract's quality clause where a supplier is involved, not by this STANAG.
STANAG 2535 itself has nothing to implement: it is a ratification agreement, and the deployment health surveillance content sits in AMedP-4.1. The work that content generates, running a surveillance programme for a deployed force, is medical and operational work, carried out by force health protection and deployed medical personnel, not in a compliance platform.
What ComplyTrain does for that kind of work in general is give a defence organisation one auditable place to hold the surveillance procedures a nation's own implementing orders set out, the training records for the personnel who run them, and the evidence trail, corrective actions and document control, that a command inspection or a customer's quality clause will ask to see.
ComplyTrain does not carry out deployment health surveillance, decide what a surveillance programme monitors, or determine whether a deployed unit's practice meets AMedP-4.1. That is medical work, done under a nation's own orders and against the publication itself, not something a compliance tool does on a nation's or a supplier's behalf.
Which STANAGs and Allied Publications actually apply to a given deployment is set by the contract and the customer's quality clause, not by us. Browse the standards explorer to see what sits alongside STANAG 2535 and AMedP-4.1, and talk to us about the evidence trail once you know which ones are in your contract.
Tell us how you need to work with STANAG 2535 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.
STANAG 2535 is the cover agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AMedP-4.1, Edition B is the publication itself, the Allied Medical Publication that sets out the deployment health surveillance content. The STANAG is the agreement to implement it, not the surveillance requirements themselves.
Edition 3. It supersedes STANAG 2535, Edition 2, dated 24 July 2014.
No. STANAG 2535 describes nations ratifying and reporting implementation to NATO, and a periodic review of the STANAG itself under AAP-03. It names no certification or audit scheme for a supplier, a product, or the surveillance activity it covers.
Its cover names eighteen further NATO medical and doctrine publications, spanning patient data exchange, medical intelligence and planning, force health protection, and CBRN medical support, alongside AMedP-4.1 itself. None of them is a requirement of this STANAG; the full list is in "Standards it references" above.
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.