Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-8.2
Military medical treatment facilities treating a patient from another NATO nation, and the national military medical authorities that receive the completed report
AMedP-8.2 sets the minimum information a Basic military medical report must contain when a NATO nation's patient is treated in another nation's hospital, and how that report travels on to their own national medical authority.
AMedP-8.2 is a short NATO Allied Medical Publication with one job: standardizing the minimum information a Basic military medical report has to contain, its own aim being "to standardize the minimum information to be included in a Basic military medical report when patients from one nation are treated in hospitals of other nations and how to handle this information when patients are transferred from one MTF to another military or civilian hospital." It does not set clinical standards of care. It sets what a report must record so that information is "correct and standardized between nations in a NATO operation," and stays usable as a patient moves between allied medical treatment facilities and eventually back to their own nation.
A report is required for both in-patient and out-patient treatment, whenever a patient from one participating nation is treated in a military hospital of another. It is written by the attending physician, authenticated by an officer's name, rank, position and signature, and travels with the patient on every further transfer between military medical installations, or on to a civilian hospital, or back to their parent nation.
Participating nations "agree to the details herein," and that agreement is what gives the document force between them; the cover carrying it is STANAG 2348. For a military medical treatment facility, the practical trigger is clinical rather than contractual: a patient of another participating nation arrives for treatment, and the reporting practice needs to already be running by then. AMedP-8.2 itself does not say what happens if a facility does not have one running; it simply fixes what the report contains once one is prepared.
The document groups the minimum content into broad categories rather than a single free-text narrative: information identifying the patient, information about the medical treatment facility that prepared the record, clinical information about the treatment given, and authentication of who wrote and signed it. This page does not reproduce the individual items under each heading; a compliance summary is the wrong place for a patient's clinical record. It does say plainly that "all personal information therein will be treated like all other medical information with respect to confidentiality," and it also asks for a brief independent summary of the medical history and treatment, written in English or French, to travel ahead of the full record to the next level of treatment. Where a Field Medical Card or Patient Evacuation Tag has also been prepared, that accompanies the report rather than replacing it. A report can be issued electronically, on paper, or both.
The record is forwarded to the patient's own national military medical authority once treatment is completed, the patient is discharged or dies, or the record meets the criteria for retirement. Annex A lists each nation's authority for this purpose, and the document allows that list to be corrected administratively: changes to it "may be performed as editorial changes as appropriate, without any need for a new ratification process," on the basis that "each nation has the responsibility for providing the correct data to the Custodian Nation," which forwards it on for the record to be kept current. That administrative route covers only the Annex A list, not the substance of what a report must contain.
The document names STANAG 2132 as covering the procedures for transferring the information it discusses between facilities: AMedP-8.2 fixes what a report contains, STANAG 2132 governs how it moves. It does not describe any certification, audit or inspection mechanism of its own; the only formal mechanism it names is a nation's own recorded reservation against specific report content, and the administrative correction of Annex A described above.
AMedP-8.2 is an operational and administrative NATO standard, not a management-system one, and the substance of it, writing, authenticating and handing off a patient's medical report, happens inside a military medical treatment facility's own clinical and administrative process, not in software. ComplyTrain does not handle patient records, and the fit here is limited to the paperwork around that practice: a facility's own procedure describing how it prepares a Basic military medical report and hands it off on transfer, a training record showing attending physicians and records staff have been briefed on the requirement, and evidence that admission and discharge procedures reference AMedP-8.2 and STANAG 2132 correctly.
What ComplyTrain does not do: it does not create, store or transmit the medical report or any patient clinical data, and it is not a channel for moving patient records between facilities. Which standards actually apply to a given operation or contract is set by the nations and the command involved, not by this page. The standards explorer shows what else sits alongside AMedP-8.2, and we are glad to talk through what a specific requirement is asking for.
Tell us how you need to work with AMedP-8.2 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 the STANAG that covers it, recording participating nations' agreement "to the details herein." For a military medical treatment facility, it becomes relevant in practice whenever a patient from another participating nation needs treatment, rather than through a separate contract or tender.
No. ComplyTrain does not create, store or transmit patient medical reports or clinical data. Where it can help is with the surrounding paperwork, such as the facility's own procedure and training records for the reporting requirement, not the patient record itself.
AMedP-8.2 sets the minimum information a Basic military medical report must contain. STANAG 2132, which AMedP-8.2 names directly, covers the procedures for transferring that information between facilities. One fixes the content, the other the transfer mechanism.
No. The document describes no certification, audit or inspection scheme against itself. The only mechanisms it names are a nation's own recorded reservations against specific content and the administrative correction of the Annex A list of national military medical authorities.
In the document's own broad terms: information identifying the patient, information about the treating medical facility, clinical information about the treatment given, and authentication of who completed the record, plus a short English or French summary to travel ahead of it. This page does not reproduce the individual items the document lists, since that is the report's clinical content rather than compliance information.
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.