Compliance research

CLSI M100 35th Edition — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 7-327 to 7-328 and state declaration-acceptance date(s) for the replaced recognition: recognition 7-327: 2027-07-04. 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-327
CLSI M100 34th Edition

Performance Standards for Antimicrobial Susceptibility Testing

Partial

Partial recognition. The following part(s) of the standard is (are) not recognized: Exceptions are noted on the FDA Antimicrobial Susceptibility Test Interpretive Criteria (STIC) webpage (https://www.fda.gov/Drugs/DevelopmentApprovalProcess/DevelopmentResources/ucm575163.htm). In the absence of interpretive criteria and quality control parameters on this FDA webpage, consult the technical contacts below.

[2] [5]
Exported transition expiration: 07/04/2027
FDA 7-328
CLSI M100 35th Edition

Performance Standards for Antimicrobial Susceptibility Testing

Partial

Partial recognition. The following part(s) of the standard is (are) not recognized: Exceptions are noted on the FDA Antimicrobial Susceptibility Test Interpretive Criteria (STIC) webpage (https://www.fda.gov/Drugs/DevelopmentApprovalProcess/DevelopmentResources/ucm575163.htm). In the absence of interpretive criteria and quality control parameters on this FDA webpage, consult the technical contacts below.

[1] [3]
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-327 → 7-328

FDA recognition of CLSI M100 34th Edition [Rec# 7-327] will be superseded by recognition of CLSI M100 35th Edition [Rec# 7-328]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 7-327] until July 4, 2027. After this transition period, declarations of conformity to [Rec# 7-327] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [4] [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 M100 35th Edition and the replaced designation(s) CLSI M100 34th 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-327: 2027-07-04. 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 — 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

  • [1] CSV row 226 · record 3b5ca67774097b62a0a248e87b190c331572ff91c52e00c76c6f39c494fce653
  • [5] CSV row 327 · record 7d031e13b4c2cfc4dfe3a6f1ead9ad2098156e8edd7da48cdf750a28cf755403

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 b54eb42004f865573ce8ac76d10acacf14eea304e8c68ab23258ebdf65329202

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 404e85c8f1979d08c4caf088e2a887e972ed26d62366ccdcbd120b2213899b43
  • [6] HTML tr 23 / Transition Period / nested table · record e996b69656212bbb5d7311a6445986af643399d35b31b4a3a1eb26ca0212bd11

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 b53bdb5bd5ada58560e79cb44115cf0f8d4ed442daa65e6a60d28b84f1a22891

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 54f1935b0a8ccab627760dfd64671f17e4e313539358b4aa1e89a22c6a62e311
  • [4] HTML tr 23 / Transition Period / nested table · record 5a3aabc7615b9a80d42b243c973c6affaefa152769bff052c7fc3a99b9f16113

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