Compliance research

ISO 80601-2-79 Second edition 2024-08 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 1-143 to 1-185 and state declaration-acceptance date(s) for the replaced recognition: recognition 1-143: 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-143
ISO 80601-2-79 First edition 2018-07

Medical electrical equipment - Part 2-79: Particular requirements for basic safety and essential performance of ventilatory support equipment for ventilatory impairment

Complete

Complete standard

[1] [4]
Exported transition expiration: 12/19/2027
FDA 1-185
ISO 80601-2-79 Second edition 2024-08

Medical electrical equipment - Part 2-79: Particular requirements for basic safety and essential performance of ventilatory support equipment for ventilatory impairment

Complete

Complete standard

[2] [3]
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-143 → 1-185

FDA recognition of ISO 80601-2-79 First edition 2018-07 [Rec# 1-143] will be superseded by recognition of ISO 80601-2-79 Second edition 2024-08 [Rec# 1-185]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-143] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 1-143] will not be accepted.

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

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-79 Second edition 2024-08 and the replaced designation(s) ISO 80601-2-79 First edition 2018-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-143: 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 — recognised standards metadata ↗

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

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 6fb3fbfc5966018eb93d447f8f00905755b087a6b128d6463997e8fa1ce58918

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

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 284 · record 6b8fb224666f6694a2beb0ee4e9b918a3c37d868655cc6af1b265cc925292f83
  • [4] CSV row 1078 · record ae6ac27f6148b8c810f7b6db6f012802e9977acafdeedff17e85727e5c001f1c

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 c8e1e0403bb7925b85ae0d7b2daf3a88bdf2ecac38d3caa41e19922007e3d785

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 9adeaba891416b0b68d5eed168ce410891ddf63a93afa6f3b63029c64e7081b0
  • [6] HTML tr 22 / Transition Period / nested table · record ff237fbec9c4df9d10d353049ab83feff4f88dac8270dc60122b0314051b54d3

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