Compliance research

IEEE Std 11073-10419:2023 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 13-81 to 13-145 and state declaration-acceptance date(s) for the replaced recognition: recognition 13-81: 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-81
IEEE Std 11073-10419:2015; ISO IEEE 11073-10419 First edition 2016-06-15

Health informatics - Personal health device communication - Part 10419: Device Specialization - Insulin Pump; Health informatics - Personal health device communication - Part 10419: Device specialization - Insulin pump

Complete

Complete standard

[1] [2] [3]
Exported transition expiration: 07/04/2027
FDA 13-145
IEEE Std 11073-10419:2023

Health informatics - Device Interoperability Part 10419: Personal health device communication - Device Specialization - Insulin Pump

Complete

Complete standard

[4] [7]
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-81 → 13-145

FDA recognition of IEEE Std 11073-10419:2015 [Rec# 13-81] will be superseded by recognition of IEEE Std 11073-10419:2023 [Rec# 13-145]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 13-81] until July 4, 2027. After this transition period, declarations of conformity to [Rec# 13-81] 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 IEEE Std 11073-10419:2023 and the replaced designation(s) IEEE Std 11073-10419:2015; ISO IEEE 11073-10419 First edition 2016-06-15. 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-81: 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 1549 · record 011b20e6e2d56eb120744bcaeb8c922ac5a61ea864c97ed8e404d884d521da8f
  • [2] CSV row 1550 · record 5c833108da7a73b670b7fdcda3b6480478fe03ca404d2a0d8c63b74024d584e6
  • [4] CSV row 275 · record 7479d9db5945361417aa97c050e084a4af49751cf06157c5b4cb0afba9f034d7

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 d5d1395b3d6151fb6a5b4787f1cb6f41271a9578f41845e15b6c1b9d9affa66a

  • [3] HTML tr 20 / Extent of Recognition / nested table · record 68dcb83f02501885356008fb9007f48df22ffdf577e5d3bd635019ca0b953af4
  • [6] HTML tr 24 / Transition Period / nested table · record d3b5e791d5e60fcbe0a136495dc94f5e9936ceb4a9de979c18748c555a031cb7

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 607eabec7f1ae993bfb541a09a7c7d2fe5edf0d47b2142e083ef154df1a7833b

  • [5] HTML tr 22 / Transition Period / nested table · record 84164f8aace96ff7a8a53f0e19fad98fb496e6341324305e855cdc3e1a8e05dc
  • [7] HTML tr 18 / Extent of Recognition / nested table · record e97ff12ecb075163419ed175ee7c98624b9407f494a35d30e579464e5ed4048c

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