Compliance research

ISO 80369-20 Second edition 2024-11 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 5-97 to 5-144 and state declaration-acceptance date(s) for the replaced recognition: recognition 5-97: 2028-07-02. 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 5-97
ISO 80369-20 First edition 2015-05-15; ANSI AAMI ISO 80369-20:2015

Small-bore connectors for liquids and gases in healthcare applications - Part 20: Common test methods

Complete

Complete standard

[2] [4] [7]
Exported transition expiration: 07/02/2028
FDA 5-144
ISO 80369-20 Second edition 2024-11

Small-bore connectors for liquids and gases in healthcare applications - Part 20: Common test methods

Complete

Complete standard

[1] [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 5-97 → 5-144

FDA recognition of ISO 80369-20 First edition 2015-05-15 [Rec# 5-97] will be superseded by recognition of ISO 80369-20 Second edition 2024-11 [Rec# 5-144]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 5-97] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 5-97] 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 80369-20 Second edition 2024-11 and the replaced designation(s) ISO 80369-20 First edition 2015-05-15; ANSI AAMI ISO 80369-20:2015. 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 5-97: 2028-07-02. 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 9a2d8bc623da196fd583cde1ec7d7b53934cb0702661ed0e4fe83f577f58db87

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 371495fd17f5547aaec65f14c9308d8fd2b3203e16f35a77c0b3dc7b598f2d91
  • [3] HTML tr 22 / Transition Period / nested table · record b0e4902d90f3865fd2def6970b8cfea34e20b4597fe4ad0d29d75b8901073224

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 47234f28df16069b2adb466a9ed54b7ce91327f70dd4ecb3e8f39e03d1dbb775

  • [2] HTML tr 20 / Extent of Recognition / nested table · record 6b680e38488dfdb6b9db892ee2fcc30953028878d9d071de3699e5865534b4a9
  • [5] HTML tr 24 / Transition Period / nested table · record c2a47beeb79d515af9183dbdcf118c454b0c382590cfef932d0837964934f2b7

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

  • [4] CSV row 1566 · record b830b167e2c493feb8f7b7b83e0f1f4c92b4203eb0c6483590400e66ba23559e
  • [6] CSV row 212 · record c58ee31140d12898c0db23cda7d00562290acd2368300e246e12d22e784ed97c
  • [7] CSV row 1567 · record c73693dca274a71a4f2b3140a1825be9f64c28c89899a853e813c1e1d603b617

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