加拿大 MDL 申请需要哪些检测证据

结论：先看级别，级别决定证据的深度

加拿大对医疗器械按风险分级管理，级别不同，申请要求差别很大——低级别的可能只需要体系层面的证明，高级别的则需要提交完整的安全与有效性证据。

所以准备工作的第一步不是收集报告，而是确认产品属于哪一级。级别判断错了，后面的准备要么不足要么过度。

分级与证据要求的对应

中等级别以上，检测数据就是核心内容之一。 需要覆盖的通常包括：产品性能、安全性（电气、机械等适用项）、生物相容性、灭菌与包装、以及软件相关验证。

体系证书的前置作用

加拿大的一个特点是：质量管理体系证书是申请许可的前置条件，而且这个体系认证有指定的路径。

这意味着时间规划上，体系认证要排在产品许可申请之前完成。而体系审核本身会查检测相关的记录（设备校准、方法确认、检验记录、供方评价），所以这部分工作实际上更早就要就位。

常见的规划失误是把体系和产品许可并行准备，结果体系证书没下来，产品申请无法提交，前面做的产品资料只能等着。

检测证据的组织

提交的证据建议按这个逻辑组织：

产品描述与预期用途。 这是判断哪些要求适用的基础。

适用标准清单。 列出执行的标准，说明为什么这些标准适用于本产品。

逐项的检测数据。 每个标准或要求对应的报告，给出实测结果。

符合性说明。 明确说明产品满足各项要求，依据是什么。

未测项目的说明。 判断为不适用的，给出理由。

与其他市场的技术文档结构相近，所以已有欧盟或美国资料的，多数内容可以改编使用，不必重做。

常见的准备遗漏

标签与说明书的语言要求。 加拿大有双语要求，这一点常被忽略。说明书上的性能参数要与检测报告一致，双语版本之间也要一致。

体系证书的覆盖范围。 证书要覆盖申请的产品类别和生产场地。范围不匹配时申请会被卡住。

代表与进口安排。 相关的责任主体要提前确定。

检测报告的时效与代表性。 距今较久的报告，如果产品有过变更，代表性会被质疑。

这四项里，前两项是程序性的，后两项与检测直接相关。

与其他市场的协同

如果产品已经在其他市场上市，多数检测数据可以复用。复用时要确认的是：

方法标准是否被接受；报告内容是否完整；语言是否满足要求；样品与当前产品的对应关系是否仍然成立。

加拿大的体系认证路径与多国审核方案有衔接，如果企业已经通过相应的多国审核，体系这一环可以直接使用，这是规划上值得利用的一点。

时间规划建议

按依赖关系倒排：

体系认证是前置，先启动；检测与产品资料准备可以与体系认证并行；产品许可申请在体系证书到手后提交；标签与说明书的双语版本在申请前完成。

体系认证的周期通常较长，是整个时间表的决定项。如果企业尚未建立体系或体系证书不覆盖目标产品，这部分时间要留足。

后续维护

获得许可之后，产品变更、体系证书续期、年度相关义务都需要跟进。与检测相关的是：

产品变更时要判断是否需要更新许可以及补充数据；体系证书续期时会再次审核检测记录；上市后出现问题时需要数据支撑分析。

建议把这些节点纳入内部的合规日历，避免临期才发现要准备。

双语材料的准备

双语要求在实务上会产生额外工作量，而且容易出错。建议的做法是：先定稿一种语言，再翻译，而不是两种语言并行编写。并行编写时，一处修改容易漏掉另一处。

翻译之后要做一次交叉核对，重点是数字、单位、型号这类容易出错的内容。性能参数如果两个语言版本不一致，是明确的问题。

与体系审核的衔接

体系审核中涉及检测的部分，与产品申请中的检测证据是相互印证的关系：体系证明你有能力持续产出合格产品，产品证据证明这一批确实合格。

两者如果对不上会很显眼——比如产品资料里的检验项目，在体系的检验规程里找不到对应。准备时建议把两边的清单对照一遍。

现场检查的可能

除了资料审查，还可能面临现场检查。检查会看实际的生产和质量控制情况，其中包括检测环节：设备是否如资料所述、检验是否按规程执行、记录是否完整。

资料与现场不一致是较严重的问题。 准备资料时描述的检验能力和流程，要与现场实际相符。为了资料好看而写超出实际的内容，现场一查就露馅。

许可后的变更管理

获得许可之后的产品变更，需要判断是否影响许可的有效性。与检测相关的判断依据是：变更是否影响了支撑许可的安全有效性证据。

建议建立一个简单的判断流程：变更评审时增加一项「是否影响已提交的检测证据」，答是则进一步评估是否需要通知或重新申请。没有这个环节，变更累积到一定程度可能使原许可的基础不再成立。

我们的做法

承接面向加拿大的委托时，我们会先确认产品的风险级别与体系认证状态。级别决定检测深度，体系状态决定时间排序，这两点不清楚就排不好计划。

对于已经有其他市场报告的委托方，我们会先看现有报告能覆盖多少，只补差额部分。实际操作中，能复用的比例通常不低，重新全做一遍是浪费。

如果你在准备加拿大市场的申请，不确定检测需要做到什么程度，可以把产品资料和现有报告发过来一起评估，或者直接联系：132 4819 8029。能力范围见服务介绍，送检要求见送检要求，更多内容见知识库。

English version

Conclusion. Canada manages medical devices by risk class, and requirements differ substantially between classes. Lower classes may rely largely on quality system evidence, while higher classes require a complete body of safety and effectiveness evidence. Preparation therefore begins not with gathering reports but with confirming the class. Getting the class wrong leaves preparation either inadequate or excessive.

Class and depth of evidence. At lower classes, evidence rests mainly on system certification with relatively simplified product documentation. At intermediate classes, supporting safety and effectiveness evidence including test data must be submitted. At higher classes, complete technical evidence is needed, covering detailed testing, clinical material and risk documentation. From intermediate classes upward, test data become a core component, typically covering performance, applicable safety aspects such as electrical and mechanical, biocompatibility, sterilisation and packaging, and software verification.

The quality system certificate as a prerequisite. A distinctive feature of the Canadian framework is that a quality management system certificate is a precondition for a device licence, obtained through a designated route. For planning this means system certification must complete before the device application. System auditing itself examines testing-related records, covering equipment calibration, method validation, inspection records and supplier evaluation, so that work must be in place considerably earlier. A frequent planning error is preparing the system and the device application in parallel, only to find the application cannot be submitted because the certificate has not issued, leaving completed product documentation waiting.

Organising the evidence. Structure it as product description and intended use, which establishes which requirements apply; a list of applicable standards with reasons for their applicability; test data item by item, with measured results against each standard or requirement; a conformity statement explaining that requirements are met and on what basis; and explanations for untested items judged inapplicable. The structure resembles technical documentation for other markets, so existing European or American material can largely be adapted rather than recreated.

Frequent omissions. Bilingual labelling and instruction requirements, which are easily overlooked, where performance parameters must agree with the test reports and the two language versions must agree with each other. The scope of the system certificate, which must cover the product category and manufacturing site, since a mismatch stalls the application. Representation and import arrangements, which need settling early. And the currency and representativeness of reports, since older reports are questioned where the product has changed. The first two are procedural; the last two bear directly on testing.

Coordination with other markets. Where a product is already marketed elsewhere, most test data can be reused, subject to confirming that the method standard is accepted, the report is complete, the language meets requirements, and the relationship between the tested samples and the current product still holds. The Canadian system certification route connects with the multi-jurisdiction audit programme, so a manufacturer already assessed under it can use that for the system element, which is worth exploiting in planning.

Scheduling. Work back from dependencies. System certification is the prerequisite and should start first. Testing and product documentation can proceed in parallel with it. The device application follows once the certificate is in hand. Bilingual labelling and instructions complete before submission. System certification generally has the longest lead time and governs the overall schedule, so where no system exists or the certificate does not cover the target product, allow generous time.

Maintenance afterwards. Product changes, certificate renewal and annual obligations all need attention. On the testing side, product changes require judging whether the licence needs updating and whether supplementary data are needed; certificate renewal re-examines testing records; and post-market problems require data to support analysis. Add these points to an internal compliance calendar rather than discovering them as deadlines approach.

How we handle it. For Canadian work we confirm the risk class and the system certification status first, since class determines the depth of testing and system status determines the sequence, and without both the plan cannot be built. Where clients already hold reports for other markets, we assess how much they cover and address only the difference. In practice the reusable proportion is usually substantial and repeating everything would be wasteful.

Send us the product information and existing reports and we will assess what is needed. Phone or WeChat: +86 132 4819 8029.