Compliance research

ISO 25539-3 Second edition 2024-10 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 3-103 to 3-198 and state declaration-acceptance date(s) for the replaced recognition: recognition 3-103: 2027-07-04. 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 3-103
ISO 25539-3 First edition 2011-12-01; ANSI AAMI ISO 25539-3:2011

Cardiovascular implants - Endovascular devices - Part 3: Vena cava filters

Complete

Complete standard

[2] [4] [5]
Exported transition expiration: 07/04/2027
FDA 3-198
ISO 25539-3 Second edition 2024-10

Cardiovascular implants - Endovascular devices - Part 3: Vena cava filters

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 3-103 → 3-198

FDA recognition of ISO 25539-3 First edition 2011-12-01 [Rec# 3-103] will be superseded by recognition of ISO 25539-3 Second edition 2024-10 [Rec# 3-198]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 3-103] until July 4, 2027. After this transition period, declarations of conformity to [Rec# 3-103] will not be accepted.

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

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 25539-3 Second edition 2024-10 and the replaced designation(s) ISO 25539-3 First edition 2011-12-01; ANSI AAMI ISO 25539-3:2011. 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 3-103: 2027-07-04. 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 49c98f7b9153d728a24053ef89d1410e334d4807a082777f60d1ef3bac563af4

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 19ef6dcde421bd5c0707d5cfaae70df7b0754ea950753ff995b0386d418ec471
  • [7] HTML tr 22 / Transition Period / nested table · record de1cf36b0837e298b30096010d467e55da77821994af41e932d3c97db31a67e0

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 5b0ca6f686e9e95375ccc7c2868e5421410f3a60fa092a18460252edecdad326

  • [2] HTML tr 20 / Extent of Recognition / nested table · record 3402b009a5eea2b954d9e0b06bc6a560e4caad99fc222c980d5f502f923d391d
  • [3] HTML tr 22 / Transition Period / nested table · record 691d56af3c00daad5c66f4da6a24e76dd391fe12ecb81b9a7b7ea6effda8342a

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 1795 · record 71c6edb94599cf306cc01322f0c817c4305da672bae0f05b4955d8ae9f1afc93
  • [5] CSV row 1794 · record 8055583de953e0598afbb27084e67a7c6ba6e53e7174e12bc746a7986d80aebb
  • [6] CSV row 199 · record 8a2a602da2505f3affd8dc99e70462af78636e6b56c4682af64ab342a9dd8371

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