韩国 MFDS 注册的检测与 GMP 衔接

结论：产品注册与体系审查是两条线，要并行但有先后依赖

进入韩国市场，通常要处理两件事：产品层面的注册，以及生产质量体系层面的审查。 两者是分开的流程，但存在依赖关系——体系审查的结果会影响产品注册的推进。

实务中常见的规划失误是把两者当成一件事，或者按顺序串行处理。前者会漏掉工作，后者会让周期拉得很长。

合理的做法是并行启动，在依赖节点上对齐。

检测数据的准备

产品注册需要提交技术资料，其中检测数据是核心部分。通常需要覆盖：

产品性能，对应技术要求的实测结果；安全性，电气与机械等适用项；生物相容性，按接触情况确定；灭菌与包装，无菌产品适用；软件相关验证。

这些项目与其他市场高度重合，所以已有的数据多数可以复用。要确认的是方法标准是否被接受、报告内容是否完整。

本地标准与本地测试

需要核对的是：适用的标准是否有本地采纳版本、本地版本与国际版本有无技术差异、以及某些项目是否要求在当地完成测试。

「是否要求本地测试」这一点对规划影响最大。 如果某些项目必须在当地做，那么样品要运过去、周期要按当地实验室的排期算，整体时间会明显延长。

建议在项目启动时就确认这一点，而不是等资料准备到一半才发现。

与体系审查的衔接

体系审查会查看质量管理体系的运行情况，其中与检测相关的包括：

检验规程与实际执行是否一致；设备的校准状态；检验人员的资质；检验记录的完整性；不合格品的处置；以及外部检测机构的评价与管理。

这些内容与产品注册提交的检测数据是相互印证的关系。 产品资料里说做了某项检验，体系里就应当有对应的规程和记录。两边对不上会引出问题。

所以准备时建议做一次对照：把产品注册资料里涉及的检验项目列出来，逐项确认体系文件里有对应的规程、实际有对应的记录。

时间规划的建议

按依赖关系排：

最先启动： 本地标准差异核对、是否需要本地测试的确认。这两项决定了后面的工作量。

并行推进： 检测数据准备（含可能的本地测试）、技术资料编写、体系文件梳理。

对齐节点： 体系审查与产品注册的相互依赖点，按实际要求安排先后。

收尾： 本地语言资料的准备与核对。

本地测试如果需要，通常是周期的决定项，因为它涉及样品运输、当地排期、以及可能的沟通往返。

样品运输的考虑

如果需要送样到当地测试，运输环节要提前规划：产品是否含电池（涉及危险品运输）；样品数量；通关所需文件；以及测试后样品的处置。

含锂电池的产品在这一环节容易卡住，相关准备要更早启动。

资料的语言

提交资料通常需要本地语言。技术附件的语言要求可能相对宽松，但主体资料需要翻译。

翻译时要注意技术参数的准确性，并确保与检测报告、说明书之间一致。参数在翻译过程中出错，是很容易发生又不容易发现的问题。

后续维护

获得注册之后，产品变更、体系证书的维持、定期的更新义务都要跟进。

与检测相关的是：变更时要判断是否影响已提交的数据；体系的定期审查会再次查看检验记录。建议把这些节点纳入统一的合规日历，与其他市场的义务一起管理。

两条线的工作内容对照

把产品注册和体系审查的工作内容并排列出来，更容易看清哪些可以共用：

从表里能看出：技术要求和型式检测报告是两条线共用的。 所以这两项做扎实，两边都受益；反过来，如果技术要求写得含糊，两边都会出问题。

关于检验外包的管理

如果把部分检验外包给第三方机构，体系审查时会查看对外部机构的管理：

选择依据是什么，有没有评价记录；机构的资质是否覆盖所委托的项目；委托的项目清单是否明确；收到报告后有没有确认与审核的动作；以及定期的再评价。

很多企业在这一项上准备不足——报告有，但选择和评价的记录没有。建议建立一份外部机构清单，记录资质信息、委托项目、评价结论和评价日期，每年更新一次。这份清单本身就是最直接的证据。

风险管理文件的衔接

风险管理文件在两条线上都要用到，而它与检测数据的关系是双向的：

风险分析识别出的危害，需要通过检测来验证控制措施有效。 比如识别出过热风险，就要有温升测试；识别出机械伤害风险，就要有相应的结构强度或防护验证。

检测中发现的问题，应当反馈到风险文件。 比如测试中出现了预期之外的失效模式，风险分析里应当补充。

实务中常见的脱节是：风险文件和检测报告各做各的，互相不引用。 审查时一比对就能看出来——风险控制措施写了一堆，但没有一条能指向具体的验证证据。

建议做一张对照表：左边列风险控制措施，右边列对应的验证方式和证据编号。这张表在两条线的审查中都用得上，做一次省两次事。

我们的做法

承接面向韩国的委托时，我们会先确认两件事：现有报告能覆盖多少、以及是否存在必须本地完成的项目。后者决定了我们能做的范围，说清楚之后委托方才好安排整体计划。

对于可以在我们这边完成的项目，我们会按较详细的口径出具报告（含条件、实测值、设备信息），这个详细程度通常能满足多个市场的需要，减少重复。

如果你在准备韩国市场的注册，想先理清检测部分的范围和顺序，可以把产品资料和现有报告发过来，或者直接联系：132 4819 8029。能力范围见服务介绍，送检要求见送检要求，其他问题见常见问题。

English version

Conclusion. Entering the Korean market generally involves two workstreams: product registration and review of the manufacturing quality system. They are separate processes with a dependency, since the outcome of system review affects progress on product registration. A common planning error is treating them as one thing, or running them strictly in sequence. The first omits work; the second stretches the timeline. Starting both in parallel and aligning at the dependency points is the sensible approach.

Preparing test data. Product registration requires technical documentation in which test data are central, typically covering performance against the technical requirements, applicable electrical and mechanical safety, biocompatibility according to contact conditions, sterilisation and packaging for sterile products, and software verification. These overlap heavily with other markets, so existing data are largely reusable; what needs confirming is whether the method standards are accepted and whether the reports are complete.

Local standards and local testing. Check whether applicable standards have locally adopted versions, whether those differ technically from the international editions, and whether particular items must be tested locally. Whether local testing is required has the greatest effect on planning: if it is, samples must be shipped, the schedule follows the local laboratory's capacity, and the overall timeline lengthens noticeably. Confirm this at project start rather than discovering it midway through documentation.

Connection with system review. System review examines how the quality management system operates, and the testing-related aspects include whether inspection procedures match actual practice, equipment calibration status, inspector qualification, completeness of inspection records, handling of nonconforming product, and evaluation and management of external laboratories. These corroborate the test data submitted for product registration: where the product file states that an inspection is performed, the system should contain the corresponding procedure and records. Mismatches generate questions. Prepare by listing the inspection items referenced in the registration documentation and confirming that each has a corresponding procedure and actual records in the system.

Scheduling. Start first with the local standard comparison and confirmation of whether local testing is required, since those determine the workload that follows. Then run in parallel the preparation of test data including any local testing, the writing of technical documentation, and the review of system documents. Align at the points where system review and product registration depend on one another. And finish with preparation and checking of local-language documentation. Where local testing is required it usually governs the schedule, because it involves shipping, local capacity and possible communication cycles.

Shipping samples. Where samples must go to a local laboratory, plan the logistics early: whether the product contains batteries, which brings dangerous goods requirements; the quantity needed; customs documentation; and disposal after testing. Products containing lithium batteries are the ones that most often stall here, so start that preparation earlier.

Language. Submissions generally require the local language. Technical annexes may face lighter requirements, but the main documentation needs translating. Pay attention to the accuracy of technical parameters during translation and ensure they agree with the test reports and the instructions for use. Parameter errors introduced in translation occur easily and are hard to spot.

Maintenance afterwards. Product changes, maintenance of system certification and periodic update obligations all need attention. On the testing side, changes require judging whether submitted data are affected, and periodic system review re-examines inspection records. Add these to a single compliance calendar managed alongside obligations for other markets.

How we handle it. For Korean work we establish two things first: how much existing reports cover, and whether any items must be performed locally. The second defines what we can do, and stating it clearly lets the client plan the whole programme. For items we can perform, we issue reports at a fairly detailed level covering conditions, measured values and equipment information, which generally satisfies several markets and reduces duplication.

Send us the product information and existing reports and we will map the scope and sequence. Phone or WeChat: +86 132 4819 8029.