Compliance research

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

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

Cardiovascular implants - Cardiac valve prostheses - Part 1: General requirements

Partial

Partial recognition. The following part(s) of the standard is (are) not recognized: -7.2.5.3 Device structural component fatigue assessment -Annex J.3.1 General

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

Cardiovascular implants - Cardiac valve prostheses - Part 1: General requirements [Including: AMENDMENT 1 (2025)]

Partial

Partial recognition. The following part(s) of the standard is (are) not recognized: Section 7.2.5.3 Device structural component fatigue assessment Annex J.3.1 General

[1] [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 3-174 → 3-205

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

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

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-1 Second edition 2021-01 01 [Including AMD1:2025] and the replaced designation(s) ISO 5840-1 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-174: 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 1f2e6d469dc58acd21061ae64ca5ece16e151ab4a50de96957e19c4be1a25598

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 05c691e3493c1132af1b20801121a52d3f3bebdfbf7f22bc7107eae3cc1a4817
  • [2] HTML tr 23 / Transition Period / nested table · record 1d58c3941832c7c288ccf0b872ce1f3138da278f7a9923f15e79d25e9f18227f

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 7d80fe3100534e75de1337acdd67d136849fd78069559c20f33126e9440f0395

  • [3] HTML tr 23 / Transition Period / nested table · record 8c506ee42f1b737c62877d8e63f8a9f06bd28beefec435b343b8e0065713edbc
  • [6] HTML tr 18 / Extent of Recognition / nested table · record aafe06fb6249a662ab929868667e7302b7e41fb8789cc88a4146cf28d9eadfa0

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 689 · record 8c9ee653c75e129009df9449a2cf65bc2b654a0e18eb723531e43aed4247c9ae
  • [5] CSV row 7 · record 9aa75e5a775adfcd0b5c3cd482365ddc9566db16fb5a6e55a3c56379e0c7a69d

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