Compliance research

CLSI M02 14th Edition — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 7-280 to 7-325 and state declaration-acceptance date(s) for the replaced recognition: recognition 7-280: 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 7-280
CLSI M02 13th Edition

Performance Standards for Antimicrobial Disk Susceptibility Tests

Complete

Complete standard

[2] [3]
Exported transition expiration: 12/20/2026
FDA 7-325
CLSI M02 14th Edition

Performance Standards for Antimicrobial Disk Susceptibility Tests

Partial

Partial recognition. The following part(s) of the standard is (are) not recognized: Appendix E. Test for Performing Disk Diffusion Directly from Positive Blood Culture Broth

[4] [5]
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 7-280 → 7-325

FDA recognition of CLSI M02 13th Edition [Rec# 7-280] will be superseded by recognition of CLSI M02 14th Edition [Rec# 7-325]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 7-280] until December 20, 2026. After this transition period, declarations of conformity to [Rec# 7-280] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [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 CLSI M02 14th Edition and the replaced designation(s) CLSI M02 13th Edition. 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 7-280: 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 6c06bc14d2d25ab34bd73aa1b02369d35b26f218d06fc0fbac9b8b35d06ed3e8

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

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 1258 · record 58b722e12e072bf184edc0938b529db006a5dfb5e2278a0449253a4b89674d0a
  • [5] CSV row 325 · record be725ab81d99175772cb3e6cf7693429d7772c3953a95112649d90ce4d0d72a4

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 fd041ba5da5b8780bc965f2d08c74af94e46d8a167c9ce70f561d46cffba4748

  • [4] HTML tr 18 / Extent of Recognition / nested table · record 84b42e5f4fa3dca306d19295b3a32e52f24185e49da21c6fffe199acdececf5c
  • [6] HTML tr 23 / Transition Period / nested table · record fe9e9c94e24bea1fe2a402ca4c0c3635af37ee4baf435efbb6dce4ba6cb985a1

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