Compliance research

ISO 23500-5 Second edition 2024-04 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 9-137 to 9-156 and state declaration-acceptance date(s) for the replaced recognition: recognition 9-137: 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 9-137
ISO 23500-5 First edition 2019-02; ANSI AAMI ISO 23500-5:2019

Preparation and quality management of fluids for haemodialysis and related therapies - Part 5: Quality of dialysis fluid for haemodialysis and related therapies

Complete

Complete standard

[3] [6] [7]
Exported transition expiration: 07/02/2028
FDA 9-156
ISO 23500-5 Second edition 2024-04

Preparation and quality management of fluids for haemodialysis and related therapies - Part 5: Quality of dialysis fluid for haemodialysis and related therapies

Complete

Complete standard

[1] [2]
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 9-137 → 9-156

FDA recognition of ISO 23500-5 First edition 2019-02 [Rec# 9-137] will be superseded by recognition of ISO 23500-5 Second edition 2024-04 [Rec# 9-156]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 9-137] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 9-137] 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 23500-5 Second edition 2024-04 and the replaced designation(s) ISO 23500-5 First edition 2019-02; ANSI AAMI ISO 23500-5:2019. 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 9-137: 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 63 · record 434b8cd4f98464e1962a01266eed16503ee163caeaa9cfe531335c037c6c03c5
  • [3] CSV row 818 · record 753f585b0acb78e80b08afd6d3c1a558b64f00926034ae29b8779a39f9f212dd
  • [6] CSV row 819 · record b05daeac5bfef0d835034aae8fd8dc3126224c8594379213a5b4c015cf1bff44

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 892c68d82458cc1167d4f57e6ee25cb8e1723c2276512025a834505ecc450cf7

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 5fe043514601130a27deddcc39dde0e97efd23f4d5a408bb536d70c9fdade970
  • [5] HTML tr 22 / Transition Period / nested table · record a6e38e55a66c9823ec48a658e86f96ee36efaf44fa9c19fbcae6bc69c51422d4

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 0eed39d23269de826555d0bdec2b526b9979ebfc7f0011aeda2d72069bde9a3a

  • [4] HTML tr 24 / Transition Period / nested table · record 9aa156e5915ee568bb4be4484ff6ab3e39410875a2edc8ab9fbaa60f0e73082a
  • [7] HTML tr 20 / Extent of Recognition / nested table · record e988a2ede387b593ee1ea1d3d1b78e938358ffa39d4df9841ea43947e0755b42

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