Compliance research

ISO 80369-1 Third edition 2025-10 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 5-121 to 5-147 and state declaration-acceptance date(s) for the replaced recognition: recognition 5-121: 2028-12-17. 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-121
ISO 80369-1 Second edition 2018-11

Small-bore connectors for liquids and gases in healthcare applications - Part 1: General requirements

Complete

Complete standard

[1] [5]
Exported transition expiration: 12/17/2028
FDA 5-147
ISO 80369-1 Third edition 2025-10

Small-bore connectors for liquids and gases in healthcare applications - Part 1: General requirements

Complete

Complete standard

[3] [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-121 → 5-147

FDA recognition of ISO 80369-1 Second edition 2018-11 [Rec# 5-121] will be superseded by recognition of ISO 80369-1 Third edition 2025-10 [Rec# 5-147]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 5-121] until December 17, 2028. After this transition period, declarations of conformity to [Rec# 5-121] will not be accepted.

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

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-1 Third edition 2025-10 and the replaced designation(s) ISO 80369-1 Second edition 2018-11. 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-121: 2028-12-17. 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 — 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

  • [1] CSV row 1173 · record 0b157566ec64c539de4b15d5763988d809ea3f3a81078483baad3ed5262b25d2
  • [6] CSV row 118 · record bf8dcf094463a5fcc71bc57cf6e14e9403116f380be6552f39a72da0cbf3e1e6

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 c0eb4d1bea6350e0680ecabc8314deb7cdcdc51ed2ad9e40c34d9720ee22adb9

  • [2] HTML tr 22 / Transition Period / nested table · record 2e57519454485cc9729f4785b7a4cbc6dba02366c877edccbe68f88227cc8fe7
  • [5] HTML tr 18 / Extent of Recognition / nested table · record 7adac3f52a04fb3d8a44d6fcc1ddeeef495d58290b79e39ed7df3a61349fa29a

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 58267a8fde6e379e5d44beed006ab30165df66ad450e59504511b3bdd49d596a

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 3179b7ec8079774dda02768d8e6ab74460df8afdcdc325e1cdc268fbe1ad0069
  • [4] HTML tr 22 / Transition Period / nested table · record 554a4821561e6c964c4355a37c04be5969732cf34124cc2231fba3824eea97ff

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