How to Group Multiple Models for Overseas Registration of Patient Monitoring Devices?

Key Summary

The direct decision basis for submitting multiple models of monitoring equipment in overseas registration is whether the target country has a concept of a registration unit or family. Companies must first confirm whether the product falls within the medical device regulatory scope of that country, then assess the risk class and registration pathway. In most GHWP member states, a submission approach based on a basic model plus difference analysis is accepted, but requirements vary. When preparing documentation, core technical files such as performance verification, risk management, clinical evaluation, or clinical evidence can be reused; however, labeling, instructions for use, language, local agent, and post-market maintenance requirements must be localized. Common risks include: including models with significant hardware differences in the same registration unit, leading to deficiencies; ignoring the local agent's control over the certificate; using domestic clinical data without an applicability assessment; and failing to notify post-market changes. Companies should first use a difference matrix to determine grouping, then create a submission checklist according to target country requirements, and establish a change notification mechanism with the local agent to avoid repeated submissions and certificate risks.

For Chinese medical device companies, a more prudent approach is to first conduct product classification and documentation gap assessment, then determine whether NMPA, CE, FDA, ISO 13485, or other market documentation can be reused. Target market registration usually affects technical files, authorized representative, importer coordination, label language, quality system certificates, and subsequent change maintenance. If the project is driven only by 'which documents to submit,' it is easy to encounter deficiencies or rework in model coverage, evidence chain consistency, label claims, and certificate control. AIMEILI recommends that companies plan this issue within a GHWP member state and multi-country market access strategy, using one set of reusable core technical files to support localization in different markets, rather than re-doing documents from scratch for each country.

This content is compiled based on AIMEILI's registration practice database, medical device international registration knowledge base, and public regulatory information; specific projects should follow the latest requirements of the target country's regulatory authority and the product's documentation basis.

Applicable Scenarios and Core Issues

During overseas registration of monitoring equipment, companies often encounter multiple models within the same product series, such as the same main unit with different screen sizes, different measurement modules, or software version variants. The most direct question is: should these models be submitted as one application or split into multiple registration certificates? This decision directly affects testing costs, review timelines, and the scope of post-market changes.

The term 'multiple models' here requires distinguishing between hardware differences, software differences, or configuration differences. Regulators in different countries have non-uniform definitions of 'model': some use trade names, some use registration units, and some use technical specifications. Companies should not directly apply the domestic NMPA classification approach but must confirm the country's acceptance of 'model' and 'registration package.'

The core issue is not 'can we submit together' but 'what evidence proves that these models are the same risk class, share the same basic design, and differences do not affect safety and effectiveness.' If this cannot be proven, the models should be split.

Registration Decision Logic

Step 1: Confirm Regulatory Scope

Confirm whether the monitoring device falls within the target country's medical device regulatory scope. Most countries and regions classify equipment with physiological parameter measurement, display, and alarm functions as active medical devices, but the specific category depends on intended use and measured parameters. For example, heart rate monitoring in sports wearables may not be regulated as a medical device in some countries, while clinical monitors are usually within scope.

Step 2: Determine Risk Class and Pathway

In GHWP member states, monitoring devices are mostly classified as Class A or Class B (corresponding to different levels), but this must be confirmed according to the target country's specific classification rules. The risk class determines whether the registration pathway is certification, declaration of conformity, or pre-market approval.

Step 3: Identify the Applicant

Most countries require a local registrant or local agent to be the applicant and certificate holder. The identity of the applicant directly affects the submission documents, fees, and post-market change processes.

Step 4: Assess Reusability of Existing Documents

Companies should review existing NMPA registration certificates, CE technical files, FDA 510(k), ISO 13485 certificates, MDSAP certificates, or other national registration documentation to identify matches with target country requirements. For GHWP member states, many basic test items can be reused, but clinical evaluation, instruction language, and metrology standards may need localization.

Step 5: Confirm Full Requirements

Confirm technical files, performance verification, risk management, clinical evaluation, labeling, instructions for use, local agent, authorized representative, and post-market surveillance requirements. Monitoring equipment typically involves electrical safety, electromagnetic compatibility, biocompatibility, data interfaces, alarm systems, and clinical accuracy verification. These documents should be organized using a difference matrix as the main thread, covering all models item by item.

For Southeast Asia, the Middle East, Latin America, and other markets, it is recommended to select a base model as the main model and establish a 'family' concept through a complete difference analysis. Do not create a full set of documents for each model separately; instead, use a master file plus appendix approach to reduce the risk of repeated assembly and deficiencies.

Documentation and Evidence

The first critical document for grouped submission is a model coverage logic explanation, usually a difference matrix or family statement. This document must list each model's hardware configuration, software version, measurement modules, interfaces, and intended use differences, and explain whether these differences affect safety and effectiveness.

The second document is the core technical file, preferably structured as a master document plus difference appendixes. The master document records the basic model's design, production, risk management, and performance data, while the appendixes describe the specific changes and verification results for additional models. This reduces duplicate submissions and helps reviewers quickly locate key evidence.

The third document is a performance verification summary table. Monitoring equipment must provide accuracy verification for different parameters, alarm function verification, environmental testing, and software verification data. If multiple models use the same measurement module, the same verification report can be referenced, but a traceable model coverage table must be maintained.

The fourth document is clinical evidence or clinical evaluation. Different countries have different acceptance levels of Chinese clinical data. Companies need to assess whether local clinical evaluation is required or if literature and standard conformity suffice. For example, some GHWP member states accept clinical accuracy data based on standard testing but require an applicability assessment.

The fifth document is labeling and instructions for use. Each model's label should include the model name, manufacturer, intended use, warning information, and manufacturing date. If multiple models share a label system, verify local language and regulatory requirements. Instructions for use must cover all model differences and cannot only describe the basic model.

Finally, local agent and post-market maintenance documents are required, including the authorization letter, quality system statement, adverse event reporting plan, and update agreement. There should be a clear division of responsibilities between the certificate holder and the agent, especially for change notifications and certificate renewals.

Common Mistakes

• Forcibly merging models with significant hardware differences into one registration unit, leading to requests for complete testing and extended timelines.
• Focusing only on models covered by the registration certificate while ignoring post-market change obligations, such as not notifying software upgrades under local requirements.
• Treating software version or configuration differences as independent models and submitting them one by one, causing unnecessary duplicate testing.
• Failing to confirm the classification of main units and accessories. For example, a monitor screen or data module sold separately may be regulated as a standalone medical device.
• Ignoring the local classification boundary and applying for a lower risk pathway, leading to rejection by the regulatory authority and delays.
• Not establishing a control mechanism for critical components, causing the registration certificate to no longer cover certain models after changes.
• Relying only on domestic or CE reports without confirming acceptance by the target country or conducting language and standard localization.
• Selecting an inappropriate local authorized representative without agreeing on certificate control, making it difficult to respond quickly to changes.

Company Preparation Checklist

• Establish a complete model list, registering each model's hardware version, software version, measured parameters, and intended use.
• Create a model difference matrix, clearly identifying the main model and variant models, and marking differences.
• Collect existing NMPA, CE, FDA, ISO 13485, MDSAP, or other market registration documents and test reports.
• Confirm the target country's risk class and registration pathway by checking official classification guidance or confirming with the local agent.
• Select and appoint the target country's local agent or authorized representative and sign an authorization agreement.
• Prepare the technical file master document and difference appendixes according to the target country's requirements.
• Verify label and instruction language, ensuring coverage of operational differences for all models.
• Develop a post-market surveillance plan, including adverse event reporting, change notifications, and certificate renewal milestones.
• Establish a change notification process with the local agent to ensure any design or process change is promptly assessed for registration impact.
• Conduct an internal mock deficiency review before submission, checking model coverage logic and evidence closure.

AIMEILI Regulatory Interpretation and Business Impact

The most common misjudgment by companies is understanding 'family registration.' Many companies think that listing as many models as possible will reduce certificate fees, but in fact, regulators care whether the evidence covers the models, not just whether the registration certificate looks complete. Instead of expanding the submission scope to include more models, it is better to first conduct a difference analysis and confirm which models can be supported by the same technical file for safety and effectiveness.

At the beginning of a project, three tasks are most important: first, establish a mapping table between models and the target country's access requirements; second, confirm whether the target country accepts the 'main model plus difference' submission mode; third, sit down with the proposed local agent and clarify the responsibility boundaries. If these three tasks are done solidly, subsequent document preparation and deficiency response will be much smoother.

Regarding document reusability, electrical safety, electromagnetic compatibility, biocompatibility, and risk management system documents are often reusable across countries, but local voltage, frequency, standards, and language requirements must be checked. Clinical accuracy verification data requires an applicability assessment based on the regulatory environment; one cannot assume all data is directly usable. Instructions for use and labels must be localized. This is not a translation issue but a regulatory compliance issue.

Local agent and certificate control are extremely critical. In many countries, the registration certificate holder is the local agent. If the actual control of the certificate is not in the company's hands, subsequent changes, renewals, or even withdrawal may be compromised. It is recommended to clearly define in the agent agreement the rights to use the certificate, data access, and change confirmation.

The most effective approach for multi-country registration is not to prepare a complete set of documents for each country separately, but to establish a 'Basic Technical File' plus 'Country-Specific Difference Annex' structure. This reduces duplicate preparation and lowers the risk of deficiencies because reviewers see a consistent evidence logic. Companies should organize files according to this structure before the registration project begins, rather than patching documents together at the last minute.

Frequently Asked Follow-up Questions

Q: Model A is already registered in Country A. Can I add Model B under the same registration certificate?

This depends on the change pathway allowed by Country A. If Model B belongs to the same registration unit and the differences do not affect safety and effectiveness, most countries allow adding a model through 'change registration,' but a difference analysis and technical documents must be submitted. If the differences are significant, a new application may be needed. Confirm Country A's rules on registration certificate changes; do not assume all countries accept a similar NMPA filing change.

Q: Does grouped submission mean all models require full testing?

Not necessarily. If using the main model plus difference analysis model, you can rely on the basic model's test reports, but you need to prove that differences do not affect key performance. For example, if only the screen size changes without affecting the measurement module, repeat accuracy verification may not be required, but usability and alarm loudness tests may be needed. The key is to provide evidence of difference acceptability.

Q: The same series of models can have different registration unit divisions in different countries?

Yes, and this is common. The definition of a 'registration unit' is not uniform across countries. Companies should follow the target country's regulatory logic. When planning multi-country registration, do not try to use one global model grouping to satisfy all countries; instead, design a flexible base file plus national-specific pages.

Q: If one model is not considered a medical device in one country, is registration still required?

It should not be included in that country's medical device registration. However, other regulatory requirements may apply, such as wireless certification for radio modules. Companies should confirm regulatory status country by country and not assume that a lack of regulation in one country means no regulation elsewhere.

Continue Reading

Previous article: None available.

Next article: How to Use ISO 13485 Certification for Overseas Registration of Rehabilitation Equipment?

Content Review and Applicability

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team. Source principle: Priority is given to official regulatory authorities, international organizations, standards organizations, and public regulatory materials; industry media and project experience are only for supplementary judgment.

Applicability: This article is intended for early-stage understanding, documentation preparation, and project planning. It does not replace the formal requirements of the target country's regulatory authority, testing conclusions, or legal advice.