Compliance research

ICDM IDMS Version 1.3 May 31 2025 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 12-361 to 12-384 and state declaration-acceptance date(s) for the replaced recognition: recognition 12-361: 2027-12-19. 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 12-361
ICDM IDMS Version 1.2 May 2023

Information Display Measurements Standard

Complete

Complete standard

[1] [5]
Exported transition expiration: 12/19/2027
FDA 12-384
ICDM IDMS Version 1.3 May 31 2025

Information Display Measurements Standard

Complete

Complete standard

[3] [4]
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 12-361 → 12-384

FDA recognition of ICDM IDMS Version 1.2 May 2023 [Rec# 12-361] will be superseded by recognition of ICDM IDMS Version 1.3 May 31 2025 [Rec# 12-384]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 12-361] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 12-361] will not be accepted.

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

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 ICDM IDMS Version 1.3 May 31 2025 and the replaced designation(s) ICDM IDMS Version 1.2 May 2023. 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 12-361: 2027-12-19. 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 c2b7cd1bfaf4a243ad192b03485238bfe4873a5f90c465e9512d1bbe00c19b75

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 02b28e32d6b6df4b7b54d7c3b7e1297eb342e89ee75c5dad9918885699324aa0
  • [2] HTML tr 22 / Transition Period / nested table · record 44da51e6f7d47882bd31bac18d8d046cbf7e8c9e7fb1404ca8c119c739a3682a

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 6f8ac41723035e25b0640bb57d9c4b706cb1cdb9189cff426d64d160f960bcfd

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 4ae17a672e1e4f49b784aa6e05ffd204a398d969f9bd21e7fdfbd8c6e7d0bc18
  • [6] HTML tr 22 / Transition Period / nested table · record e3a53858dd962d8575bc3fbf7f400d71c1271b69da114d1e5063a59bde396a61

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 176 · record c0240aef0c12adc9828b5485788afbe5d78a885296af59aebbc3dd6de5ac5d83
  • [5] CSV row 412 · record cd4b039d1e894a73d2918214fec611d8226537ed13165140b62bb951e85f5f30

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