Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-9.2
Lead Nations and Troop Contributing Nations negotiating the establishment of a multinational medical unit for a NATO-led operation
AMedP-9.2 supplies the MOU templates and planning aide-memoire NATO nations use to agree command, legal, logistics, finance and information arrangements before standing up a multinational medical unit.
AMedP-9.2, "Guidelines for a Multinational Medical Unit," is a NATO Allied Medical Publication of guidelines rather than a technical specification. Edition A, Version 1 was promulgated in January 2018, effective on receipt, and it supersedes the earlier AMedP-1.3, Edition A, Version 1. Rather than setting technical requirements, it supplies the templates nations use when they agree to establish a Multinational Medical Unit (MMU): a medical treatment facility that more than one nation staffs, equips and funds for a NATO-led operation. Nations' agreement to use this publication is recorded in STANAG 2552, the NATO Standardization Agreement that gives it its force; a specific unit only becomes bound once the nations involved negotiate and sign their own Memorandum of Understanding (MOU) for that mission.
One participating nation takes on the role of Lead Nation, normally providing the bulk of the unit's infrastructure and its first Commanding Officer. The other nations join as Troop Contributing Nations, each supplying a National Medical Contingent of healthcare and support personnel. This is not a document written for a general equipment manufacturer, a software supplier or a certification body; it speaks to the Ministries of Defence negotiating the unit's establishment, and separately to the Lead Nation and Supreme Headquarters Allied Powers Europe (SHAPE) negotiating the Lead Nation's NATO Common Funding arrangements.
Before a multinational medical unit can stand up, the nations negotiating it have to reach agreement in several distinct areas, and the sample MOU in Annex A is built around exactly these headings. Command sets out who commands: full command of contributed personnel stays with their own nation, Operational Command or Control of the unit passes to the Force Commander, and Tactical Control of day-to-day activity sits with the unit's own Commanding Officer. Legal jurisdiction and discipline over each nation's own personnel stays with that nation. Logistics covers how requests for support move between the unit and the nation supplying it, across medical, general and individual logistics. Finance covers how the unit's shared costs are funded, normally pre-financed by the Lead Nation and reimbursed through NATO Common Funding, with a Financial Management Group overseeing multinational-shared spending. Information covers how classified material and clinical records are handled, shared between nations, and eventually returned to national ownership, alongside how the unit reports and communicates once established.
The Annex A template makes explicit what it does and does not settle: it covers "definitions, command and control, jurisdiction, medical considerations, logistics and other support, finance, claims, security and other general principles concerning the responsibilities of Participants," while the detailed work of organising, manning and equipping the unit is left to a subsequent Implementing Agreement negotiated once the MOU is in place. A parallel MOU in Annex B, this time between the Lead Nation and SHAPE, formalises the same broad areas, command, logistics, finance, at the level of the Lead Nation's relationship with NATO: which costs NATO's funding mechanisms can cover, how the Lead Nation reports and invoices, and how any equipment acquired through common funding is owned and eventually disposed of.
The guidelines follow the life of a unit from first planning through to its eventual stand-down, in the document's own terms. Chapter 1 frames the earliest stage: the publication exists to "expedite planning and establishment of an MMU, and establish a common understanding between participant nations." Annex C carries that forward into an aide-memoire of planning considerations for the Lead Nation, organised under headings that include the unit's mission and command and control, force generation and training, national doctrine, personnel welfare, logistics, information management, administration, liaison with other agencies, infrastructure, patient services and force health protection; it was built from earlier operations' lessons learned specifically so a Lead Nation has a starting point for managing the differing requirements and contributions of participating nations. This page does not reproduce its individual planning questions.
Once a unit is established and operating, the same MOU governs its day-to-day running: command and control, logistics requests, financial reimbursement and information handling all continue under the agreements reached at the planning stage, with a Multinational Medical Management Steering Group providing ongoing oversight. Annex D offers examples of non-clinical unit standard operating procedures, covering areas such as casualty reception, facility recall, visitor and detainee handling, waste disposal and quality assurance, that a Lead Nation can adapt for its own operation; the document is explicit these are a model to refine, not a fixed requirement. Annex E does the same for the security of the unit itself, covering threat and alert states and actions on attack. Eventually the MOU's own provisions on withdrawal, termination and the disposal of shared assets govern how a nation's part in the unit, or the unit itself, is wound down.
Annexes C, D and E are working tools rather than narrative requirements: Annex C is a long table of planning questions and cross-references to other NATO publications, Annex D is a set of example standard operating procedures covering casualty handling, security protocols, waste disposal and administration, and Annex E is a camp-security template covering threat states, alert states and guard procedures for detained patients. None of these carry capability figures, staffing levels, bed numbers or clinical detail that belongs on this page; naming what each covers is enough to show the document's structure without turning this summary into a copy of its planning checklist.
AMedP-9.2 is operational and organisational guidance, not a management-system standard. The work it describes, negotiating an MOU, standing up a command structure, and running logistics and finance for a deployed unit, happens between nations and their military staffs, not in a document platform. No certificate attaches to this document, and no software negotiates an MOU or commands a unit on a nation's behalf.
Where evidencing this kind of work does look like familiar compliance work is in the paper trail behind it: version-controlled drafts of the MOU and its Implementing Agreement as they move through negotiation, records of which clauses each Participant has agreed, training and credentialing records showing personnel meet the standards the unit invokes, quality-assurance findings from the unit's own audits, and the supporting documentation behind invoices claimed through NATO Common Funding. ComplyTrain holds that kind of evidence, procedures, controlled documents and records, as an auditable trail, so a nation preparing to lead or contribute to a multinational medical unit has a clear record of what was agreed, and when.
ComplyTrain does not negotiate an MOU, does not provide command and control, logistics or medical care to a deployed unit, and does not determine what is eligible for NATO Common Funding; those decisions stay with the participating nations and NATO's own funding committees. Which standards from the wider medical family a specific mission brings with it is set by the contract and the customer's own quality clause. The standards explorer shows the other Allied Publications and STANAGs in the medical family, and we are glad to talk through how you would document readiness for this kind of work.
Tell us how you need to work with AMedP-9.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.
Nations' agreement to use it is recorded in STANAG 2552, and that ratified commitment gives the templates their standing. A specific multinational medical unit is only bound once the nations involved negotiate and sign their own Memorandum of Understanding for that mission, so whether it applies to a given operation is a question of what a specific MOU says, not a standing obligation.
One participating nation takes on the role of Lead Nation, normally providing the bulk of the unit's infrastructure and its first Commanding Officer, and pre-financing the unit's shared costs for reimbursement through NATO Common Funding. The other nations join as Troop Contributing Nations, each supplying a National Medical Contingent of personnel under the arrangements the MOU sets out.
No. It is procedural and organisational: it supplies the MOU templates and planning tools nations use to agree command, legal, logistics, finance and information arrangements. Clinical protocols and standards of care are established separately, by the Lead Nation in consultation with the participating nations, and are outside this publication's own scope.
AMedP-9.2 describes no evaluation or certification scheme of its own. It directs that the unit, or a nation's contribution to it, be evaluated under STANAG 2560 and AMedP-1.6, the Medical Evaluation Manual, before deployment, unless operational necessity prevents it.
AMedP-9.2's sample MOU sets out the general principles, command and control, jurisdiction, logistics, finance, claims, security and information. It explicitly does not address the detailed arrangements for organising, manning and equipping the unit; those are left to a subsequent Implementing Agreement negotiated once the MOU is in place.
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.