Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-8.1
NATO nations' military medical services documenting a casualty's initial treatment and evacuation up to Role 1
AMedP-8.1 sets the minimum data a NATO nation's Field Medical Card must carry to document a casualty's initial treatment and evacuation, agreed between nations under STANAG 2132.
AMedP-8.1 is a NATO Allied Medical Publication: DOCUMENTATION RELATIVE TO INITIAL MEDICAL TREATMENT AND EVACUATION. It sets out the minimum data a NATO nation's Field Medical Card (FMC) has to carry so a casualty's initial treatment and evacuation is understood by whoever receives that casualty next, from the point of injury through to a Role 1 medical treatment facility. It is issued as an agreement between nations, recorded in STANAG 2132, rather than a technical specification a supplier builds a product against.
A hard copy FMC is treated as still necessary for initial documentation in the prehospital environment even as electronic medical documentation develops. The publication's own agreement is that "participating nations agree to include a defined set of minimum core medical data elements into nationally developed FMC or to make use of the FMC found in Annex A." A nation may add its own registrations to a nationally developed card, but "cannot exclude any item listed in this STANAG."
The minimum core medical data elements themselves are grouped into a small number of categories covering the casualty's identity, the circumstances of the injury or illness, the clinical assessment made, the treatment given, and the casualty's onward movement. This page does not reproduce that list, the card's layout, or any of its clinical entries or codes: those live in the document itself and in Annex A, which gives an example of the NATO Field Medical Card for a nation that chooses to use it rather than build its own compliant equivalent.
The document is addressed to NATO nations' military medical services, developed through the Committee of the Chiefs of Military Medical Services (COMEDS) and approved by nations in the Military Committee Medical Standardization Board. In practice, "the FMC is intended for use initially by the first responder at the point of injury or as soon as possible and follow the casualty en route," and the treatment facilities that handle the casualty up to Role 1 add to the same record as care continues.
The edition in front of you is Edition B, Version 1, effective on receipt in June 2023. It supersedes Edition A, Version 2, which nations were instructed to destroy on receipt of the new edition.
The Record of Reservations is where cross-recognition is actually worked out, and several nations used it. A number keep a nationally developed card, or another allied casualty-care format already in service, rather than adopting the Annex A template outright, while at the same time recording that they will accept the NATO-format card produced by other nations. Belgium's reservation is a clear example: it continues to use its own template while recording that it accepts the Annex A card from other nations. Italy's records that its army will continue to use its own casualty card while accepting that other nations will use the NATO format or their own national variants. One reservation goes further and reserves the right to decide, under its own national legislation and policy, whether certain identifying data is recorded on the card at all.
None of this weakens the underlying agreement: a nation keeping its own format still commits to carrying the same minimum data elements the document lists, and to recognising a partner nation's FMC when a casualty is handed over.
AMedP-8.1 does not itself set out how long a completed card is kept, who may see it once the casualty leaves Role 1, or how it is transferred between nations' medical services beyond being carried with the casualty. One national reservation notes only that a specific nation's own implementation of certain fields must follow that nation's own legislation and policy on data protection; that is a commitment recorded by one nation in this document, not a rule the document sets for every nation, and it is not a data protection regime in its own right.
AMedP-8.1 does not describe a certification, audit or inspection mechanism, and no organisation can be certified against it. What it describes is a national commitment: a nation that has ratified STANAG 2132 records that its own Field Medical Card, or its adoption of the NATO example in Annex A, carries every minimum data element the document lists. Several nations recorded a formal reservation rather than full compliance at the time of promulgation, which is the document's own way for a nation to state where its practice differs from the minimum set. There is no third party, notified body or accredited certifier involved: it is a matter of what a nation declares to NATO, not something a company is assessed against.
The document is issued under STANAG 2132, which records the nations' agreement to use it. Its own reference list, Annex B, names two further Allied Publications used elsewhere in the same casualty's journey, cited as related documentation rather than as something that must already be in place: AMedP-8.8, the Medical Warning Tag, carried under STANAG 2347, and AAMedP-1.1, Aeromedical Evacuation, carried under STANAG 3204. A national reservation separately mentions Medical Warning Tags under STANAG 2437; Annex B, not the reservation, is the document's own reference list.
AMedP-8.1 is published by the NATO Standardization Office and, like all NATO standardization documents, is free of charge and not sold by NATO or by us. It can be retrieved from the NATO Standardization Document Database or through a national standardization authority.
AMedP-8.1 governs a casualty's own clinical documentation: the Field Medical Card carries a named individual's identity, injury, treatment and movement information as they are handled and evacuated. That is patient data, and ComplyTrain does not manage patient or casualty records. The product is a quality and compliance management system, not a clinical documentation system, and it plays no part in completing, carrying or transmitting the card itself.
Where a compliance programme sits around this document is one step removed from the card itself: the standard operating procedures a medical unit writes for how the FMC is completed and handed over at each stage of the evacuation chain, and the training records that show personnel have been briefed on the minimum data elements the document requires. ComplyTrain can hold and version documents of that kind, the way it does for any procedure a quality system needs to evidence, alongside the internal review records that show a unit's own procedures were followed.
It does not replace the Field Medical Card, the treatment and evacuation chain it supports, or the national medical governance that decides what a nation's own casualty documentation carries. The fit here is limited, and it is worth saying so plainly. For a defence organisation working out which standards sit alongside AMedP-8.1, our standards explorer sets out what else is in the same family; which of them actually applies is a matter for your contract and your customer's quality clause, and we are glad to talk it through.
Tell us how you need to work with AMedP-8.1 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 ratification rather than automatically. The agreement of nations to use this publication is recorded in STANAG 2132, and a nation that has ratified that STANAG commits its own medical services to include the minimum data elements AMedP-8.1 lists. Several nations have also recorded formal reservations against parts of it, which the document itself provides for.
It is the hard copy record AMedP-8.1 is built around: a document that carries a casualty's identity, the circumstances of injury, the clinical assessment, treatment given, and movement information from the point of injury through to a Role 1 medical treatment facility. This page does not reproduce its fields, layout or codes.
Yes. Several nations have recorded reservations keeping a nationally developed card, or another allied casualty-care format already in service, provided it carries the minimum core data elements AMedP-8.1 lists and is still recognised by other nations using the NATO-format card.
AMedP-8.8, the Medical Warning Tag, is a separate publication carried under a different STANAG (2347) and named in AMedP-8.1's own list of references as related casualty documentation. It is not a prerequisite for implementing AMedP-8.1.
Edition B, Version 1, effective on receipt in June 2023. It supersedes Edition A, Version 2, which nations were instructed to destroy.
No. ComplyTrain does not manage patient or casualty records. It can hold the standard operating procedures and training records a medical unit uses to evidence how it handles this documentation requirement, but not the clinical data itself.
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.