Compliance research

IEC 60601-2-37 Edition 3.0 2024-07 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 12-293 to 12-380 and state declaration-acceptance date(s) for the replaced recognition: recognition 12-293: 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-293
IEC 60601-2-37 Edition 2.1 2015

Medical electrical equipment - Part 2-37: Particular requirements for the basic safety and essential performance of ultrasonic medical diagnostic and monitoring equipment

Complete

Complete standard

[5] [6]
Exported transition expiration: 07/02/2028
FDA 12-380
IEC 60601-2-37 Edition 3.0 2024-07

Medical electrical equipment - Part 2-37: Particular requirements for the basic safety and essential performance of ultrasonic medical diagnostic and monitoring equipment

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-293 → 12-380

FDA recognition of IEC 60601-2-37 Edition 2.1 2015 [Rec# 12-293] will be superseded by recognition of IEC 60601-2-37 Edition 3.0 2024-07 [Rec# 12-380]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 12-293] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 12-293] will not be accepted.

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

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 60601-2-37 Edition 3.0 2024-07 and the replaced designation(s) IEC 60601-2-37 Edition 2.1 2015. 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-293: 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 8fd63ff5f9ba6b9297c4423df84f32adaef0113f121dd4a58bf42aaa27a2aa93

  • [1] HTML tr 18 / Transition Period / nested table · record 0f5ffc5655751f65c25382e65a303a6ef620dd109e95fcbf3a69c590495d98f6
  • [6] HTML tr 16 / Extent of Recognition / nested table · record b24e771d6c0ac498c288a467fa13334a302d1c1bbafb0fd26bf90663b2e4e929

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

  • [2] HTML tr 20 / Transition Period / nested table · record 17e2a768f137d7e761d5e43133e4a2d58952dc0595b0402a163955db95828697
  • [3] HTML tr 16 / Extent of Recognition / nested table · record 18b66abaf245774e2c1de90aca4d17ee794103406c7b5e680d490f43fd4f4876

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 267 · record 2484fe9dfa8c9131dda84361d9fd1b49bd0d024e04f470bc8fb31f8af5b855f3
  • [5] CSV row 1490 · record 8d5f5b38b23157c73b5bc9cf18f7f0ccca8f68ed74f5497a63879cd2f58d562a

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