Compliance research

ASTM F2026-23 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 8-475 to 8-609 and state declaration-acceptance date(s) for the replaced recognition: recognition 8-475: 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-475
ASTM F2026-17

Standard Specification for Polyetheretherketone (PEEK) Polymers for Surgical Implant Applications

Complete

Complete standard

[2] [3]
Exported transition expiration: 12/20/2026
FDA 8-609
ASTM F2026-23

Standard Specification for Polyetheretherketone (PEEK) Polymers for Surgical Implant Applications

Complete

Complete standard

[1] [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 8-475 → 8-609

FDA recognition of ASTM F2026-17 [Rec# 8-475] will be superseded by recognition of ASTM F2026-23 [Rec# 8-609]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 8-475] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 8-475] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [5] [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 ASTM F2026-23 and the replaced designation(s) ASTM F2026-17. 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-475: 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 2e590fe2bef6ce21a5b2a80c1a531bea868b8cc83933c6bdb0abfdbe08f0e88e

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 10277cd4eea2dd39b3e6431cd529dc057c6893933b7026d5cdb0a1fb7ece7562
  • [5] HTML tr 22 / Transition Period / nested table · record c0079f7e21f9c9891eee88677f1d0b23caf734055cfa8f1667b25a6cbecc4317

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 1271 · record 21d1704903ec5c872f0278bfcf26c639301bba74a9debb97a342e3b83c824121
  • [4] CSV row 479 · record 677ab54c8ed504e75761d1728d894b6a89c4f3d9a842a8a9e27ccd732c8d6731

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 3e1c1c051117e44cc75efbe9b4c2925bb5ae616855588ab7a3502ac9afc26223

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 334cfb0a0a4d7f676a08936d5cab696e4cfbb78f50850235883e73f34abaaa40
  • [6] HTML tr 22 / Transition Period / nested table · record d8abde2528a2a34682093b71be5779e1577c7e2fbf59e83cfb72414e21218b3f

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