Cruxi
Compliance research
FDA’s acquired supplementary sheets explicitly connect 13-56 to 13-147 and state declaration-acceptance date(s) for the replaced recognition: recognition 13-56: 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
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 / edition | Public recognition limitations | Declaration transition context |
|---|---|---|
| FDA 13-56 IEEE Std 11073-10406-2011; ISO IEEE 11073-10406 First edition 2012-12-01 Health informatics - Personal health device communication - Part 10406: Device specialization - Basic electrocardiograph (ECG) (1- to 3-lead ECG); Health informatics - Personal health device communication Part 10406: Device specialization - Basic electrocardiograph (ECG) (1- to 3-lead ECG) | Complete Complete standard [3] [4] [7] | Exported transition expiration: 07/04/2027 |
| FDA 13-147 IEEE Std 11073-10406-2023 Health informatics - Device Interoperability Part 10406: Personal health device communication - Device Specialization - Basic electrocardiograph (ECG) (1- to 3-lead ECG) | Complete Complete standard [2] [6] | No expiration date is stated in this acquired export row. That is not a guarantee of indefinite recognition. |
FDA recognition of IEEE Std 11073-10406-2011 [Rec# 13-56] will be superseded by recognition of IEEE Std 11073-10406-2023 [Rec# 13-147]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 13-56] until July 4, 2027. After this transition period, declarations of conformity to [Rec# 13-56] will not be accepted.
Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [5]
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.
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.
Reconcile each report and declaration against IEEE Std 11073-10406-2023 and the replaced designation(s) IEEE Std 11073-10406-2011; ISO IEEE 11073-10406 First edition 2012-12-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.
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.
Record planned declaration/submission dates against the FDA sheet’s acceptance date(s): recognition 13-56: 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.
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.
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.
Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.
Version not stated by the source · retrieved 2026-10-07
Source key D02 · snapshot 25ae86e4cad0d936d867c1a5f23a7220ef2e992ea1b2993f2709cce77dc139d5
Version not stated by the source · retrieved 2026-10-07
Source key D02 · snapshot 94ccf56dc846c7f6d78d6ad77dc6e87d1803ac3612af01d6894949e34c4a78d8
Version not stated by the source · retrieved 2026-10-07
Source key D02 · snapshot 891ba3adfc6e9b77ac54dff5bddca3d19669e7a83e06b8814d3ab8e5891eaa3d
Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.