Compliance research

ISO 28399 Third edition 2021-03; ANSI ADA Standard No. 136-2022 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 4-291 to 4-331 and state declaration-acceptance date(s) for the replaced recognition: recognition 4-291: 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 4-291
ISO 28399 First edition 2011-01; ANSI ADA Standard No. 136-2015 (R2020)

Dentistry - Products for external tooth bleaching; Products for External Tooth Bleaching

Complete

Complete standard

[4] [6] [7]
Exported transition expiration: 12/20/2026
FDA 4-331
ISO 28399 Third edition 2021-03; ANSI ADA Standard No. 136-2022

Dentistry - External Tooth Bleaching Products; Dentistry - External tooth bleaching products

Complete

Complete standard

[2] [3] [8]
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 4-291 → 4-331

FDA recognition of ISO 28399 First edition 2011-01 [Rec# 4-291] will be superseded by recognition of ISO 28399 Third edition 2021-03 [Rec# 4-331]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 4-291] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 4-291] 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 28399 Third edition 2021-03; ANSI ADA Standard No. 136-2022 and the replaced designation(s) ISO 28399 First edition 2011-01; ANSI ADA Standard No. 136-2015 (R2020). 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 4-291: 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 ecbaf4fc31cbf99dcedc8c59fe397cd74e6137c06c693b01aaeeaaf4e93534ca

  • [1] HTML tr 24 / Transition Period / nested table · record 0cad0c0e8ca451a23a4c1908efed6a0d456e421348236ab30d4e5d2974470dd4
  • [8] HTML tr 20 / Extent of Recognition / nested table · record e777a9ec2f43287c4ec305ba5e775e1f16ad25ed43eb646747a9228efe5365cc

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 303 · record 160c28ded8388c5a7e0be00a9ebde3055f3e2cf409edc915c067c30e8abf2077
  • [3] CSV row 302 · record 24dbd7fd0ffbe6894566dba510044170c309a8f6cbda2aeb543d6e7dcf358305
  • [4] CSV row 706 · record 287a8a99d96afce224bb7a723142a6437701cb11ee70437202d0fce7c518a1b8
  • [6] CSV row 705 · record aeffb439aa6a325381349a27f5c38b99a0b53cb6f2dd5518e6b768ce119137a2

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 aa1e49303e97855018e0556f4aaa4901b9ebe582fc4478ec4763c0ba0d07d043

  • [5] HTML tr 24 / Transition Period / nested table · record 4384396c3d54e6106bbce4871d4676a4b5dcf64b86eb095213e838ec5d055416
  • [7] HTML tr 20 / Extent of Recognition / nested table · record ddab00bcddcb986f13720c23fc36a9f49de67dd584229f2a42005414650615e7

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