Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2348
National military medical and standardization authorities implementing NATO's basic military medical record requirement
STANAG 2348 is NATO's agreement committing ratifying nations to implement AMedP-8.2, the standard for the basic military medical record prepared when an allied patient is treated in another nation's military hospital.
STANAG 2348 is the NATO standardization agreement that gives force to AMedP-8.2, Edition B, the Allied medical publication for the Basic Military Medical Record. A STANAG is not itself a technical specification: it is the agreement by which NATO nations commit to implement one, and the actual content sits in the Allied Publication it covers. This STANAG responds to a stated interoperability requirement: when a patient of one allied nation is treated in a military hospital of another nation, "a military medical record will be prepared for each patient." "This record will accompany the patient upon transfer between hospitals, and will be forwarded to the patient's national military medical authority when the patient is discharged from the hospital or dies." Where a field medical card or patient evacuation tag under STANAG 2132 has also been prepared, "it will accompany the military medical record." The record's own fields and content are AMedP-8.2's subject, not this cover's.
This is Edition 6, dated 15 January 2018. It supersedes STANAG 2348, Edition 5.
The mechanism that matters here: a STANAG binds a nation, not a supplier. "Participating nations agree to implement the following standard": AMedP-8.2, Edition B, and "the national responses are recorded in the NATO Standardization Document Database (NSDD)." Once ratified, "this STANAG is effective upon receipt and ready to be used by the implementing nations and NATO bodies," and it "is implemented when a nation has issued the necessary orders or instructions to authorities and units concerned putting the procedures detailed in this agreement into effect." After implementation, "the nations have to work continually to enhance the STANAG and send the proposals to the Custodian." A supplier meets AMedP-8.2 only where a contract or a tender brings it in by name, not because this STANAG exists on its own.
Nations report their effective implementation "using the form in Annex H to AAP-03(J)"; partner nations report adoption "using the form in Annex G to AAP-03(J)." "This STANAG is to be reviewed at least once every three years," with the result "recorded within the NSDD." Nations and NATO bodies may propose changes at any time to the tasking authority, and any change is processed during that review.
STANAG 2348 also names four other related documents, without making any of them a requirement of its own: MC 0326/3 (NATO's principles and policies of medical support), STANAG 1059 (letter codes for geographical entities), STANAG 2061 (disposition of allied patients by medical installations), and STANAG 2132 (documentation for initial medical treatment and evacuation, which itself covers AMedP-8.1).
No certification exists here, and the document names none. What it describes is a national ratification, implementation and review cycle run through NATO's own machinery, not an audit against this STANAG. Whether a nation's medical record practice matches the current edition of AMedP-8.2 is a matter for that nation's own military standards and any customer's quality clause, not a certification scheme.
STANAG 2348 is a cover, not a specification, so there is nothing to evidence against the STANAG itself: its only substance is the commitment to implement AMedP-8.2. The work that follows, treating and transferring patients between allied military hospitals and forwarding the record to a national military medical authority, happens in medical practice, not in software. What that leaves to hold as evidence is the paperwork around it: procedures that correctly reference AMedP-8.2 and this STANAG, and a record that the implementing orders described in the agreement were actually issued to the authorities and units concerned.
ComplyTrain holds that evidence as a modern, auditable system: version-controlled procedures, records tied to named individuals and dates, and corrective actions when a gap turns up, searchable when a customer's quality clause asks for it. It does not treat patients, prepare or transfer a medical record, or decide how a nation ratifies or implements the agreement, and it does not replace the ratification and reporting nations carry out themselves through the NSDD.
The applicable tier here, and whatever standards come with it, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 2348, the standards explorer covers the related NATO medical publications, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 2348 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 in general. It binds a nation once that nation ratifies it, and it reaches a supplier only through a contract or a tender that names AMedP-8.2 or this STANAG, not by existing on its own. Whether it applies to a given programme is set by the tasking or contract in front of you.
STANAG 2348 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AMedP-8.2 is the publication itself, the Allied medical document that sets out the Basic Military Medical Record's actual content. The STANAG is the cover; AMedP-8.2 is the substance.
Edition 6, dated 15 January 2018. It supersedes STANAG 2348, Edition 5.
No. There is no accredited certification for STANAG 2348 or AMedP-8.2 to hold, and ComplyTrain does not claim one. What we support is the evidence trail around the procedures and records that follow from implementing AMedP-8.2, at an informational level.
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.