Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-1.7
NATO nations' armed forces and, where a reservation names it, a Ministry of Health, declaring and evaluating their own deployed medical facility and module capabilities
AMedP-1.7 is NATO's Capability Matrix, naming by module and echelon what a deployed military medical facility can provide, without prescribing how, and sitting under STANAG 2560 alongside AMedP-1.6 and AMedP-1.8.
AMedP-1.7 is NATO's Capability Matrix, an Allied Medical Publication that names, module by module, what a deployed military medical facility is expected to be able to provide, at whichever echelon a nation has committed to, without setting out how a module actually delivers that care. Edition A, Version 2 was promulgated on 9 September 2022, is effective upon receipt, and supersedes Edition A, Version 1, which nations were instructed to destroy.
The document is approved for use by NATO nations through the Military Committee Medical Standardization Board, and it speaks throughout in terms of a deployed medical facility or module, never a supplier, a manufacturer or a certification body. NATO's letter of promulgation records, in its first paragraph, that nations' agreement to use this publication is recorded in STANAG 2560; it reaches a company only at one remove from that agreement, where an organisation runs or supports a deployed medical module under contract to a nation and the contract is what brings this document to it, not the publication itself.
Clause 1 places AMedP-1.7 under STANAG 2560 together with two companion publications, AMedP-1.6 and AMedP-1.8. Clause 2 puts the matrix first in that family: it is the template AMedP-1.6 draws on for the key questions asked per module, in that publication's Annex E, and the template AMedP-1.8 draws on to describe the skill sets expected per module. A detailed description of medical capabilities lives in AMedP-1.8, not here; this document's job is to name the modules and the echelon each can sit at, and leave the detail to the two publications built on top of it.
Elsewhere it is cited alongside STANAG 2879 and AMedP-1.10, repeatedly, as the reference for how a module responds to a major incident or mass-casualty situation. That is context for each module, not a requirement the matrix itself imposes. Spain's own national reservation separately cites STANAG 2136 and AMedP-4.9 for how it evaluates drinking-water potability within the medical supply module; neither appears in the document's general text.
AMedP-1.7 groups deployed medical support into named modules and assigns each a capability code drawn from NATO's own Bi-SC Capability Codes and Capability Statements, dated 29 July 2020 and cited in clause 3. For every module it gives a short core capability description and marks which echelon, from Role 1 through Role 4, the module can sit at. That structure, not the content of any one module, is what the rest of the series is built on. This page does not reproduce the module descriptions, the capability codes or the echelon assignments the matrix carries: a reader who needs that detail works from the document itself, not from a summary of it.
Several nations recorded reservations when this edition was promulgated, and together they show that ratifying STANAG 2560 is not the same as adopting the matrix whole. Albania and Croatia record that they apply the document only up to Role 2. Latvia applies it to Role 1 units only, and excludes CBRN capacity even from that. Montenegro records that its limited capacities mean it has not developed Role 2 or Role 3 medical support at all. Turkey's reservation records that Role-2 and above medical support is conducted under the responsibility of its Ministry of Health. Germany's reservation records a specific disagreement with how one module frames a CBRN-related capability, without this page repeating the clinical detail behind it. The current, complete list of reservations is held on the NATO Standardization Document Database, not fixed in this text: the promulgation letter itself says as much.
No one is certified or assessed against AMedP-1.7. It names no accredited certification body, no notified body and no government quality-assurance representative; what it describes instead is a nation stating and evaluating its own medical modules and facilities against the matrix, most visibly in the reservations it records at the point of ratification.
NATO publishes AMedP-1.7 free of charge through the NATO Standardization Document Database. ComplyTrain does not sell it or hold a copy for distribution; the NSDD listing for AMedP-1.7 is the source.
AMedP-1.7 addresses nations and the modules they field, not a supplier directly, so there is no compliance-software mapping to claim here. Where a company runs or supports a deployed medical module or facility under contract to a nation, the contract or tasking will usually name a module and an echelon from this matrix as the standard the work is measured against. ComplyTrain gives that kind of operation a controlled place to hold the procedures, training and competency records, and the audit trail a customer or reviewing authority would ask to see, and to show which of them map to which contracted module.
What ComplyTrain does not do: it makes no clinical or capability determination, and it does not evaluate whether a facility or module meets a given echelon. That judgement belongs to the customer nation and, where a national reservation applies, to whatever domestic process the reservation describes.
Which capability codes and echelons actually apply to a given contract is set by that contract and the customer's quality clause, not by this page. The standards explorer shows what sits alongside AMedP-1.7, AMedP-1.6, AMedP-1.8 and STANAG 2560; if you are working out what a contract's medical-module clauses require, talk to us.
Tell us how you need to work with AMedP-1.7 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 by itself. AMedP-1.7 is covered by STANAG 2560, and a NATO nation is bound once it has ratified that agreement, with the option to ratify with reservations, as several nations have done for this edition. Whether it affects your organisation depends on the contract or tasking that names a module or echelon from it, not on the publication existing.
AMedP-1.7 is the Capability Matrix: it names the modules and the echelon each can sit at. AMedP-1.6 uses it as the template for the key questions asked per module in that publication's Annex E, and AMedP-1.8 uses it as the template for the skill sets expected per module. The detailed description of medical capabilities lives in AMedP-1.8, not in AMedP-1.7.
No. It carries module names, capability codes and which echelon each module can sit at; it does not set out staffing, bed counts, timelines or equipment. This page does not reproduce that structure either, for the same reason: it is a matrix meant to be read in the document itself, not summarised into planning guidance.
Yes, and several already do. A nation ratifies STANAG 2560 and can record a reservation against this edition limiting the echelon it applies the matrix to, or excluding a specific capability. Albania, Croatia, Latvia, Montenegro and Turkey all have recorded reservations, and the current list is held on the NATO Standardization Document Database rather than fixed in this document.
No. It names no certification scheme, accredited body or notified body. A nation states and evaluates its own medical modules and facilities against the matrix; nothing in the document creates a certificate a company or a facility can hold.
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.