Compliance research

CLSI EP37 2nd Edition — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 7-284 to 7-348 and state declaration-acceptance date(s) for the replaced recognition: recognition 7-284: 2027-12-19. 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-284
CLSI EP37 1st Edition

Supplemental Tables for Interference Testing in Clinical Chemistry

Complete

Complete standard

[2] [5]
Exported transition expiration: 12/19/2027
FDA 7-348
CLSI EP37 2nd Edition

Supplemental Tables for Interference Testing in Clinical Chemistry

Complete

Complete standard

[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-284 → 7-348

FDA recognition of CLSI EP37 1st Edition [Rec# 7-284] will be superseded by recognition of CLSI EP37 2nd Edition [Rec# 7-348]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 7-284] until December 19, 2027. After this transition period, declarations of conformity to [Rec# 7-284] 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 EP37 2nd Edition and the replaced designation(s) CLSI EP37 1st 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-284: 2027-12-19. 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 130 · record 168265422953b9580b328a9030b116f4056d76d71f59c9043711775180a424bc
  • [5] CSV row 1260 · record 6bb893e5babf17b037234a029f6e29d7f53956956556dd346006a3d964312fc9

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 e754f04a6841eb04dc1f0d8d829a200ffa9bda84c55c8e0ccbca7a7615c94cf2

  • [2] HTML tr 18 / Extent of Recognition / nested table · record 31c669844e9f90482872cb007209c3e1f5558f5a1d6f939143a8ebafb2379aa1
  • [6] HTML tr 22 / Transition Period / nested table · record e91bf1614d970d203ceb82c63622e5c5b0357b9803880ccb9cafc5dec1649439

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 c9765059434df45757f82c3d9da7ac81cd31fb0597ce2e9e7e39b83664d4e2ff

  • [3] HTML tr 18 / Extent of Recognition / nested table · record 41bdfc1542e787230831fed176b4f4c2cbd87e3ff19b4db167d09c274b55690b
  • [4] HTML tr 22 / Transition Period / nested table · record 583b3b58b6e4ebeb3e4a40be64d4d809d2628d16c7f6caff8a3e015914258ee7

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