Compliance research

ISO 80601-2-84 Second edition 2023-11 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 1-160 to 1-188 and state declaration-acceptance date(s) for the replaced recognition: recognition 1-160: 2027-12-19. 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-160
ISO 80601-2-84 First edition 2020-07

Medical electrical equipment - Part 2-84: Particular requirements for the basic safety and essential performance of ventilators for the emergency medical services environment

Complete

Complete standard

[1] [4]
Exported transition expiration: 12/19/2027
FDA 1-188
ISO 80601-2-84 Second edition 2023-11

Medical electrical equipment - Part 2-84: Particular requirements for the basic safety and essential performance of ventilators for the emergency medical services environment

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-160 → 1-188

FDA recognition of ISO 80601-2-84 First edition 2020-07 [Rec# 1-160] will be superseded by recognition of ISO 80601-2-84 Second edition 2023-11 [Rec# 1-188]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-160] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 1-160] 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 80601-2-84 Second edition 2023-11 and the replaced designation(s) ISO 80601-2-84 First edition 2020-07. 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-160: 2027-12-19. 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 — 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

  • [1] CSV row 587 · record 15f0b08bb2edf8690c9bc4e117249ad37a43f30a8bf3269cc08fc000b910fc16
  • [6] CSV row 287 · record cb971fa7af634ce41c2a587d2594afeb7c2a07f0399664acdf6bab53e9abcc42

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 eed78166b69105987ad42f4d1060eeb2cd449f337f81d388b7a528fd627e9990

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 2bcf705b29c682b55a6a147f9d00004edc842887d34a81ae893d42e39eb001e0
  • [3] HTML tr 22 / Transition Period / nested table · record 565bd5d8b9d1e53985ed02242da2d3b597996327cce9e55855d196a71eb1a061

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

  • [4] HTML tr 18 / Extent of Recognition / nested table · record 5ba926960933a119234d3d55eb1c308cce2a8befc1f1be3f7ddaec817b195eea
  • [5] HTML tr 22 / Transition Period / nested table · record 6abdf395d25d3180f54352f71b9dc8e8ce37100c6169423d016713270ba8d402

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