Compliance research

ISO 5362 Fifth edition 2024-07 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 1-75 to 1-182 and state declaration-acceptance date(s) for the replaced recognition: recognition 1-75: 2026-12-20. Compare the exact edition and recognition limitations with your reports before agreeing the submission evidence or further work.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Exact FDA recognition records

Compare the edition and the recognized portion

Read these columns together. A complete recognition is not a device-specific testing instruction. The limitations are the FDA’s public metadata; the licensed standard itself is not reproduced.

Recognition / editionPublic recognition limitationsDeclaration transition context
FDA 1-75
ISO 5362 Fourth edition 2006-06-01; ANSI AAMI ISO 5362:2006

Anaesthetic Reservoir Bags

Complete

Complete standard

[1] [4] [7]
Exported transition expiration: 12/20/2026
FDA 1-182
ISO 5362 Fifth edition 2024-07

Anaesthetic and respiratory equipment - Anaesthetic reservoir bags

Complete

Complete standard

[2] [6]
No expiration date is stated in this acquired export row. That is not a guarantee of indefinite recognition.

What FDA’s transition statement says

Recognition 1-75 → 1-182

FDA recognition of ISO 5362 Fourth edition 2006-06-01 [Rec# 1-75] will be superseded by recognition of ISO 5362 Fifth edition 2024-07 [Rec# 1-182]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-75] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 1-75] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [3] [5]

FDA public recognition metadata describes use of declarations of conformity in support of premarket submissions. A recognition transition is not a universal retesting deadline, a product ban, or proof that this standard applies to your device. The technical differences between licensed editions, adequacy of existing reports, buyer-specific route and final test scope remain incomplete. The comparison below does not reproduce the standard or establish FDA approval.

Method: Exact directed old-to-new statements are reconciled across both acquired sheets and the old export date. No name-similarity mapping or technical-clause inference.

Build your edition-to-report handoff matrix

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which edition is actually in your evidence?

    Reconcile each report and declaration against ISO 5362 Fifth edition 2024-07 and the replaced designation(s) ISO 5362 Fourth edition 2006-06-01; ANSI AAMI ISO 5362:2006. Record amendments and the exact report/device revision. A similar standard number is not an edition match.

    Useful evidence: Report cover, method/edition references, amendments, declarations and device/configuration revision.

  2. Does the declaration cover the recognized portion?

    Use the complete FDA public limitation text in the comparison table. Map each listed exclusion, where present, to the relevant report sections and obtain a reasoned evidence assessment. Complete recognition still does not determine device applicability.

    Useful evidence: Recognition-to-report coverage matrix, excluded-clause assessment and the licensed edition used by your specialist.

  3. How does the recorded transition affect your submission plan?

    Record planned declaration/submission dates against the FDA sheet’s acceptance date(s): recognition 1-75: 2026-12-20. This concerns declarations supporting premarket submissions to the replaced recognition; do not treat it as a blanket deadline to retest or stop selling.

    Useful evidence: Submission plan, intended declaration references, dated recognition-sheet check and rationale for the chosen evidence route.

  4. What changed beyond the designation?

    Ask the specialist to assess the actual licensed edition/amendment differences for your design, materials, software and use environment. Separate a documented evidence gap from a changed title. This metadata comparison does not establish which tests changed or must be repeated.

    Useful evidence: Edition gap assessment tied to the device and existing evidence, with a bridging rationale and unresolved inputs.

  5. What should the quote include?

    Request a report/recognition reconciliation and a justified gap assessment first. Separate any proposed additional evaluation or testing, samples, methods, deliverables and exclusions; agree them only after applicability and existing evidence are assessed.

    Useful evidence: A scoped evidence-assessment quote; separately identified conditional work and report ownership.

Work packages and dependencies

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 0110dd90b907c8bed7b3c52b3af2429b733cba7383d541711e58f5f38780111d

  • [1] HTML tr 20 / Extent of Recognition / nested table · record 007f02d328a6304bc66e6d54766690d85524ca1aadf969a4005cf3531158aeeb
  • [5] HTML tr 24 / Transition Period / nested table · record 85db81443e0fe573c1e74132292f8cb92f677f9b8fe53a9cf6a8bc5ec351b9b7

FDA — recognition metadata exported through the official search form ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 94ccf56dc846c7f6d78d6ad77dc6e87d1803ac3612af01d6894949e34c4a78d8

  • [2] CSV row 281 · record 2541790d6da91d58329d83b291a15ff00442d57aed5e324255b11805af8e1a09
  • [4] CSV row 1808 · record 835ae0bb9ad2955424082648ba72dfe26b1816614b3fd98d8bb6e9040e4feb43
  • [7] CSV row 1807 · record d27352abef275c8bc82ba5457e6f30fb78ee290901182999699c6f93d7b9caca

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot c01c271513d4eec68002d5b5e2c59e17b74a5a013d957d3708e5915f124edef1

  • [3] HTML tr 22 / Transition Period / nested table · record 6ef707d7b2506d56d8b9539b9fad94239235afc28ad92715fe6dd965993652a0
  • [6] HTML tr 18 / Extent of Recognition / nested table · record a21f62a470c13f7e8e7d1c448334f2f06dbce66e56208505418a4aff21469a11

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services