Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-5.2
NATO nations and the organisations that build or integrate their deployable Military Health Information Systems
AMedP-5.2 names the interchange standards, such as DICOM and HL7, that deployable NATO military health information systems must use to exchange medical data with each other.
AMedP-5.2 is a NATO Allied Medical Publication (an "AMedP") that names the technical standards a deployable Military Health Information System (MHIS) has to use when it exchanges personal medical data and medical information with another nation's system or with a NATO system. It leaves each nation free to run whatever it likes inside its own national health IT, and only reaches in at the interchange boundary: whatever a nation runs, it has to be able to hand data across in the standards this publication lists. Those standards are civil and international ones the document adopts rather than writes itself, set out domain by domain in a single annex.
The document traces its own reason for being to an operational problem rather than a policy preference. Recent NATO and coalition operations had shown a need to exchange personal medical data electronically to support patient care, and variation in national and military health data, semantics and system architecture was getting in the way of doing that reliably. AMedP-5.2 is NATO's answer: not a new data format of its own, but a shared list of which existing standard applies to which kind of medical data, so that two nations' systems, built independently, can still exchange it.
The annex works through eleven technical domains and names a standard against each. DICOM covers most imaging (dental X-ray, ECG, endoscopic pictures, nuclear medicine, radiology and ultrasound), with JPEG for microscopic images and any clinical picture not covered elsewhere. HL7 covers clinical messaging (order entry, scheduling, patient administration and patient care), laboratory results (with LOINC for result names and ELINCS for result content), immunizations (alongside the CVX and MVX code sets), patient demographics and clinical encounters, and, in its Clinical Document Architecture form, text-based reports such as history and physical. The Anatomical Therapeutic Chemical (ATC) classification system covers medications, and ICD-10 covers interventions, procedures, and diagnosis and problem lists. Personal health monitoring uses HL7 together with IEEE standards. One domain, multimedia, is recorded as not yet defined. This page names those standards and what each one covers; the annex itself, not this page, is where the message formats and code lists live.
The publication's own front matter shows that implementing every domain is not automatic. At promulgation, three nations recorded reservations: Bulgaria's military medical service could not provide the imaging standard for ECG, nuclear medicine or microscopic pictures (JPEG only, for microscopic images); Canada was still examining its implementation options for the medications standard; and Norway recorded that it would not implement the messaging standard at all. The document treats this as ordinary: a nation ratifies the STANAG this AMedP sits under and can enter a reservation against any domain it does not yet meet, rather than being blocked from ratifying altogether.
AMedP-5.2 is covered by STANAG 2543. The document's own clause states that "This AMedP is implemented when a nation fulfils its obligations under the STANAG, as described in its ratification reply," not by the publication existing on its own. It names no certification scheme, no notified body and no periodic inspection: what it describes is a nation's own ratification and its own reservations, not a third party checking a system's interchange capability against the document.
AMedP-5.2 governs a health information system's own ability to exchange data in a named format, and that work, building or configuring the interchange itself, is systems engineering and clinical IT integration, carried out inside a Military Health Information System. ComplyTrain is not a health information system and does not exchange clinical data; it has no part in that engineering work, and nothing here implies otherwise.
What a compliance platform can reasonably support is the paper trail around the decision, not the decision itself: a record of which annex domain a fielded system is expected to cover and which named standard it uses for it, the documented reservation and remediation plan against any domain a system does not yet meet, the training record for staff who configure or operate the interchange, and the audit trail tying that evidence back to the annex entry it answers. That is general evidence and documentation work of the kind ComplyTrain supports across many standards, not a mapping of the product to AMedP-5.2's own technical content.
Which domains and standards actually apply to a given system is set by the contract and the customer's quality clause, not by this page. The standards explorer shows what else sits alongside AMedP-5.2, and we are glad to talk through what a specific tasking is asking for.
Tell us how you need to work with AMedP-5.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 a nation through the STANAG it is published under: a nation implements AMedP-5.2 once it fulfils its ratification obligations under that STANAG. For an organisation building or integrating a system, it typically arrives as a national requirement or a contract clause naming the publication.
Its annex names DICOM for most imaging, HL7 for clinical messaging, laboratory results, immunizations, patient demographics and text-based reports, LOINC and ELINCS for laboratory result detail, the ATC classification for medications, ICD-10 for procedures and diagnoses, CVX and MVX for immunization codes, and HL7 with IEEE standards for personal health monitoring. One domain, multimedia, is recorded as not yet defined.
No. The document names no certification scheme, notified body or inspection regime. It works instead through a nation's own ratification of the STANAG it sits under, and any reservation a nation enters against a domain it does not yet meet.
No, and the document's own record says so: at promulgation, three nations recorded reservations against specific domains rather than full compliance, and the document points readers to NATO's own standardization database for the current position.
No. ComplyTrain is not a health information system. It can hold the documentation and evidence around which standards a system uses and why, but the interchange itself happens in the Military Health Information System, not in ComplyTrain.
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.