Compliance research

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

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

Preparation and quality management of fluids for haemodialysis and related therapies - Part 3: Water for haemodialysis and related therapies

Complete

Complete standard

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

Preparation and quality management of fluids for haemodialysis and related therapies - Part 3: Water for haemodialysis and related therapies

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 9-135 → 9-154

FDA recognition of ISO 23500-3 First edition 2019-02 [Rec# 9-135] will be superseded by recognition of ISO 23500-3 Second edition 2024-04 [Rec# 9-154]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 9-135] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 9-135] 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-3 Second edition 2024-04 and the replaced designation(s) ISO 23500-3 First edition 2019-02; ANSI AAMI ISO 23500-3: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-135: 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 6ac86aeee9182eb28991b556ea1be2b71db3729987848abf8e262752fc526857

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 32500c01b9b66d14db9d661248a38929cef07bd4c10fdc22bbbf0fff034499cd
  • [5] HTML tr 22 / Transition Period / nested table · record 8510a6a86761443c7330940b2a57896b542764062f50e984476d1e0229d6c81a

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

  • [2] CSV row 814 · record 5e07f85b61122b808d86258425649ae0eaa266178a9818336cb3d40d452c2452
  • [6] CSV row 61 · record c6db52f82466510a51580954a934881199f6f8a2044899f48be6c95fc4c405f7
  • [7] CSV row 815 · record d369e6dbb0c8301ac793dfeef25d24edf49eeb6fb7aa104d013170fe514e8241

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 1cee7131c3f59b6494b38164a91993f8b529f3023f9f73e1ee3863df7efeb31d

  • [3] HTML tr 20 / Extent of Recognition / nested table · record 66b0e0b084572a1a6b280a8b17da7c550605a3d57d0fb916bf1405c92be59625
  • [4] HTML tr 24 / Transition Period / nested table · record 79816e63b788693e782b5934769a491e48c65368472cb1e2530738bb2f1fc252

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