美国 FDA 注册与列名和检测报告的关系

结论：注册列名不审查检测报告，上市许可才审查

进入美国市场时，企业会遇到两组不同的动作：一组是注册与列名，另一组是上市许可（多数产品走 510(k) 路径，部分豁免）。

这两件事常被混为一谈，而它们与检测报告的关系完全不同：注册列名是告知性的程序，不审查你的检测数据；上市许可才是实质性审查，检测报告是核心证据之一。

理解这个区别，能避免两类常见错误：以为完成了注册列名产品就可以合法销售；或者以为注册列名需要提交全套检测报告而做了不必要的准备。

两者的区别

第三行是关键。 注册列名时不需要提交检测报告，但这不意味着不需要有——产品仍然必须符合适用要求，只是这一步不检查。检查发生在别处：上市许可审查时、以及现场检查时。

检测报告在哪一步起作用

在上市许可申请中。 这是检测报告最集中使用的地方。需要提交的通常包括性能测试、生物相容性、电气安全与电磁兼容、灭菌与包装、软件验证等，具体取决于产品。

在豁免产品的合规文件中。 有些产品豁免上市许可，但仍需符合适用要求。这时候检测报告不提交给监管方，但企业自己要有，并且在现场检查时能拿得出来。

在现场检查时。 检查会查看质量体系记录，其中包括设计验证确认的数据、过程确认的数据、以及日常检验记录。

在上市后的问题处理中。 出现投诉或不良事件时，需要用数据说明产品的实际表现。

常见的理解偏差

偏差一：完成注册列名就可以卖。 如果产品需要上市许可而未获得，仅完成注册列名是不能合法销售的。

偏差二：豁免产品不需要做检测。 豁免的是上市许可这个程序，不是符合性要求。产品仍要满足适用的要求，并且要有证据。

偏差三：有了检测报告就能通过审查。 报告只是证据之一，还要看它是否覆盖了必要的项目、是否与你的产品对应、以及与其他资料是否一致。

偏差四：国内的报告直接能用。 报告能否被接受，取决于出具方的资质、方法的适用性、以及报告内容的完整性。这一点较好在做检测之前就确认清楚，而不是做完再问。

准备上的建议

先确定路径再安排检测。 产品走哪条路径、是否豁免，决定了检测的范围和报告的形式要求。路径不明就开始测，很可能测偏。

确认实验室的资质与报告形式。 把计划的项目清单给实验室，确认哪些在其能力范围内、报告会做成什么形式。

方法选择要对应目标市场。 同一项性能可能有多个方法标准，选择时要考虑目标市场的接受情况。

保留完整记录。 即使是豁免产品，检测记录也要按体系要求保存，现场检查时会用到。

与其他市场的协同

如果产品同时面向多个市场，检测安排可以协同：

先梳理各市场的要求，找出重叠部分；重叠的项目按较严的口径做一次，多处使用；差异的项目单独安排。

报告的语言和形式也要提前考虑。 一份报告如果一开始就按通用形式出具，多市场使用时会省很多事；出具之后再调整格式，要走更正程序。

代理人与报告的关系

进入美国市场通常需要指定代理人。代理人的职责与检测报告没有直接关系，但有一点值得注意：监管方的问询可能通过代理人转达，其中可能涉及检测数据的澄清。

所以代理人应当能够联系到掌握技术细节的人，或者企业内部要有明确的响应流程。代理人只负责转递而技术侧无人对接，问询的响应会拖延。

报告有效期的问题

检测报告本身通常不设有效期，但其有效性取决于产品是否变化、方法是否更新。对于长期在售的产品，建议定期回看：报告依据的方法版本是否仍然适用、产品是否发生过累积变更。

这件事没有触发机制就不会有人做，建议在体系中设置定期复核的节点。

产品变更后的处理

获得上市许可之后产品发生变更，要判断变更是否需要重新申请。这个判断与检测直接相关：如果变更影响了安全性或有效性，通常需要新的数据支撑，可能还要重新申请。

建议在变更评审时同步评估市场准入影响，而不是只看国内的变更要求。同一个变更在不同市场的处理方式可能不同。

标签与说明书的检测关联

标签和说明书上标注的性能参数，需要有检测数据支撑。这一点在准备材料时容易被忽略——技术资料里的数据准备得很充分，而标签上随手写的一个参数没有对应的实测值。

建议把标签和说明书上的所有量化表述列出来，逐条对应到检测数据。没有数据支撑的表述，要么补测，要么删掉。

我们的做法

承接面向美国市场的委托时，我们会先确认产品的路径与目标——是准备上市许可申请，还是豁免产品的合规储备。两者对报告的要求不同，前者更强调项目覆盖与方法对应，后者更强调记录完整与可追溯。

我们也会在委托阶段说明报告会以什么形式出具、包含哪些信息，让委托方能提前判断是否满足使用需求。这比报告出来之后再发现形式不合适要省事。

如果你在准备美国市场的相关材料，对检测范围或报告形式有不确定，可以把产品信息和计划路径发过来一起看，或者直接联系：132 4819 8029。能力范围见服务介绍，送检要求见送检要求，流程见检测流程。

English version

Conclusion. Entering the United States market involves two distinct sets of actions: establishment registration and device listing on one side, and marketing authorisation on the other, which for most devices means a 510(k) submission while some are exempt. These are frequently conflated, and their relationship to test reports is entirely different. Registration and listing are notification procedures that do not examine your test data. Marketing authorisation is substantive review in which test reports are central evidence.

Understanding the distinction avoids two common errors: believing that completing registration and listing permits lawful marketing, and believing that registration and listing require submitting a full set of test reports, leading to unnecessary preparation.

The differences. Registration and listing are notification in character, submit basic company and product information, involve no submission of test reports, carry no technical review, result in an entry on a register and take relatively little time. Marketing authorisation is substantive, requires a complete technical file including test data, treats reports as core evidence, involves technical review, results in authorisation to market and takes considerably longer.

The point about reports is the crucial one. No test report is submitted at registration and listing, which does not mean none is needed. The product must still meet applicable requirements; this step simply does not check. Checking happens elsewhere: during marketing authorisation review, and during inspection.

Where reports actually matter. In a marketing authorisation submission, where reports are used most intensively, typically covering performance, biocompatibility, electrical safety and electromagnetic compatibility, sterilisation and packaging, and software verification, depending on the device. In the compliance file for exempt devices, where reports are not submitted to the regulator but must exist and be producible during inspection. During inspection, where quality system records including design verification and validation data, process validation data and routine inspection records are examined. And in post-market problem handling, where data are needed to explain actual product behaviour.

Common misunderstandings. That completing registration and listing permits sale: where authorisation is required and has not been obtained, it does not. That exempt devices need no testing: the exemption applies to the authorisation procedure, not to the substantive requirements, and evidence is still needed. That having a report guarantees clearance: a report is one item of evidence, and what matters is whether it covers the necessary items, corresponds to your product, and agrees with the rest of the file. And that a domestic report is automatically usable: acceptance depends on the issuing body's accreditation, the applicability of the method and the completeness of the report, which is best confirmed before testing rather than afterwards.

Preparation. Settle the pathway before arranging testing, since whether the device requires authorisation or is exempt determines the scope of testing and the form of the reports; testing before the pathway is clear commonly produces the wrong work. Confirm the laboratory's accreditation and the form of its reports by sending the planned item list in advance. Choose methods with the target market in mind, since the same property may have several method standards with differing acceptance. And retain complete records even for exempt devices, because inspection will look at them.

Coordinating across markets. Where a product addresses several markets, map the requirements, identify the overlap, run the overlapping items once to the stricter reading for use everywhere, and arrange the divergent items separately. Consider report language and format in advance as well: a report issued in a generally applicable form from the outset saves considerable effort across markets, whereas changing format after issue requires a correction procedure.

How we handle it. For work aimed at the United States we first confirm the pathway and purpose, whether preparing an authorisation submission or building a compliance file for an exempt device. The emphases differ: the former stresses item coverage and method correspondence, the latter stresses record completeness and traceability. We also state at the commissioning stage what form the report will take and what it will contain, so the client can judge suitability in advance rather than discovering a mismatch after issue.

Send us the product information and intended pathway and we will review. Phone or WeChat: +86 132 4819 8029.