Compliance research

ISO 5840-2 Second edition 2021-01 [Including AMD1:2025] — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 3-175 to 3-206 and state declaration-acceptance date(s) for the replaced recognition: recognition 3-175: 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 3-175
ISO 5840-2 Second edition 2021-01

Cardiovascular implants - Cardiac valve prostheses - Part 2: Surgically implanted heart valve substitutes

Complete

Complete standard

[1] [2]
Exported transition expiration: 07/02/2028
FDA 3-206
ISO 5840-2 Second edition 2021-01 [Including AMD1:2025]

Cardiovascular implants - Cardiac valve prostheses - Part 2: Surgically implanted heart valve substitutes [Including: AMENDMENT 1 (2025)]

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 3-175 → 3-206

FDA recognition of ISO 5840-2 Second edition 2021-01 [Rec# 3-175] will be superseded by recognition of ISO 5840-2 Second edition 2021-01 [Including AMD1:2025] [Rec# 3-206]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 3-175] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 3-175] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [4] [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 5840-2 Second edition 2021-01 [Including AMD1:2025] and the replaced designation(s) ISO 5840-2 Second edition 2021-01. 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-175: 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 — 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 690 · record 0df84ed9371101dc75320da49ef44e73c7deb15d2efafa1396c38780105dfa81
  • [3] CSV row 8 · record b68a9693b741b22b028419b065e337360110822fcf52f46575f7550147308bb7

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 01b88010e0bbfba8c62897d30d7ab89a483e3065e8ac223b29efcacc3f09d600

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 52096b6211526fa2b11df512afca294499bb7b46e867019440100b4a75b241c2
  • [5] HTML tr 22 / Transition Period / nested table · record d478cf79d9845a8f2e30a1ec5b42de7529c515d878341f73cb43bf66d0ca3e05

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 af6747c3eb16b6b9f59119ca81041a08654430df42d65205951560494fc81ea5

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

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