How to Organize the Model/Specification Matrix for Overseas Medical Device Registration

When registering a medical device overseas, the model/specification matrix is a core document that clearly displays the differences, common characteristics, and conformity status among different models within the same registration unit. To compile the matrix, you must first determine whether the product falls under the target country's medical device regulatory scope, then identify the registration pathway based on risk classification, and evaluate the reusability of existing NMPA, CE, FDA, or MDSAP documentation. The matrix should include basic parameters, functional differences, key components, software versions, sterilization methods, packaging specifications, etc., and correspond to relevant sections of the technical file such as performance verification, risk management, and clinical evaluation. Common risks include unreasonable model partitioning leading to deficiency letters, unclear description of model differences causing reviewer queries, and failure to consider localization requirements in multi-country registrations. Companies should analyze the model logic in advance, ensure consistency between the matrix and instructions for use, labels, and quality system documents, and avoid model omissions or confusion that could affect registration progress and post-market maintenance. For Chinese medical device enterprises, a prudent approach is to first conduct product classification and documentation gap analysis, then determine whether NMPA, CE, FDA, ISO 13485, or other market documentation can be reused. Target market registration typically impacts technical documentation, authorized representatives, importer coordination, label language, quality system evidence, and subsequent change management. If you only advance based on 'which documents to submit,' you risk deficiencies or rework regarding model coverage, evidence chain consistency, label claims, and certificate control. AIMEILI recommends that companies address this issue within a GHWP member states and multi-country access strategy, using a set of reusable core technical documents to support localizations across different markets, rather than recreating documentation for each country on an ad hoc basis.

Applicable Scenarios and Core Issues

The model/specification matrix is an indispensable technical document for overseas medical device registration applications, especially in multi-country registration scenarios such as GHWP member states, Southeast Asia, the Middle East, and Latin America. When companies submit registration applications to target countries, regulatory authorities typically require a matrix to clearly illustrate the differentiated information of all models under the same registration unit, to determine whether the products belong to the same system, whether risk management is adequate, and whether clinical evaluation is comprehensive. The core issue is: how to reasonably divide models within a product family to ensure the matrix reflects differences without over-segmentation that expands the registration scope or increases deficiency risks. Additionally, the matrix must maintain data consistency with performance verification reports, risk management documents, clinical evaluation reports, and labels and instructions for use, posing challenges to technical documentation management. Common business questions include: Should products that differ only in packaging specifications, color, software version, or accessories be classified as different models? Do different markets have consistent rules for model identification? Can models already registered domestically be directly used overseas? Without proper organization, these issues can easily lead to deficiencies or withdrawal during registration.

Registration Judgment Logic

Step 1: Regulatory Scope

Confirm whether the product falls under the target country's medical device regulatory scope. For example, in some countries, diagnostic reagents may be classified as pharmaceuticals or in vitro diagnostic devices.

Step 2: Risk Classification

Determine the product's risk level based on the target country's classification rules (e.g., China NMPA Class II/III, EU CE MDR classification, FDA Class I/II/III).

Step 3: Reuse of Existing Documentation

Assess whether existing NMPA registration certificates, CE certificates, FDA 510(k) clearances, or MDSAP certifications can be reused. Note that model nomenclature and difference requirements vary by country—e.g., China requires model names to reflect structural differences, while the EU focuses more on performance parameters.

Step 4: Granularity of Model Division

Base model division on the same design, intended use, and key performance parameters, with functional or configuration differences as sub-models. The matrix should include: model name, basic parameters (dimensions, weight, materials), functional differences, list of key components, software version (if any), sterilization method, packaging specifications, and accessory list.

Step 5: Localization Requirements

Some countries require the matrix table to be in the local language and stamped by the local agent; GHWP member states generally accept English but may require a translation.

Documentation and Evidence

Core materials needed for compiling the matrix include: product technical documentation (design inputs/outputs, BOM), performance verification reports (e.g., electrical safety, EMC, biocompatibility), risk management documentation (ISO 14971), clinical evaluation or trial reports, label and IFU drafts, quality system certificates (ISO 13485, MDSAP), and the country-of-origin registration certificate (e.g., NMPA certificate). Model information in these documents must be identical to the matrix; otherwise, the product may be questioned as different and require retesting. For multi-country registration, it is recommended to create a universal matrix template and then localize according to target country requirements—for example, add columns for 'China NMPA model,' 'EU MDR model,' 'FDA model,' with notes on reasons for differences. Also, retain test report numbers and risk management report version numbers for each model to trace the evidence chain. Companies should also prepare a model difference statement clearly identifying which models are 'equivalent' (same performance, different appearance or packaging) and which are 'derived' (partial parameter changes without affecting safety or effectiveness). This statement helps reduce reviewer doubts about model coverage.

Common Mistakes

• Overly granular model division: Treating configurations differing only in color or accessories as independent models, leading to excessive registration scope and increased testing/documentation costs.
• Model omission or misclassification: Overlooking key differences such as software versions or wireless modules, resulting in a matrix that does not cover actual commercial models.
• Inconsistency with IFU/labels: Incomplete model list in the matrix compared to the IFU, or model names on labels not matching the matrix.
• Neglecting local language requirements: Providing a matrix in English only where local regulations require an official language translation (e.g., Latin America, Middle East).
• Failure to update versions: After product upgrades, the matrix is not updated, leading to disconnection between registration files and actual products, affecting post-market audits.
• Lack of unit specifications: Parameter tables missing units or not converted to target country's conventional system (e.g., imperial/metric).

Company Preparation Checklist

• Compile BOMs and product specification data sheets for all models.
• Confirm the logic for model division within the same registration unit and prepare a model difference analysis report.
• Verify that performance verification reports cover all differential parameters of all models.
• Check that the risk management report identifies hazards specific to each model (e.g., chemical risks from different materials).
• Ensure the clinical evaluation report (CER) or clinical evidence demonstrates safety and effectiveness equivalence for all models.
• Prepare draft IFU and labels, ensuring the model list matches the matrix.
• Communicate with the local agent or authorized representative to confirm matrix format and language requirements.
• Establish a version control mechanism for the matrix, updating related documents after each product change.

AIMEILI’s Perspective

The most common misjudgment by companies is conflating 'model' with 'registration unit.' Many assume that having a domestic registration certificate allows direct reuse of the model matrix overseas, overlooking differences in how countries define 'same design.' We recommend investing time early on to understand each target country's model definition rules and create a cross-market model mapping table, which significantly reduces deficiency risks later. Regarding documentation reuse, core performance verification reports (e.g., safety, EMC, biocompatibility) can usually cover multiple models, but differential items may require new risk assessments or clinical evaluations—for example, adding wireless functionality may introduce EMC and cybersecurity issues requiring separate supplements. For clinical evaluation using equivalence arguments, ensure all models fall within the same equivalence scope. Local agent and certificate control issues are also critical. Some countries (e.g., Saudi Arabia, Brazil) require the matrix to be signed by the local agent, and the certificate must be registered under the agent's name; changing agents requires resubmission of the matrix. Therefore, choose stable local partners and include clear clauses on certificate ownership and change procedures in contracts. For multi-country registration, establishing a unified matrix template with 'market-specific columns' is an effective way to reduce repetitive work—e.g., adding fields for 'China Registration Number,' 'CE Certificate Number,' 'FDA 510(k) Number' to facilitate reviewer cross-referencing. We also recommend updating the matrix every six months, as product upgrades, regulatory changes, or certificate renewals may alter the model list.

Frequently Asked Questions

Do model names need to be consistent across different countries?

Not necessarily. Some countries require model names to exactly match labels, but others allow local naming conventions. For example, China requires model names to reflect product characteristics, while the FDA allows internal company codes. Companies should include multiple columns in the matrix such as 'Generic Model,' 'China Model,' 'US Model,' along with naming rule explanations to avoid confusion.

If I discover a missing parameter in the existing model matrix during overseas registration, can I supplement it with test reports later?

Yes, but assess whether it impacts completed testing and review timelines. It is recommended to cross-check the matrix against the target country's registration guidelines (e.g., official templates from Thailand’s TFDA or Indonesia’s MOH) before submission. If gaps are found, immediately perform additional tests or issue a declaration—do not wait for the reviewer to send a deficiency notice.

If multiple models share a single risk management report, should I indicate the coverage in the matrix?

Yes. Add a column for 'Risk Management Report Number' in the matrix and note the model range covered by that report. If a specific model has unique hazards (e.g., batteries, surgical use), provide a separate supplemental analysis and link it in the matrix.