Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-8.13
NATO nations' deployed medical services, and the dental officers, oral surgeons and assistants they license, delivering dental and maxillofacial care at Role 1 to Role 3
AMedP-8.13 sets out, by Role of medical support, the extent of dental and maxillofacial treatment NATO nations agree to provide during deployment, without fixing how a nation staffs or equips it.
AMedP-8.13 is a NATO Allied Medical Publication - the technical layer beneath a STANAG cover - that sets out, Role by Role, the extent of dental and maxillofacial treatment a nation's deployed medical support is expected to provide. Its own aim is "to describe the different oral health care modules at the different medical roles in order to ensure interoperability and interchangeability related to the dental and maxillofacial treatment during deployment." It covers Role 1 through Role 3 of the deployed medical support chain and states plainly that "every higher role includes all the lower role's capabilities": what Role 3 is expected to provide already assumes everything Role 1 and Role 2 provide beneath it. What each Role actually has to be able to do, against capabilities, outcome, objective, personnel and equipment, is worked out in an annex this page does not reproduce - it is the operational planning detail a medical service works from directly, not something a summary should flatten into marketing language.
Nations' agreement to use AMedP-8.13 is recorded in STANAG 2453: "The agreement of nations to use this publication is recorded in STANAG 2453." AMedP-8.13 is the technical content; the STANAG is what commits a nation to it. For an organisation, the route in is rarely the STANAG itself: it is a nation's own force-generation process for a deployment, or a contract or tasking for a deployed medical treatment facility that points to this publication. Edition B, version 1 (October 2024) is effective on receipt and supersedes Edition A, version 1, which nations were directed to destroy under their own local document-destruction procedure; the document itself does not say what changed between the two editions.
At this promulgation, a number of nations recorded formal reservations against specific provisions - the document's own record of reservations notes that "the reservations listed on this page include only those that were recorded at time of promulgation and may not be complete." The reservations range from a service not having deployed a given dental capability to a nation's timetable for full implementation remaining open, which is a useful reminder that ratifying AMedP-8.13 and a nation's armed forces actually holding every capability it describes are two different things. AMedP-8.13 also points onward once: "AMedP-1.17 describes the necessary skills sets for each capability," so where this document fixes the extent of treatment expected at each Role, AMedP-1.17 is the companion document for the skill sets behind delivering it. Separately, one nation's reservation on first-aid training refers a reader to "the UK Reservation on STANAG 2122" rather than restating it here - that is a national annotation, not a reference AMedP-8.13's own body makes.
Beyond its short aim and general statement, AMedP-8.13 is essentially one annex: "for each role the modules are described in Annex A with corresponding capabilities, outcome, objective, required personnel and equipment." That table, Role by Role, is the substance of the document and the detail an organisation actually plans and staffs against. This page does not restate it, because doing so would either drop the qualifications the document attaches to each line or compress a Role-by-Role table into something that says less than the original. What is safe to take from it without the table itself is the shape: capability accumulates upward through the Roles, and the document treats that accumulation as "the basic principle" its modules are built on.
What AMedP-8.13 does fix, in Chapter 1 rather than the annex, is the vocabulary the rest of the document uses: a Dental Officer is "person licensed in accordance with his national legislation to perform dental care and/or dental surgery"; an Oral Surgeon is a Dental Officer additionally licensed for oral surgery; an Oro-Maxillofacial Surgeon is "specialist licensed in accordance with his national legislation to perform surgery in the oro-maxillofacial area"; and a Dental Assistant and an OMF Surgical Assistant support them. Every one of these is an individual, national licence, not a scheme AMedP-8.13 itself runs.
AMedP-8.13 names no certification, audit or inspection scheme, and nothing in it describes NATO or any other body checking a nation's or a provider's compliance with it. Whether a deployed dental capability actually matches what a Role commits to is a matter for the contracting nation's own military medical oversight, not a scheme this document sets up to test. The personnel it defines are licensed individually under each nation's own legislation; that is a professional qualification held by a person, not a certificate an organisation can hold against this document.
AMedP-8.13 is an operational and technical NATO standard, not a management-system one, and the substantive work - deciding what Role of dental capability a deployment needs, staffing and equipping it, and delivering the care itself - happens in a nation's medical services and dental units, not in software. Where ComplyTrain fits is the evidence trail around that work: the procedure or instruction that translates a Role's requirement into a unit's own planning, the training and licensing record showing a Dental Officer, Oral Surgeon, Oro-Maxillofacial Surgeon or assistant holds the licence AMedP-8.13's own definitions describe, and the document control around a national implementation instruction or a contract that invokes AMedP-8.13 or its companion publications.
What ComplyTrain does not do: it does not deliver dental or maxillofacial care, decide what Role of capability a deployment needs, or license a dental officer or surgeon. Which of AMedP-8.13 and the standards that sit alongside it applies to a given contract or tasking is set by that contract and the customer's own quality clause, not by this page. The standards explorer shows what else sits alongside AMedP-8.13, and we are glad to talk through what a specific tender or requirement is asking for.
NATO publishes AMedP-8.13 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-8.13 is the source.
Tell us how you need to work with AMedP-8.13 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 2453, which records nations' agreement to use the publication. A number of nations recorded reservations against specific provisions at this edition's promulgation, so ratification and full implementation are not the same thing. For an organisation, it typically arrives through a nation's own force-generation process or a contract tasking a provider to support a deployed medical treatment facility.
No. AMedP-8.13 describes no certification, audit or inspection scheme of its own. The personnel it defines are licensed individually by each nation under its own legislation, and that licence belongs to the person, not to a company or provider organisation.
AMedP-8.13 sets out the extent of dental and maxillofacial treatment expected at each Role of medical support. AMedP-1.17 is the companion document that describes the skill sets needed behind each capability AMedP-8.13 names.
The document does set out required personnel and equipment against each Role in its annex, but this page does not reproduce that table; it is the operational planning detail an organisation works from directly rather than a summary point.
Edition B, Version 1 (October 2024) is effective on receipt and supersedes Edition A, Version 1, which nations were directed to destroy under their own local document-destruction procedure. AMedP-8.13 does not itself describe what changed between the two editions.
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.