Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-3.2
Personnel of NATO nations' armed forces, particularly health services personnel, and the National Authorities and coordinating offices that receive their medical information reports
AMedP-3.2 is the NATO agreement on gathering and passing on medical information from operations and exercises, routed through a chain of command or National Authority to a coordinating office, under STANAG 2481.
AMedP-3.2 is the NATO Allied Medical Publication that sets out how nations gather medical information during operations and exercises and pass it on so it reaches the people who need it. Participating Nations' agreement to use it is recorded in STANAG 2481. The document draws a deliberate line between two things people often use interchangeably: "medical information" is data about human or animal health that "has not been analyzed for intelligence purposes," while medical intelligence is a specialised product derived from it, potentially needing medical expertise to process. Everything AMedP-3.2 routes and reports is, by its own definition, information rather than intelligence.
The document's own background points to a recurring lesson of military history: personnel losses from disease have shaped the outcome of operations, and today's forces rely more than before on resources available locally in the area of operations. Chapter 3 gives the operational reason for standardising how medical information is gathered rather than leaving each nation to its own method: "interoperability will be maximised and burden sharing facilitated if all TCNs are sharing the same" medical information and medical intelligence. A shared, standardised way of collecting and reporting is what lets nations contributing to the same operation work from the same picture instead of each rebuilding it independently.
Collecting relevant medical information is, in the document's own words, "the responsibility of all personnel, but particularly health services personnel." Once a report is completed, it does not stop at the unit that gathered it. AMedP-3.2 names a coordinating office as the destination - this can be a NATO command's medical adviser, another NATO Headquarters, or a NATO Centre of Excellence, according to how that command has delegated the task - and sets two routes for getting a report there depending on context. Within a NATO operation or exercise, a report goes through the theatre chain of command for release to the National Authority and onward to the coordinating office. Under national command, it goes to the National Authority directly, for release and onward forwarding to the same coordinating office. Either way, the National Authority sits in the chain before the information reaches NATO's own coordinating structure.
This page does not set out the forms AMedP-3.2 points nations toward, or what they capture: that detail lives in a companion standards-related document, SRD-01, which the text names but does not reproduce.
Beyond naming who collects it and where it goes, AMedP-3.2 says one thing about protecting a completed report: it "should be classified appropriately depending on the information contained therein," a judgement left to whoever compiles it rather than a fixed rule. The document does not state how long medical information gathered this way should be kept, and it says nothing about technical safeguards, access control, or a retention schedule.
AMedP-3.2 binds through nations' ratified agreement to use it, recorded in STANAG 2481. Like any STANAG-covered publication, it commits a nation once ratified, and a nation implements it through its own armed forces and command structure; the document names no supplier, manufacturer or contractor anywhere in its text. There is no certification scheme, accredited assessment or audit mechanism described here: this is a reporting agreement between nations, not something an organisation is assessed against.
AMedP-3.2 is an operational NATO document, not a management-system standard, and the substantive work it describes - collecting medical information in the field and moving completed reports through a chain of command or a National Authority to a coordinating office - happens inside a nation's armed forces and NATO's own command structure, not in software.
Where an organisation supporting a NATO operation is asked, by contract, to follow the same reporting discipline the personnel around it work to, ComplyTrain is the kind of place the evidence trail for that lives: a record that staff have been briefed on when a report is due and to whom it is released, and a procedure document covering how a completed report gets classified before it is passed on. ComplyTrain does not collect, transmit, store or classify medical information itself, and it does not stand in for the chain of command, the National Authority or the coordinating office AMedP-3.2 names. The standards explorer shows what else sits alongside AMedP-3.2, including STANAG 2481 itself, and we are glad to talk through what a specific requirement is asking for.
Tell us how you need to work with AMedP-3.2 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.
It binds through STANAG 2481, the NATO agreement recording Participating Nations' agreement to use this publication. A STANAG binds a nation once ratified; it does not itself place an obligation on a company, and AMedP-3.2's own text names no supplier or contractor.
No. AMedP-3.2 describes no certification scheme, accredited body or audit process of any kind. It is an agreement between nations about how medical information is gathered and reported, not something a company or individual is assessed against.
AMedP-3.2 defines medical information as data relating to human or animal health that has not been analyzed for intelligence purposes. Medical intelligence is a specialised product derived from that information, which the document notes may need medical expertise to process. The document governs the first, not the second.
No. The document says a completed report should be classified appropriately depending on what it contains, but it does not state a retention period for the information itself.
Not in AMedP-3.2 itself. The document names a companion standards-related document, SRD-01, as the source for the forms it points nations toward, without reproducing their content in its own text.
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.