Compliance research

IEEE Std 11073-10103 Second edition 2023 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 13-84 to 13-146 and state declaration-acceptance date(s) for the replaced recognition: recognition 13-84: 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 13-84
ISO IEEE 11073-10103 First edition 2014-03-01

Health informatics - Point-of-care medical device communication - Part 10103: Nomenclature - Implantable device cardiac

Complete

Complete standard

[1] [3]
Exported transition expiration: 07/04/2027
FDA 13-146
IEEE Std 11073-10103 Second edition 2023

Health informatics - Point-of-care medical device communication - Part 10103: Nomenclature - Implantable device cardiac

Complete

Complete standard

[5] [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 13-84 → 13-146

FDA recognition of ISO IEEE 11073-10103 First edition 2014-03-01 [Rec# 13-84] will be superseded by recognition of IEEE 11073-10103 Second edition 2023 [Rec# 13-146]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 13-84] until July 4, 2027. After this transition period, declarations of conformity to [Rec# 13-84] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [2] [4]

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 IEEE Std 11073-10103 Second edition 2023 and the replaced designation(s) ISO IEEE 11073-10103 First edition 2014-03-01. 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 13-84: 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 1498 · record 0d3aa262920faad4bfac0c03ed3da40bfe1ec9858575c3938a30a84e486c7ec7
  • [5] CSV row 276 · record 778a7388ddb4a3fdc8a0cd82d64f2b393bc22a8783c4dc2b6aaf389b324e99a4

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 c57da52a17c4a6c89488bc406fb5ba817d4aaf43feb4b6e57ff1f8781dea6df2

  • [2] HTML tr 22 / Transition Period / nested table · record 3c78d62a3d2288b81be48fce760918c96b46c89ec9a92689c06d92bf657c4102
  • [3] HTML tr 18 / Extent of Recognition / nested table · record 533f009e8696afc26e41b58f86731b192428042992b2cdbf4f3801f5bd3ef9e7

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 5f5f844ad38bf1d170c3726146168be56e6df6f3d79409aec923b61d5234dd2b

  • [4] HTML tr 22 / Transition Period / nested table · record 58d0a228b24e9deaa16a936688d99f0455925f884c99b0f0349ab0be222fac7c
  • [6] HTML tr 18 / Extent of Recognition / nested table · record 7b34b213cde8fe0735820e80cb7eb477bf291a6d3c86c324f7be9ce6813b7a72

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