Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-7.4
Nations that establish or contribute a Med-DOIIT, and the team itself once tasked by an Operational Commander
AMedP-7.4 is NATO doctrine for establishing and deploying a Medical Deployable Outbreak and Incident Investigation Team (RDOIT, Med-CIIT or Med-RIIT), which nations agree to use under STANAG 2551.
AMedP-7.4 is the NATO Allied Medical Publication that sets out the concept and minimum requirements for nations to establish and deploy a Medical Deployable Outbreak and Incident Investigation Team (Med-DOIIT), fielded as one of three specialist configurations depending on the trigger: a Rapid Deployable Outbreak Investigation Team (RDOIT), a Medical Chemical Incident Investigation Team (Med-CIIT), or a Medical Radiological Incident Investigation Team (Med-RIIT). In the document's own words, the team's mission is "to provide initial reachback advice (before any deployment) and/or rapidly deploy to an area of operations" in order to support the investigation of a suspected or confirmed outbreak or CBRN incident, provide operational and clinical advice, enhance deployed medical capabilities, support patient care and maintain operational effectiveness. Nations' agreement to use the publication is recorded in STANAG 2551, which is how AMedP-7.4 acquires force: the STANAG is the agreement, and this publication is the doctrine it covers. Edition B, Version 2 is described in the document's own summary of changes as "an editorial update", current from June 2026, and it superseded Edition B, Version 1 on receipt.
AMedP-7.4 is written to give "medical personnel, CBRN defence specialists and Command staff" a consistent understanding of a Med-DOIIT's mission, and it is addressed to the nations that create or contribute one. It does not name a commercial supplier, manufacturer or notified body as an addressee. As with any NATO standardization agreement, ratification and implementation are separate national steps. Once a nation has agreed to the framework, the mechanism that actually moves a team is operational: deployment is "initiated upon request by the Operational Commander or higher-level authority through the chain of command, following medical advice", not a fixed compliance date. The framework and concept "apply in peace, crisis and conflict, including Article 5 Operations as well as Non-Article 5 Operations", though any contribution to identifying the cause of an outbreak or incident stays "constrained by the Contributing Nation's legal framework for direct support to forensic and attribution missions."
Once deployed, a Med-DOIIT comes under the Operational Control of the Operational Commander, exercised through a Medical Advisor or Command Surgeon: the Team Leader is the team's point of contact with Command, and the document states plainly that "Med-DOIITs shall operate, on behalf of the Operational Commander, by supporting the Medical Advisor/Command Surgeon." Its tasking is bounded to the Commander's intended end state agreed at activation, and any change to the mission needs agreement from the Operational Commander, the Medical Advisor, Allied Command Operations and the contributing nations. Reporting runs the same way: initial findings "must be available to all participating nations," the team may interact with or report to bodies such as the United Nations, the World Health Organization, the International Atomic Energy Agency and the Organization for the Prohibition of Chemical Weapons as authorised by the Operational Commander, and any exchange of information has to go "through the agreed national or NATO chain of command." Separately from anything this publication itself creates, the document notes that Med-DOIITs and NATO nations "are bound by their legal obligation under the International Health Regulations to report outbreaks or incidents that may constitute a Public Health Emergency of International Concern", a duty it says should run "through the most appropriate reporting chain" without compromising operational or personal security.
An end-state and its criteria are defined when a Med-DOIIT is activated, and recovery includes a formal report to the Medical Advisor and Commander. Final findings go to participating nations and the relevant NATO command through the chain of command, and, subject to security and legal limits, may be shared further with partner nations and international organisations the same way. A post-operational report, including lessons identified, is generated by the Team Leader and forwarded to NATO's Joint Analysis and Lessons Learned Centre and the relevant Centre of Excellence.
AMedP-7.4 gives each of the RDOIT, Med-CIIT and Med-RIIT configurations its own chapter of team composition, technical roles, equipment and activation timelines, and covers sampling, laboratory and treatment detail in depth. That is operational and clinical substance for the people fielding and running these teams; it belongs to the document itself and, for patient management specifically, to its companion AMedP-7.1, not to a page like this one. AMedP-7.4 also names no certification scheme for a Med-DOIIT, an RDOIT, a Med-CIIT, a Med-RIIT or the nation that fields one. The one accreditation-shaped requirement in the text sits with a supporting reachback laboratory rather than with the team: "RBL must comply with the medical laboratory international standards (ISO 15189, 15190 and 17025)." That is an accreditation the laboratory holds against those ISO standards, not a certification of AMedP-7.4 itself.
AMedP-7.4 sits under STANAG 2551, its cover. It points to AMedP-7.1 for medical management of CBRN casualties, AMedP-1.10 for managing a major incident before a Med-DOIIT is activated, AMedP-7.5 for CBRN casualty estimation, AJMedP-7 for the wider CBRN medical doctrine it sits alongside, AMedP-7.6 for a commander's guide to CBRN defensive medical support, and AEP-66 for NATO's sampling and identification handbook. It cites AJP-3.8 for CBRN identification confirmatory levels and ATP-45 for guidance on toxic industrial hazard incidents. Most of these are pointed to as further reading. STANAG 2294 and ACIEDP-01 are the exception: a Med-DOIIT must "have an appropriate level of IED preparedness in accordance with" them, invoked as a training standard rather than background material. A reachback laboratory must separately comply with ISO 15189, ISO 15190 and the laboratory-competence standard our catalogue holds as ISO/IEC 17025, which AMedP-7.4 itself cites in the shorter form "ISO 17025".
AMedP-7.4 is operational doctrine for a deployable military capability, not a management-system standard, so the honest shape of help follows from that: activating a team, tasking it, running an investigation and reporting the outcome happens in the field under an Operational Commander, not in software. Where an organisation supports this readiness, for example by supplying training, equipment or reachback laboratory services to a nation's Med-DOIIT programme, ComplyTrain gives it somewhere to hold the paperwork a customer or contract actually asks for: training and clearance records for personnel who could be tasked, designation records for the reachback laboratory arrangements the document treats as a precondition of deployment, and records of after-action reports and lessons identified.
ComplyTrain does not activate or command a Med-DOIIT, does not run or direct an outbreak or incident investigation, and does not decide what gets reported to a national authority or an international organisation; those decisions stay with the Operational Commander, the Medical Advisor and the contributing nations.
Which standards actually apply to a given piece of supporting work is set by the contract and the customer's quality clause, not by this page. See the standards explorer for what sits alongside AMedP-7.4, and talk to us about the evidence trail behind a contract that touches it.
Tell us how you need to work with AMedP-7.4 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.
No. AMedP-7.4 binds nations, which agree to use it by ratifying STANAG 2551. A company meets it only indirectly, where a military customer's own readiness programme or a contract built on it calls for something the publication describes, such as training records or reachback laboratory arrangements.
They are the three specialist configurations of a Med-DOIIT that AMedP-7.4 covers: an RDOIT responds to an outbreak or biological incident, a Med-CIIT to a chemical incident, and a Med-RIIT to a radiological or nuclear incident. Which one is activated depends on the trigger, and elements of one can support another where the cause is uncertain.
Edition B, Version 2, promulgated in June 2026 and described in the document's own summary of changes as an editorial update. It is effective on receipt and superseded Edition B, Version 1.
No. AMedP-7.4 names no certification, audit or inspection scheme for a Med-DOIIT or the nation that fields one. The one accreditation it mentions belongs to a supporting reachback laboratory, held against ISO laboratory standards, not against this publication.
Once deployed, it operates under the Operational Control of the Operational Commander through a Medical Advisor or Command Surgeon. Findings go to participating nations and the relevant NATO command through the chain of command, and, where authorised, to international organisations; separately, nations carry their own reporting duty under the International Health Regulations for outbreaks or incidents that could be a Public Health Emergency of International Concern.
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.