How to Localize Labels and Instructions for Software Medical Device Overseas Registration?

Localizing labels and instructions for software medical devices in overseas registration is not simple translation. It requires a systematic transformation based on the target country's regulations, risk classification, clinical evidence, and local agent requirements. Companies should first confirm whether the product falls within the target country's medical device regulatory scope, then determine the risk class, and subsequently assess whether existing NMPA, CE, FDA, ISO 13485, MDSAP, or other market documentation can be reused. The label is not limited to the outer packaging; software interfaces, electronic instructions, and online help documents are all within the review scope. All clinical statements, warnings, and data security descriptions in the instructions must be consistent with the risk management file and clinical evidence. Localization must be reviewed by certified translators or regulatory consultants and must incorporate local units of measurement, date formats, patient privacy clauses, and local agent information.

Key Summary

Label and instruction localization for software medical devices in overseas registration is not merely a translation task. It is a systematic conversion that must align with the target country's regulations, risk class, clinical evidence, and local agent requirements. Companies should first confirm whether the product is regulated as a medical device in the target country, then determine the risk class, and then evaluate whether existing NMPA, CE, FDA, ISO 13485, MDSAP, and other materials can be reused. Labels include not only packaging but also software interfaces, electronic instructions, and online help documents. Clinical claims, warnings, and data security statements must be consistent with risk management files and clinical evidence. Localization must use certified translation or regulatory review, and must incorporate local units, date formats, patient privacy terms, and local agent information. Common risks include machine translation errors, version mismatches, inconsistent agent information, and unreported changes.

Companies should establish a core instruction set and a localization field library, managing instructions as controlled documents synchronized with software versions, risk management, and clinical evidence. In GHWP member states and markets in Southeast Asia, the Middle East, and Latin America, core registration materials may be reused, but each country requires an independent submission; the same instruction set cannot be shared directly. Technical documentation, performance validation, risk management, clinical evaluation or evidence, labels and instructions, local agents, authorized representatives, and post-market maintenance are all critical elements of the registration pathway. Any omission can lead to deficiency letters. After market approval, companies must manage instruction changes, renewals, and agent replacements. Establishing a localization process early is key to reducing deficiencies, delays, and compliance risks.

Applicable Scenarios and Core Issues

When software medical devices are registered overseas, label and instruction localization is often treated as a translation task, leading to repeated deficiencies. This article is intended for companies planning to enter GHWP member states, Southeast Asia, the Middle East, or Latin America, and explains how to judge, prepare, and transform software medical device labels and instructions within the regulatory framework.

Software medical device labels are unique. Screen displays, electronic instructions, patient interfaces, and physician interfaces may all be considered part of the label. Instructions are not just user manuals; they include clinical precautions, data security descriptions, system environment requirements, and version update notes. Localization is not simply translating Chinese into English or a local language; it requires rebuilding the evidence chain according to the target country's regulations, language, culture, and clinical practices.

Many companies first complete domestic registration or CE certification, then consider overseas registration, and may overlook target market requirements for local agents, authorized representatives, post-market reporting, and label change control. Depending on the product classification, the verification evidence required for labels and instructions varies. Companies must first determine whether the product falls under the target country's medical device regulatory scope, then determine the risk class, and only then can they determine the specific workload of localization.

Registration Judgment Logic

Step 1: Confirm Regulatory Scope

The first step is to confirm whether the target country regulates the software as a medical device. Definitions of SaMD are similar but boundaries differ. For example, some countries treat pure function software as a medical device, while excluding health management software from regulation. Companies should consult local regulations or delegate confirmation to a local agent to avoid premature localization investment.

Step 2: Determine Risk Class

The second step is to assess the risk class. According to IMDRF or local classification rules, Class I, II, or III software receives different levels of scrutiny. The higher the risk class, the stricter the review of clinical claims, warnings, and verification data in the instructions. Companies must consider the intended use, whether the algorithm provides diagnostic or therapeutic decisions, and whether patient data is involved.

Step 3: Assess Reusability of Existing Data

The third step is to evaluate whether existing NMPA, CE, FDA, ISO 13485, MDSAP, or other market information can be reused. If CE technical documentation exists, clinical performance and risk management content can be reused, but the target country's language, units, contacts, manufacturer information, and local regulatory requirements must be localized. If only an NMPA certificate exists, much of the clinical evidence and risk management content must be regenerated and cannot be directly translated.

Step 4: Confirm Local Agent Responsibilities

The fourth step is to confirm the responsibilities of the local agent and authorized representative. In most GHWP member states, overseas manufacturers must appoint a local agent. The agent's name and address must appear on labels and instructions, and the agent is responsible for post-market surveillance, adverse event reporting, and change notifications. Companies must not treat the local agent as a simple recipient; they must confirm regulatory requirements with the agent during the localization process.

Materials and Evidence

Localizing labels and instructions requires more than just translated documents. To prove that the content is accurate, companies must retain the following evidence:

• Original version of the instructions with version number, and the corresponding software version number.
• Evidence of translation accuracy, typically requiring certified translation or review by personnel familiar with local regulations.
• Source and generation records of label files, such as product packaging labels, device screenshots, and electronic label HTML files.
• Risk control measures in the risk management file related to labels and instructions, such as contraindications, warnings, and precautions.
• Usability engineering files proving that target users can understand the instructions and complete tasks.
• Clinical evaluation or clinical evidence, particularly for any clinical claims in the instructions.

For multi-country registration, companies can establish a core instruction set and then perform localized field replacements for each country. The structure and content of the core instructions remain unchanged; only language, regulatory marks, manufacturer information, local agent information, and country-specific warnings and precautions are modified. This reduces duplicate work and errors.

Change control for instructions is also critical. Software updates are frequent, and each update may affect the instructions. Companies must establish a process for synchronizing instructions with software versions to ensure the instructions at registration match those in the post-market phase, and that changes are filed or applied for in accordance with local regulations.

Common Mistakes

In practice, companies often make the following errors, which can extend the registration timeline or create post-market compliance issues:

• Directly machine-translating Chinese instructions into English without regulatory review, leading to inaccurate medical terminology that patients or physicians cannot understand correctly.
• Treating labels only as product packaging and overlooking help files, pop-up prompts, electronic instructions, and online user manuals within the software interface, resulting in incomplete documentation during review.
• Copying instruction content from other countries without considering local clinical practice and regulatory differences. For example, normal clinical ranges, test units, warning color semantics, and personal information protection clauses differ by country.
• Manufacturer name, address, certificate number, or local agent information in the instructions not matching the registration application, causing deficiencies.
• Ignoring post-market instruction change management—after software auto-updates, instructions are not updated or reported to the regulator, creating compliance risks.
• Failing to maintain a traceable link between instruction versions and software versions, making it impossible to prove the correct version during review or inspection.

Enterprise Preparation Checklist

Before initiating overseas registration for a software medical device, companies can self-assess using the following checklist:

• Confirm the regulatory classification and registration pathway in the target country, and document it.
• Designate or engage a local agent in the target country, and obtain authorization documents and contact details.
• Establish a core instruction set and a localization field library, clearly identifying which content must be replaced for each country.
• Collect clinical evidence, risk management documents, usability test reports, and verification records relevant to the instructions.
• Define the responsible persons for instruction translation and regulatory review, including internal regulatory staff and external translation companies or local consultants.
• Establish a change control process that synchronizes instruction versions with software versions, covering post-market updates.
• Prepare a unified documentation package for multi-country registration, but create separate submission files for each country.
• Conduct an internal review before submission using the local agent's checklist, simulating the perspective of a reviewer.

AIMEILI's Perspective

Companies often underestimate the workload of localizing instructions for software medical device registration. Many think instructions are just user manuals, but regulators treat them as part of risk control and clinical evidence. If a company only considers translation in the early stages, it will likely receive deficiency letters later, delaying the certificate and increasing communication costs.

We recommend three actions early in the project: first, commission a local agent or consultancy to confirm regulatory classification and label requirements; second, establish a core instruction framework instead of starting from scratch for each country; third, inventory existing NMPA, CE, or FDA materials to identify what can be reused and what must be localized. For example, risk control measures in the risk management file can be retained, but contraindications, precautions, and warnings on labels must be rewritten according to local regulatory language and requirements.

The local agent and certificate control are critical. Many countries require the label of an overseas manufacturer to permanently display local agent information. The agent is not only responsible for receiving regulatory notices but also participates in changes and renewals. If a company does not clarify the agent's authority, or does not update the instructions and registration files when replacing the agent, it creates compliance risks.

The most effective approach for multi-country registration is to build a configurable documentation package. Core documents remain unchanged, and country-specific fields are replaced. This significantly reduces duplication and deficiency risk. Instructions should no longer be seen as a translation project, but as a controlled document in the regulatory evidence chain, consistent with software versions, risk management, and clinical evidence. This is how companies can reduce total cost and time in multi-country registrations in Southeast Asia, the Middle East, and Latin America.

Common Follow-up Questions

Does localizing software instructions only require language translation?

No. In addition to language translation, you must adjust measurement units, date formats, patient data protection statements, regulatory marks, and local agent information. Some countries require specific layouts or colors for warnings in the instructions, making the differences significant.

If we do not have CE or FDA certificates, can we directly use NMPA materials for localization?

It is not recommended to directly copy NMPA materials. NMPA materials reflect Chinese regulatory requirements and differ from the target country's classification, clinical evaluation, and risk management requirements. Companies must re-assess whether they meet the target country's regulations and, if necessary, supplement clinical evidence or usability files.

If a software update changes the instructions, must we re-register?

It depends on whether the change affects safety and effectiveness. Minor wording changes may only require notification to the local regulator, while changes affecting intended use may require a new registration application. Companies should understand the target country's change classification in advance and establish a change control process for the instructions.

Can GHWP member states share a single localised version of the instructions?

No. Different countries have different languages, regulations, and clinical habits. The core structure and content can be shared, but localization must be performed for each country to ensure compliance with local requirements.

Source: Compiled from the AIMEILI Registration Practice Database, the Medical Device International Registration Knowledge Base, and publicly available regulatory information. Specific projects should be based on the latest requirements of the target country's regulatory authority and the product's technical documentation.