Compliance research

ISO 15223-1 Fourth edition 2021-07 [Including AMD1: 2025] — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 5-134 to 5-148 and state declaration-acceptance date(s) for the replaced recognition: recognition 5-134: 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 5-134
ISO 15223-1 Fourth edition 2021-07

Medical devices - Symbols to be used with information to be supplied by the manufacturer - Part 1: General requirements

Complete

Complete standard

[4] [6]
Exported transition expiration: 12/17/2028
FDA 5-148
ISO 15223-1 Fourth edition 2021-07 [Including AMD1: 2025]

Medical devices - Symbols to be used with information to be supplied by the manufacturer - Part 1: General requirements [Including Amendment 1 (2025)]

Complete

Complete standard

[1] [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 5-134 → 5-148

FDA recognition of ISO 15223-1 Fourth edition 2021-07 [Rec# 5-134] will be superseded by recognition of ISO 15223-1 Fourth edition 2021-07 [Including AMD1: 2025] [Rec# 5-148]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 5-134] until December 17, 2028. After this transition period, declarations of conformity to [Rec# 5-134] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [2] [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 15223-1 Fourth edition 2021-07 [Including AMD1: 2025] and the replaced designation(s) ISO 15223-1 Fourth edition 2021-07. 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 5-134: 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 6c3c9074cbb9bf4645d7d96a976d7c2e46ab662e2efdf96541536f509a5c4ab0

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 0a7824cb68bc757f32d65240f0b22cf99bb1c07b1eda5f4d7162c500c4476fbb
  • [2] HTML tr 22 / Transition Period / nested table · record 405e94e9afc0673f8a538e7129f9eb9deff9fd6a6976a6ef27100cf06e1c2e8b

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 119 · record 4807867f84651019bfe4bf51c9e3ae597bf279825c2b2415648a2657e3903e82
  • [4] CSV row 709 · record 71e42ed9514a35b292e75a119b9fbf800bdf89917ca23000383092ab3ac90bc3

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 b0179f8cb1a7d2ce685185e3e99cbbb0d495e425b1bcea0db0375f54bcf5d296

  • [5] HTML tr 22 / Transition Period / nested table · record bde416ac59be24c087cb20f0218d1c103670ab9e573247c81a49cee0ea8e926f
  • [6] HTML tr 18 / Extent of Recognition / nested table · record e30810484c2cd02a97c17e996982279a9a7de3f12aff63a4f7aecde2f1f7e4e5

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