Compliance research

ISO 80369-6 Second edition 2025-05 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 5-108 to 5-146 and state declaration-acceptance date(s) for the replaced recognition: recognition 5-108: 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-108
ISO 80369-6 First Edition 2016-03-15

Small bore connectors for liquids and gases in healthcare applications - Part 6: Connectors for neuraxial applications.

Complete

Complete standard

[2] [4]
Exported transition expiration: 12/17/2028
FDA 5-146
ISO 80369-6 Second edition 2025-05

Small bore connectors for liquids and gases in healthcare applications - Part 6: Connectors for neuraxial applications

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 5-108 → 5-146

FDA recognition of ISO 80369-6 First Edition 2016-03-15 [Rec# 5-108] will be superseded by recognition of ISO 80369-6 Second edition 2025-05 [Rec# 5-146]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 5-108] until December 17, 2028. After this transition period, declarations of conformity to [Rec# 5-108] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [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 80369-6 Second edition 2025-05 and the replaced designation(s) ISO 80369-6 First Edition 2016-03-15. 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-108: 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 — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 4173d155636e185bddf92cc8bf6c24f1596c4fba4676616629b5f51fa9407143

  • [1] HTML tr 22 / Transition Period / nested table · record 036dd843fd294317154c83bb385fc902051befddc4e0725afda05f0ec2d48b08
  • [3] HTML tr 18 / Extent of Recognition / nested table · record 613b6373fc78882e52b46f0dd0fb4fc894a2972f77b7ab7d62a2accf6c5aa120

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 1476 · record 53e76255cfc6cd1569a6a990a0f78b857d77685d64806268de5bce227f65446b
  • [5] CSV row 117 · record bedb4a2721ee3e5ea4e670374e911c482159557267f008e50f4fa815fdbe9856

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 2825d4f694e3372703fa2604e53b149ecd47b35c5dda8b9b04d97c84a2164f9e

  • [4] HTML tr 18 / Extent of Recognition / nested table · record 6e313db301e3f98d22a94e08892b632bd8755e24e1baece25d6c10864c6d0ce6
  • [6] HTML tr 22 / Transition Period / nested table · record d849200e6763500ab5a72cf5e33543857af555cfdc517413601c7182d15b2856

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