Compliance research

IEC 62127-2 Edition 2.0 2025-01 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 12-291 to 12-379 and state declaration-acceptance date(s) for the replaced recognition: recognition 12-291: 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 12-291
IEC 62127-2 Edition 1.2 2017-03 CONSOLIDATED VERSION

Ultrasonics -- Hydrophones -- Part 2: Calibration for ultrasonic fields up to 40 MHz

Complete

Complete standard

[5] [6]
Exported transition expiration: 07/02/2028
FDA 12-379
IEC 62127-2 Edition 2.0 2025-01

Ultrasonics -- Hydrophones -- Part 2: Calibration for ultrasonic fields up to 40 MHz

Complete

Complete standard

[2] [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-291 → 12-379

FDA recognition of IEC 62127-2 Edition 1.2 2017-03 CONSOLIDATED VERSION [Rec# 12-291] will be superseded by recognition of IEC 62127-2 Edition 2.0 2025-01 [Rec# 12-379]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 12-291] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 12-291] will not be accepted.

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

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 IEC 62127-2 Edition 2.0 2025-01 and the replaced designation(s) IEC 62127-2 Edition 1.2 2017-03 CONSOLIDATED VERSION. 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-291: 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 36f8781e70d7e06defe3da3ad7e98365bc5bccac01cac224956c3f078b5700a2

  • [1] HTML tr 22 / Transition Period / nested table · record 2e9b7e3f5049d651328f5863f4c7f9ec5c93e576f402beabc509841b53eaaa05
  • [4] HTML tr 18 / Extent of Recognition / nested table · record 9e82b87ee1a8208cb698d830679a9bc8109e06aab490202eb6502f2fd3ef9fa2

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 266 · record 8fb1d2f1ba07a48751b9b4556f8c92b0330135c0ab5a99a1f6738115dccff337
  • [6] CSV row 1589 · record fbafe8ef9fa43da2017a2995cccad04e37dafbd65fdcd0fc8cf66838d5e6d3c9

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 7ce37301650cd4a05a60bd3b34ba5422a85a00d2f303ea572cbfab6b3322ae5c

  • [3] HTML tr 22 / Transition Period / nested table · record 93306b63cc1b47f8010f9a56a6b84edb15a558f8bc2437e3e6c8022414968727
  • [5] HTML tr 18 / Extent of Recognition / nested table · record dd624aa4e11eab23034db55f7d86c94148d510c7c6cab293fa691a3bfbf41254

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