Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJMedP-3
NATO commanders and their medical and intelligence staffs who plan and conduct campaigns, operations and exercises
AJMedP-3 is NATO's doctrine for medical intelligence, implementing STANAG 2547, and it addresses NATO commanders and their medical and intelligence staffs rather than a supplier or company.
AJMedP-3, Allied Joint Medical Publication 3, is NATO's doctrine for medical intelligence. The document defines medical intelligence as intelligence "derived from medical, bio-scientific, epidemiological, environmental and other information related to human or animal health," and its purpose is to describe to commanders and staff what medical intelligence can do for them. It implements STANAG 2547, the NATO agreement under which nations commit to running a medical intelligence programme: AJMedP-3 is the doctrine that programme runs on, not a separate agreement nations ratify on their own account.
The document is explicit that it "is principally for use by NATO commanders and their medical and intelligence staffs in the planning and conduct of campaigns, operations, and exercises," while also having "utility for a wide range of other users, especially for medical personnel at every level of command." It focuses mainly on the operational level, as the interface between individual Allied and multinational forces. It also extends to coalition settings: it applies equally to "operations conducted by a Coalition of NATO and non-NATO nations" under a NATO-led Combined Joint Task Force, or to European-led operations using NATO assets and capabilities. It does not address a supplier, a manufacturer or a national procurement authority, and it creates no obligation that a company holds directly.
AJMedP-3 does not stand alone. Its Foreword places it under NATO's intelligence policy in AJP-2.0, which sets out how the intelligence cycle works, and under NATO's medical policy in AJP 4.10, which the Foreword calls the "capstone" document for medical guidance. It also sits under a Military Committee policy cited as MC 65-7. MC 326 is cited as setting the role of medical intelligence within the force protection concept, and Bi-SC Directive 65-7 is cited as providing the conceptual background for medical intelligence management and the production of doctrine and training within NATO. A supporting document, SRD-1 to AJMedP-3, the "Guide to medical intelligence handbook," elaborates the framework this publication sets out. None of MC 65-7, MC 326, Bi-SC Directive 65-7, AJP-2.0 or AJP 4.10 is in our catalogue, so they are named here without a link.
At subject level, AJMedP-3 covers three things: definitions, organisation, and the place of medical intelligence in planning. It fixes medical intelligence, medical information, health hazard, health threat and health risk as distinct working terms, and it is explicit that medical intelligence is the analysed product, while medical information is the underlying data "that has not been analysed for intelligence purposes." It describes medical intelligence as relevant to the assessment of health risks, the formation of medical estimates, preventive medicine planning, and the ongoing management of medical support, across the strategic, operational and tactical levels of planning, for the range of health hazards, including disease, that a deployed force can meet in an area of operations. It sets out a Medical Intelligence Officer function within the NATO Command Structure: a dedicated full-time post at ACO/SHAPE and Joint Force Command level, and an additional duty at tactical or service command level, working alongside the intelligence (J2) staff.
The document stays at doctrine and organisation. It states plainly that "NATO member nations will not collect medical intelligence on other NATO members," a restriction worth noting because it runs against the assumption that medical intelligence means watching anyone of interest, allies included. It does not itself set out disease or hazard specifics, threat assessments, or the methods by which medical intelligence is collected: those questions belong to the classified and operational products the doctrine describes the use of, not to this publication.
AJMedP-3 names no certification, audit or inspection scheme, and no body is described as assessing a nation's or a company's compliance with it. The only review mechanism in the document is NATO reviewing its own text: it is "a living document" reviewed regularly under NATO's standardisation procedures, with the Military Committee Medical Standardisation Board holding tasking authority over updates. That is not an assessment of anyone's conformity to the doctrine.
AJMedP-3 is a policy and organisational document for NATO's own command structure. It does not create a scheme a company registers for, a deliverable a contract specifies, or evidence an auditor asks a company to produce, so there is no compliance mapping ComplyTrain, or any tool, can honestly offer against AJMedP-3 itself. What it explains is why the medical intelligence programme under STANAG 2547 exists, and how it fits alongside NATO's wider intelligence and medical doctrine.
Where a company does carry a contractual medical, force health protection, or medical surveillance obligation on a NATO-related programme, that obligation comes from the specific tasking, standard or contract clause that names it, not from AJMedP-3. Documented procedures, training records and audit evidence for that kind of obligation are the general shape of work ComplyTrain holds, wherever it comes from; ComplyTrain does not implement AJMedP-3 itself, because the document sets out nothing addressed to a company for it to hold.
Which NATO standards and doctrine apply to a given contract, and what evidence a customer's quality clause expects, is set by the contract, not by us. Use the explorer to see the STANAG and doctrine documents AJMedP-3 sits alongside, and talk to us if a tasking or contract has pointed you at NATO medical intelligence doctrine and you are working out what it does, and does not, mean for your own obligations.
Tell us how you need to work with AJMedP-3 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 directly. AJMedP-3 is addressed to NATO commanders and their medical and intelligence staffs, and it implements STANAG 2547, an agreement between NATO nations. It creates no scheme a company registers against. Where a company does have an obligation on a NATO-related programme, it comes from a specific contract clause or tasking, not from this document.
STANAG 2547 is the NATO agreement by which nations commit to running a medical intelligence programme; AJMedP-3 is the Allied Joint Medical Publication that sets out the doctrine for how that programme works. The Foreword states that AJMedP-3's purpose is to implement STANAG 2547.
No. The document names no certification, audit or inspection scheme, and no body assesses an organisation's compliance with it. The only review it describes is NATO's own periodic review of the document's content.
Edition A, Version 2, promulgated in August 2020. The document does not state what an earlier version of Edition A covered.
No. It defines medical intelligence, medical information, and related terms, and describes where medical intelligence fits into planning and command structure. It does not set out disease or hazard detail, threat assessments, or collection methods; those belong to the operational products the doctrine describes the use of.
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.