Start a free trial
Menu

AMedP-4.1

AMedP-4.1 deployment health surveillance

National military medical services running deployment health surveillance for NATO forces, not companies

AMedP-4.1 is NATO doctrine for monitoring the health of deployed forces, binding through STANAG 2535 and addressed to national medical treatment facilities and NATO's own command chain.

Edition
B
Published
2026-05

What it is

AMedP-4.1, Deployment Health Surveillance, is the NATO Allied Medical Publication setting out doctrine and policy for monitoring the health of deployed NATO forces. Its stated scope is "health surveillance (i.e. monitoring of health status, follow-up of health indicator trends over time and the detection of exceptional events or outbreaks in the context of NATO deployments)." The aim is to detect a public health incident or outbreak early, feed that information to commanders so any risk is understood, and trigger an appropriate response. Nations record their agreement to use it in STANAG 2535, so it binds the way NATO doctrine generally does: through that ratified agreement, not as a stand-alone specification a company signs up to. Edition B, Version 1 was promulgated in May 2026 and supersedes Edition A, Version 2. Its numbering reflects that it provides supporting doctrine beneath AJMedP-4, Force Health Protection, which in turn supports the medical keystone doctrine AJP-4.2, Allied Joint Doctrine for Medical Support.

The document sets out two reporting mechanisms. EpiNATO-2 is a weekly morbidity-surveillance system, described as "a NATO sponsored morbidity surveillance system which is a keystone tool to be managed by the medical staffs of deployed forces at all levels." Near Real Time Surveillance (NRTS) processes the first signs and symptoms of a case as they are recorded, rather than waiting for a clinical diagnosis, to give an earlier warning of a natural or deliberate outbreak. A unit using NRTS does not also file a separate EpiNATO-2 report for the same encounter, since NRTS can generate that data automatically.

Who reports, and up which chain

Each "medical treatment facility (MTF) deployed within a theatre of operations (TOO) that treats NATO command forces personnel shall report data into NATO deployment health surveillance (DHS) systems", on the reporting rhythm set for that mission. The Medical Director or Medical Advisor for the theatre, usually acting through a subordinate preventive medicine officer, has to keep standing operating procedures current, meet reporting deadlines, and pass the data up the chain "in a uniform format and not corrupted." NATO's Force Health Protection (FHP) Branch, based in Munich, analyses what is reported and returns feedback down the same chain to the reporting facilities, while also passing findings up to Allied Command Operations, which holds overall oversight and specifies the surveillance requirements for an operation.

This chain is a national and NATO command responsibility, not a supplier one. Training the personnel who carry out this surveillance "is a national responsibility," delivered in practice through joint courses run by the NATO Centre of Excellence for Military Medicine and a named French training centre. The document is explicit that the health status of NATO personnel before and after a deployment is handled separately, under STANAG 2235/AMedP-4.8, because deployment health surveillance itself "does not collect individually identifiable information" and so "is not a substitute for National operational medical records which remain the primary means to ensure the continuity of care of individual personnel."

What the reporting cycle involves

The document works through a six-step process rather than a single form: recording a health event in the medical record, an anonymising and summarising step before anything is transmitted, declaring the facility's activity for the reporting period, collecting and validating reports up through the command hierarchy, analysing the data and preparing feedback, and disseminating that feedback back to the facilities that reported. Analysis is meant to establish whether reported cases are running higher than expected and to support trend review over time, and its output goes to commanders "at all tiers of the chain of command," not only to medical staff.

A reporting population, or "denominator," underlies every rate calculated from the data, and the document is careful about what it is not: it excludes civilians, and it is not the same as the wider population at risk, which can include people an MTF treats but is not responsible for reporting on. For operational security reasons, the document accepts that reported troop numbers "should be reasonably accurate but not exact" rather than precise, since health surveillance is retrospective and the underlying numbers are already out of date by the time they are analysed.

Standards it sits alongside

AMedP-4.1 is covered by STANAG 2535, and provides supporting doctrine beneath AJMedP-4 (Force Health Protection, covered by STANAG 2561), which in turn supports AJP-4.2, Allied Joint Doctrine for Medical Support. Surveillance draws on the medical intelligence doctrine in AMedP-3.2 and AJMedP-3, and Force Health Protection itself sits inside the broader concept defined in AJP-3.14, Allied Joint Doctrine for Force Protection. The separate matter of individual pre- and post-deployment health assessment is covered by STANAG 2235 / AMedP-4.8.

A longer list of related NATO medical and doctrine publications appears in the document's own Annex D: AMedP-4.2 (deployment pests and disease vectors), AMedP-8.1 (documentation for initial medical treatment and evacuation), AMedP-4.9 (water quality during operations), STANAG 2228 (medical support doctrine), AMedP-5.1 (patient data exchange format), AMedP-8.2 (basic military medical report), ATP-3.8.1 (specialist CBRN defence capabilities), AMedP-7.4 (deployable outbreak and incident investigation teams), AJMedP-1 (allied joint medical planning doctrine), AMedP-5.2 (data interchange between health information systems), AMedP-9.2 (guidelines for multinational medical units), AJMedP-5 (medical communications and information systems), AJMedP-7 (allied joint CBRN medical support doctrine), and AMedP-7.6 (medical support to CBRN defensive operations). Each is a cross-reference naming where more detailed doctrine lives, not a requirement AMedP-4.1 imposes directly.

How it is checked

The document names no certification, notified-body or self-declaration scheme, and no accredited body audits a company against it. Checking is an internal NATO process: nations are expected to meet the surveillance requirements Allied Command Operations mandates and to maintain data quality, and the Force Health Protection Branch "may provide an audit function if tasked by ACO" to do so, which is an optional activity run at ACO's direction rather than a routine external audit. The closest thing to a formal checkpoint is the reservation a nation records when it ratifies the STANAG; four nations did so for this edition. There is no route by which a supplier or contractor is certified against AMedP-4.1.

How we help

AMedP-4.1 is operational doctrine for a NATO command's own medical staff, not something implemented in software. The work it describes - recording a patient encounter, compiling a weekly EpiNATO-2 report, running the NRTS tool, analysing the data and returning feedback - happens inside national medical treatment facilities and NATO's Force Health Protection Branch. ComplyTrain does not run deployment health surveillance, analyse health data or make public-health decisions; that stays with the medical staff and commanders the document describes.

Where an organisation supporting a deployment has to show that its own side of a health-protection-related requirement was met, ComplyTrain can hold the evidence trail behind it: the procedure describing how the requirement is carried out, the training record for staff who completed a required briefing, and the record that a reporting or process obligation was satisfied and can be produced on request. Which parts of this doctrine apply to a given contract, and at what tier, is set by the contract and the customer's quality clause, not by this page. If your organisation is working out what a deployment-health-surveillance-related clause means for its own procedures and evidence, we can talk through what a workable structure looks like.

Standards it references

Questions

Is AMedP-4.1 mandatory?

It binds through ratification, not on its own account: nations record their agreement to use it in STANAG 2535. A nation that has ratified STANAG 2535 has committed its forces to this doctrine; a company is never a party to that agreement and meets any part of it only where a specific contract says so.

Can a company be certified against AMedP-4.1?

No. The document sets out no certification, notified-body or self-declaration scheme. Checking runs inside NATO's own command chain, through national reporting and an optional audit function the Force Health Protection Branch may run if tasked by Allied Command Operations, not through an accredited body auditing a company.

Does deployment health surveillance collect personal medical data?

No. The document states that it "does not collect individually identifiable information" and is not a substitute for a service member's own national medical record. Individual pre- and post-deployment health assessment is handled separately, under STANAG 2235/AMedP-4.8.

What is the difference between EpiNATO-2 and NRTS?

EpiNATO-2 is a weekly report a medical treatment facility compiles from its clinical activity. NRTS captures signs and symptoms closer to real time, at the point of a patient encounter, to give earlier warning of a possible outbreak. A facility using NRTS does not also file a separate EpiNATO-2 report for the same data.

What edition is current?

Edition B, Version 1, promulgated in May 2026, is the current edition. It superseded Edition A, Version 2, which nations were instructed to destroy according to their local procedure for document destruction.