Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2132
National military medical and standardization authorities implementing NATO's Field Medical Card requirement
STANAG 2132 is NATO's agreement committing ratifying nations to implement AMedP-8.1, the standard for the Field Medical Card used to document a casualty's initial treatment and evacuation.
STANAG 2132 is the NATO standardization agreement that gives force to AMedP-8.1, Edition B, the Allied medical publication that sets out a common Field Medical Card (FMC). A STANAG is not itself a technical specification: it is the agreement by which NATO nations commit to implement one, and the actual content sits in the Allied Publication it covers. This STANAG responds to a stated interoperability requirement: "to establish common procedures and standardized documents for the reporting of patient's initial treatment, a Field Medical Card (FMC)." The card documents "casualties' identity, first aid, initial medical treatment and care in transit up to and including medical treatment facilities ROLE 1." The card's own fields and content are AMedP-8.1's subject, not this cover's; a nation implementing STANAG 2132 works from AMedP-8.1 itself, and an example card sits in this STANAG's own Annex A.
This is Edition 4, dated 27 June 2023. It supersedes "STANAG 2132, Edition 3, dated 11 June 2013."
The mechanism that matters here: a STANAG binds a nation, not a supplier. "Participating nations agree to implement" AMedP-8.1, Edition B, and the national ratification response is "recorded in the NATO Standardization Document Database (NSDD)." Once ratified, "this STANAG is effective upon receipt for use by the participating nations and NATO bodies," and it "is implemented when a nation has reviewed and made necessary changes to their existing field medical card, and adjust training and logistical requirements accordingly in order to ensure compatibility with AMedP-8.1." A supplier meets AMedP-8.1 only where a contract or a tender brings it in by name, not because this STANAG exists on its own.
"Allies and NATO bodies shall provide implementation details through the electronic reporting tool (e-Reporting)"; partner nations "are invited to provide their implementation details" the same way. "This STANAG is to be reviewed in accordance with AAP-03. The result of the review is to be recorded within the NSDD." The document does not itself set a fixed review interval; it points to the AAP-03 procedure instead.
STANAG 2132 also names four other related documents, without making any of them a requirement of its own: STANAG 2347 (the Medical Warning Tag), AMedP-8.8, STANAG 3204 (aeromedical evacuation), and AAMedP-1.1.
No certification exists here, and the document names none. What it describes is a national ratification, implementation and review cycle run through NATO's own machinery, not an audit against this STANAG. Whether a nation's field medical card, training and logistics match the current edition of AMedP-8.1 is a matter for that nation's own military standards and any customer's quality clause, not a certification scheme.
STANAG 2132 is a cover, not a specification, so there is nothing to evidence against the STANAG itself: its only substance is the commitment to implement AMedP-8.1. The work that follows from that, reviewing and adjusting a field medical card, training staff to complete it correctly, and adjusting logistics for compatibility with the current edition, happens in the field, not in software. What that leaves to hold as evidence is the paperwork around it: procedures that correctly reference AMedP-8.1 and this STANAG, training records that show staff have been trained against the current edition, 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, searchable when a customer's quality clause asks for it. It does not treat casualties, complete a field medical card, or decide how a nation ratifies or implements the agreement, and it does not replace the ratification and reporting nations carry out themselves through the NSDD and the electronic reporting tool.
The applicable tier here, and whatever standards come with it, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 2132, the standards explorer covers the related NATO medical publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 2132 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 only through a contract or a tender that names AMedP-8.1 or this STANAG, not by existing on its own. Whether it applies to a given programme is set by the tasking or contract in front of you.
STANAG 2132 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AMedP-8.1 is the publication itself, the Allied medical document that sets out the Field Medical Card's actual content. The STANAG is the cover; AMedP-8.1 is the substance.
Edition 4, dated 27 June 2023. It supersedes STANAG 2132, Edition 3, dated 11 June 2013.
No. There is no accredited certification for STANAG 2132 or AMedP-8.1 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around the procedures and training records that follow from implementing AMedP-8.1, at an informational level.
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.