Compliance research

ASTM F2537-23 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 8-412 to 8-606 and state declaration-acceptance date(s) for the replaced recognition: recognition 8-412: 2026-12-20. 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 8-412
ASTM F2537-06 (Reapproved 2017)

Standard Practice for Calibration of Linear Displacement Sensor Systems Used to Measure Micromotion

Complete

Complete standard

[1] [3]
Exported transition expiration: 12/20/2026
FDA 8-606
ASTM F2537-23

Standard Practice for Calibration of Linear Displacement Sensor Systems Used to Measure Micromotion

Complete

Complete standard

[4] [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 8-412 → 8-606

FDA recognition of ASTM F2537-06 (Reapproved 2017) [Rec# 8-412] will be superseded by recognition of ASTM F2537-23 [Rec# 8-606]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 8-412] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 8-412] 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 ASTM F2537-23 and the replaced designation(s) ASTM F2537-06 (Reapproved 2017). 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 8-412: 2026-12-20. 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 69683cca8c8e57c6f4c6e38e715f22ef556b9f43c46e8a556c04df3f2987a3d4

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 0bae95a86b43c82b606edad09f64b5b2a9012346353bb785ea1311765d948bc6
  • [5] HTML tr 22 / Transition Period / nested table · record bcb0d88904c1c74936a40fa0bc4304454d43b510caaec63a893f067687a64171

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 beae1f30591ea983a2139cf2a820ea361a5a1b653075f338e02d145cf21873d8

  • [2] HTML tr 22 / Transition Period / nested table · record 338f0bc5839c1a28e9b8bbb93cc3e925531e0fa895c7ea6a2cec2c4d9cc22831
  • [4] HTML tr 18 / Extent of Recognition / nested table · record a4bd849becbdc3435055cbb971ab4c923ae829b39cc49ef15a36fc3cde9e0cde

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 1263 · record 76cce4f4dc407d246808963fd56a0f415d7d677103ecef97c0b92f8d2d4960ed
  • [6] CSV row 476 · record fd8d7909adf883c03db1da883418f10e1a5c60ed8670c8e11bd6bcef83d669e2

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