Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AMedP-1.4
NATO nations that ratify STANAG 1412, and the organisations that design or supply the litters their ships and aircraft carry for casualty transfer at sea
AMedP-1.4 sets NATO's minimum design requirements for the litter used to move a casualty from one ship to another or from a ship to an aircraft, given force through STANAG 1412 and naming no certification scheme.
AMedP-1.4 is the NATO Allied Medical Publication that sets minimum design requirements for the litter used to move a casualty from one ship to another, or from a ship to an aircraft, at sea. The document's own aim is that a casualty transfer from a ship should be managed "with the highest degree of safety in this known hazardous operation", achieved by standardising the litter itself rather than the technique for carrying it. This page covers what the publication is for, who it addresses, and how it reaches an organisation; the litter's dimensions, load ratings, hoisting arrangement and restraint strengths are for a design team to read directly from the document's clause 1.3.
STANAG 1412 is the NATO agreement that gives AMedP-1.4 its force: nations record their agreement to use the publication in that STANAG, and AMedP-1.4 is the specification the STANAG points to. Ratification is a national act, and the reservations recorded against this edition show what that means in practice. Denmark's ratification carries reservations against several of clause 1.3's requirements, because its own litter's lift capacity, construction, strap strength and marking depart from the specification. France notes that a compliant litter is available on its vessels for NATO missions and exercises, but not necessarily outside them. The Netherlands notes that not every ship of the Royal Netherlands Navy carries a stretcher in line with the STANAG. None of that is unusual: a STANAG binds a nation, not automatically every piece of equipment already in service, and a nation can ratify with a stated reservation rather than re-equip immediately. For an organisation designing or supplying transfer litters, the practical trigger is a national specification or a contract that names AMedP-1.4 or STANAG 1412, not the publication's existence in NATO's catalogue.
A casualty moved by winch, highline or helicopter hoist between one nation's ship or aircraft and another's depends on the litter fitting hardware that belongs to whichever platform is doing the lifting, not the one the casualty came from. AMedP-1.4's statement of details, in clause 1.3, sets the shared minimum a litter has to meet for that to work: it has to float and stay upright in water, attach securely for hoisting, resist the marine environment, restrain the casualty, and stay visible in poor light. The specific dimensions, load figures and attachment hardware sit in that clause itself, for a design team to work from directly; what matters here is that the requirement exists because the transfer, not any one nation's equipment, is what has to be interoperable.
AMedP-1.4 addresses the nations that approve and ratify it, in this edition recorded as "the nations in the MCMEDSB". In practice, that agreement reaches whoever designs, builds or supplies the litters a nation's ships and aircraft carry, once a national specification or contract calls the standard up. It does not bind a supplier directly by existing, and beyond being "effective upon receipt" for the ratifying nation, it says nothing about timing within a procurement or shipbuilding programme.
AMedP-1.4 names no certification body, no accreditation scheme and no periodic assessment cycle. What the document does describe is national ratification, which a nation can qualify with a specific reservation, as three nations did for this edition. Where an organisation is asked to evidence that a litter meets clause 1.3, that happens through whatever national acceptance or contract process invoked the standard, not through any scheme NATO administers or recognises.
AMedP-1.4 is an operational and technical standard, and the work it demands sits with a design and engineering team, not a compliance department: building a litter that floats, hoists, restrains and withstands salt water is done in design and test, not in software. ComplyTrain's part is the documentation and evidence trail around that work: the record of which edition and which national reservation applies to a given contract, the design and test evidence that shows a litter meets clause 1.3, the training record for staff who need to know the standard applies, and the audit trail connecting a delivered litter to the requirements it was built against.
What ComplyTrain does not do: it does not design, build, float-test or hoist-test the litter itself, and it does not decide which nation's reservation applies to a given programme. What actually applies is set by the contract and the customer's quality clause. The standards explorer shows what else sits alongside AMedP-1.4 and STANAG 1412, and we are glad to talk through what a specific tasking or contract is asking for.
Tell us how you need to work with AMedP-1.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.
It binds through STANAG 1412, the NATO agreement recording nations' commitment to use it. A nation can ratify with a reservation against specific requirements, as Denmark, France and the Netherlands did for this edition, so whether it is mandatory for a given supplier depends on the national specification or contract that invokes it, not on the publication existing.
No. The document names no certification body or accreditation scheme. A litter's compliance is a matter for whatever national acceptance or contract process called the standard up, not for an accredited body issuing a certificate.
Edition A, Version 1, published in June 2013. The document does not state what it superseded.
No, and this edition says so directly: Denmark, France and the Netherlands each recorded a reservation or a caveat against their own fleet's equipment when ratifying it.
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.