Compliance research

ISO 80601-2-55 Second edition 2018-02 [Including AMD1:2023] — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 1-140 to 1-184 and state declaration-acceptance date(s) for the replaced recognition: recognition 1-140: 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-140
ISO 80601-2-55 Second edition 2018-02

Medical electrical equipment - Part 2-55: Particular requirements for the basic safety and essential performance of respiratory gas monitors

Complete

Complete standard

[3] [6]
Exported transition expiration: 12/20/2026
FDA 1-184
ISO 80601-2-55 Second edition 2018-02 [Including AMD1:2023]

Medical electrical equipment - Part 2-55: Particular requirements for the basic safety and essential performance of respiratory gas monitor [Including Amendment 1 (2023)].

Complete

Complete standard

[2] [5]
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-140 → 1-184

FDA recognition of ISO 80601-2-55 Second edition 2018-02 [Rec# 1-140] will be superseded by recognition of ISO 80601-2-55 Second edition 2018-02 [Including AMD1:2023] [Rec# 1-184]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-140] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 1-140] will not be accepted.

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

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 80601-2-55 Second edition 2018-02 [Including AMD1:2023] and the replaced designation(s) ISO 80601-2-55 Second edition 2018-02. 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-140: 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 594e9b95bd73d7a2805d8fab3d9f0d56a3f03c7eab55da1346ce3e3150d0022d

  • [1] HTML tr 22 / Transition Period / nested table · record 4b07183c047ef15e8b684db420cab923e74b3ba50a66e6317c7998c5fcc458be
  • [5] HTML tr 18 / Extent of Recognition / nested table · record 9972bfd15fc1e9bce4816c32e3f2a9d96c171b82cc127e4cc4d1623e6a1582e6

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 283 · record 5a481bba8b12af75819a9d8e3ce84f8696c29814757732ae16018bcdbd3a226a
  • [3] CSV row 1235 · record 651664762681bab19f52de1009249a8f2ecc97d384a11a0c419f96713c1494b7

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 8c9380b56caaee14abde1659250e5c1959ebfe11dd330895fac4af2a90a45524

  • [4] HTML tr 22 / Transition Period / nested table · record 82d49a98493dfbc8337cf75163759f990b8899e0e1286c379298c9e0fed6b179
  • [6] HTML tr 18 / Extent of Recognition / nested table · record d904d4880762a80486fa3d2838fde2d24133899423878de051529817b0960c79

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