Compliance research

ISO 7376 Third edition 2020-08 [Including AMD1:2025] — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 1-149 to 1-198 and state declaration-acceptance date(s) for the replaced recognition: recognition 1-149: 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-149
ISO 7376 Third edition 2020-08

Anaesthetic and respiratory equipment - Laryngoscopes for tracheal intubation

Complete

Complete standard

[1] [2]
Exported transition expiration: 12/19/2027
FDA 1-198
ISO 7376 Third edition 2020-08 [Including AMD1:2025]

Anaesthetic and respiratory equipment - Laryngoscopes for tracheal intubation - Amendment 1: Clarification of optical output and illumination requirements [Including Amendment 1 (2025)]

Complete

Complete standard

[3] [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-149 → 1-198

FDA recognition of ISO 7376 Third edition 2020-08 [Rec# 1-149] will be superseded by recognition of ISO 7376 Third edition 2020-08 [Including AMD1:2025] [Rec# 1-198]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 1-149] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 1-149] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [4] [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 7376 Third edition 2020-08 [Including AMD1:2025] and the replaced designation(s) ISO 7376 Third edition 2020-08. 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-149: 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 a711fdd50302b570f699ed9a2a6ad238f834f0abd4902db5b48c859526911d8a

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 24fc12e1a644c58dac7b9e0f7d0e2a6aba52a527827de88754da33e511f9c0c0
  • [4] HTML tr 22 / Transition Period / nested table · record 72eebbf63b2deda6d0b6019bf87e842cea343977f2f4e9b37c86cc1e38904069

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 849 · record 3c11bb1d10c94969e598761715d99dcfce910243bd5eb42184febeff6cc538c6
  • [5] CSV row 78 · record 9946adbd3b269616cf81203bcdd764f9aeb28423e1a7881ae8e1368aced7987a

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 ef510a66786881d2425116053b61ee275a71fb54f40dec6b4ddfe6098926a7b2

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

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