Compliance research

ISO 1135-4 Seventh edition 2025-05 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 6-384 to 6-514 and state declaration-acceptance date(s) for the replaced recognition: recognition 6-384: 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 6-384
ISO 1135-4 Sixth edition 2015-12-01

Transfusion equipment for medical use-Part 4: Transfusion sets for single use gravity feed

Complete

Complete standard

[4] [6]
Exported transition expiration: 12/17/2028
FDA 6-514
ISO 1135-4 Seventh edition 2025-05

Transfusion equipment for medical use-Part 4: Transfusion sets for single use gravity feed

Complete

Complete standard

[2] [3]
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 6-384 → 6-514

FDA recognition of ISO 1135-4 Sixth edition 2015-12-01 [Rec# 6-384] will be superseded by recognition of ISO 1135-4 Seventh edition 2025-05 [Rec# 6-514]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 6-384] until December 17, 2028. After this transition period, declarations of conformity to [Rec# 6-384] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [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 1135-4 Seventh edition 2025-05 and the replaced designation(s) ISO 1135-4 Sixth edition 2015-12-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 6-384: 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 c72016968d9fed9ac8f0a89403ac7c1273506f4a85a60a85bbf4d9c039803af4

  • [1] HTML tr 22 / Transition Period / nested table · record 253bb9330588bfc1c715f90d49757be451d7242a6ad006c43cb7639ac9a7f1d6
  • [4] HTML tr 18 / Extent of Recognition / nested table · record d9e0fecb9152048b2f5693fa253556f029efddeb2bc6898b01cb32fffb62ffa5

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 914b41ea19fdf774a70e1047679468c0968da82c0d3ed0e526b79deaa81e1ee3

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 69829820d33d62ddd1e277e99d1a6b0d73d7740a189371afd654d8d94c34b6f6
  • [5] HTML tr 22 / Transition Period / nested table · record ec460b553dd0d505f12245ce9debd4b05f0066981cd9b1630fb0d075944bb14a

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

  • [3] CSV row 121 · record 9e2b78492e4ab4eb6fefd147ef774372134b1c172bb3867366182f3939a354ae
  • [6] CSV row 1386 · record f58972cc5aafb57f5ca07e41b2acdac5f9c88903b22d6f522ece460846da5634

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