Compliance research

ISO 80601-2-12 Third edition 2023-11 — FDA recognition transition and report handoff

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

Medical electrical equipment - Part 2-12: Particular requirements for basic safety and essential performance of critical care ventilators

Complete

Complete standard

[2] [6]
Exported transition expiration: 12/19/2027
FDA 1-187
ISO 80601-2-12 Third edition 2023-11

Medical electrical equipment - Part 2-12: Particular requirements for basic safety and essential performance of critical care ventilators

Complete

Complete standard

[3] [4]
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-146 → 1-187

FDA recognition of ISO 80601-2-12 Second edition 2020-02 [Rec# 1-146] will be superseded by recognition of ISO 80601-2-12 Third edition 2023-11 [Rec# 1-187]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-146] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 1-146] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [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-12 Third edition 2023-11 and the replaced designation(s) ISO 80601-2-12 Second edition 2020-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-146: 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 8914482fc2625e193fd5d4ec1b9038e5c2c8fe42a2735046704981c366cfaa5b

  • [1] HTML tr 22 / Transition Period / nested table · record 01731e1d61ff9041089f1fbe8598f2fc002bb3067dd44a0254cc3a951b3b711d
  • [2] HTML tr 18 / Extent of Recognition / nested table · record 0de3cbd35973908fc71752d8c4828dc5559f1209f5dee0f6e8b3bc52edc4413a

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

  • [3] CSV row 286 · record 2566f44aa33492dbd7b6acb68db3f732810bce9dd4a40899dab53905d0079856
  • [6] CSV row 931 · record 553fa96a5b98609106a0a3984a6bd9a67226d9088dbeaf043662b6fef6f026c7

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 3655136216a2daea6c935000b9987d7bf6a94d2d2af99b053e48101daaf7cb1c

  • [4] HTML tr 18 / Extent of Recognition / nested table · record 3341dc0a03851c10483d34667ea3b275d70ad78ceb499711c04eae30bfea6dba
  • [5] HTML tr 22 / Transition Period / nested table · record 4d0b1ca4507af4a857af8317e5bb62a5e643ec811d7eee0d1cb30790b206d5d3

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