Common Reasons for Deficiency Requests in Indonesian Medical Device Registration: FAQ

Direct answer: In Indonesian medical device registration, deficiency (supplementary data) requests most commonly arise from four clusters of causes: (1) incorrect product classification or selection of the wrong regulatory pathway; (2) inconsistency across the evidence chain, where the model/specification matrix, test reports, clinical evidence, risk management file, labelling and the application form do not support one another; (3) incomplete or unsuitable local representation and authorisation arrangements, including unclear certificate control; and (4) insufficient planning for post-market maintenance, variations and licence renewal. Before submitting, companies should confirm the target country, the product risk class, the applicable regulatory pathway and the current documentation base, then assess the technical file, quality system, labelling and IFU, local representative, clinical evidence and post-market obligations. AIMEILI recommends completing a documentation gap assessment before formal submission so that unclear classification, documentation or authorisation arrangements do not extend the project timeline.

Published: 10 July 2026, 15:20 | Updated: 10 July 2026, 15:20

This FAQ addresses the priority questions companies face in international medical device registration, documentation preparation, compliance pathways and post-market maintenance.

Article Structure

• Key Takeaways
• Applicable Scenarios and Core Questions
• Registration Decision Logic
• Documentation and Evidence
• Common Pitfalls
• Company Preparation Checklist
• The AIMEILI View
• Frequently Asked Follow-up Questions
• Further Reading
• Content Review and Scope of Application

Key Takeaways

On the question of the common reasons for deficiency requests in Indonesian medical device registration, companies should first confirm the target country, product risk class, applicable regulatory pathway and existing documentation base, and then assess technical file requirements, quality system evidence, labelling and IFU, local representation, clinical evidence and post-market maintenance obligations. AIMEILI recommends completing a documentation gap assessment before formal submission, so that unclear classification, documentation or authorisation arrangements do not prolong the project timeline.

For Chinese medical device manufacturers, the more reliable approach is to complete product classification and a documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Indonesian registration typically affects the technical file, authorised representative, importer cooperation, label language, quality system evidence and subsequent variation maintenance at the same time. If the project is driven only by a question of which documents to submit, deficiency requests or rework are more likely to arise in respect of model coverage, evidence chain consistency, label claims and certificate control. AIMEILI recommends managing this question within a GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation in different markets, rather than rebuilding documentation on an ad hoc basis for each country.

This material has been compiled from the AIMEILI regulatory practice question bank, 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 regulator and the product documentation base.

Applicable Scenarios and Core Questions

Companies searching for the common reasons for deficiency requests in Indonesian medical device registration are usually not looking for a conceptual explanation. What they need to determine is whether their existing documentation can support an Indonesian submission, whether a local agent or authorised representative is required, why the timeline is being extended, and which issues could affect the launch plan. Behind this question there are usually several connected elements: product classification, registration pathway, evidence chain, label localisation and post-market maintenance responsibilities.

If a company intends to enter several GHWP member states or markets in Southeast Asia, the Middle East or Latin America at the same time, answering the process question for a single country is not enough. A more valuable approach is to first develop reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling/IFU, and then localise them in line with each country's regulatory requirements.

Registration Decision Logic

Companies should first confirm the intended use, mechanism of action, use environment, method and duration of body contact, and whether the device is sterile, active, or incorporates software or IVD attributes, and then determine the risk class and submission pathway. Once the pathway assessment is wrong, all subsequent translation, notarisation, authorisation, testing and supplementary documentation will be directed incorrectly.

For an Indonesian project, it is also necessary to confirm the applicant entity and the boundaries of local responsibility: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market events, who triggers variations, and who maintains the documentation for renewal. If these points are left vague in a commercial contract, market control can easily be affected later.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended use, risk classification rationale, ISO 13485 or other applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labelling and IFU, authorisation documents, existing registration certificates, manufacturer declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. IFU claims, the models covered by test reports, the scope of clinical evidence, risk management conclusions, label warnings and the information on the registration application form must all support one another. Regulators assess whether the device is safe, effective and traceable for its intended use, not how many documents have been uploaded.

Common Pitfalls

The most frequent problem is that companies treat registration as a simple document submission exercise without first clarifying product classification, evidence coverage and local responsibility relationships. Specific examples include:

• Submitting translated NMPA documentation directly, without reorganising the evidence according to the Indonesian pathway.
• An excessive number of models and specifications, with insufficient coverage in test reports, clinical evidence or labelling.
• Selecting a local agent purely on the basis of sales cooperation, without defining regulatory responsibility, certificate control or post-market maintenance obligations.
• Inconsistency between labels, IFU, promotional material and registration documentation claims, leading to deficiency requests or post-market compliance risk.
• Failure to plan multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before initiating a project, companies should use an internal checklist to confirm the documentation base, so that critical evidence gaps are not discovered only after submission. AIMEILI suggests the following steps:

• Compile the target product list, model and specification matrix, and intended use statements.
• Verify whether existing NMPA, CE, FDA or other market registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management documentation, clinical evaluation and English-language IFU.
• Confirm the responsibilities, fees, certificate control and exit mechanisms of the local agent or authorised representative.
• Establish a target-country gap assessment table setting out what requires additional testing, translation, notarisation or supplementary declarations.

The AIMEILI View

AIMEILI recommends that companies do not treat Indonesian registration as a one-off document submission, but manage it as an overseas market access programme. For companies preparing to enter multiple countries, establishing a clear core technical file and evidence matrix first and then converting it to national requirements is usually faster and more stable than filling documentation gaps on a country-by-country basis, and it also supports later variations and renewals.

From a project management perspective, three things should be controlled in advance: first, product classification and pathway determination; second, the consistency of the documentation and evidence chain; third, the regulatory responsibility boundaries of the local partner. If these three items are unclear, the project may still encounter repeated issues in deficiency responses, agent communication and post-market maintenance, even if the documentation appears substantial.

Frequently Asked Follow-up Questions

Can Chinese domestic documentation be used directly for Indonesian registration?

Domestic documentation can serve as the basis, but it usually cannot be submitted as it stands. Companies need to adjust the documentation structure, language, labelling, authorisation documents and evidence chain in line with local regulatory requirements.

When is the best time to start a gap assessment?

It is advisable to start immediately after the target markets and product list have been confirmed. The earlier the gap assessment is completed, the easier it is to arrange additional testing, translation, label adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

The local agent usually participates in regulatory communication, variations, licence renewal and post-market event handling. If responsibilities are unclear, certificate control and subsequent market stability can be affected.

Project Execution Recommendations

When executing this type of registration project, companies should set up a project register that manages the product list, models and specifications, registration pathway, document owners, translation status, testing status, records of communication with the local agent and planned submission dates in a single table. This allows documentation gaps to be identified promptly and enables management to judge whether the project will affect the launch plan.

Companies that already hold registrations in several countries should also establish an evidence reuse matrix, defining which documents can serve as core evidence and which must be reissued or supplemented in line with national requirements. Labelling and IFU, clinical evaluation, risk management, performance verification and quality system certificates must in particular remain version-consistent. The recommended sequence is:

• Confirm target markets and the product list.
• Complete risk classification and pathway determination.
• Establish the documentation gap assessment table.
• Define the local agent and certificate control arrangements.
• Track translation, notarisation, testing and deficiency response status.
• Arrange post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a review perspective, quality system documentation is not an isolated certificate. Regulators normally examine whether the manufacturer name, manufacturing address, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope of the ISO 13485 certificate does not match the products being submitted, or if the manufacturing address, models and specifications or IFU version do not correspond to the test reports, a company may be asked for supplementary explanations even if it has prepared a large volume of documents.

Companies should establish an evidence consistency checklist before submission, mapping the product name, models and specifications, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and IFU version, and quality system certificate item by item. This appears basic, but it clearly reduces the likelihood of deficiency requests, particularly for projects submitted simultaneously across several GHWP member states or for multiple product families.

Localisation Conversion and Representative Responsibilities

Indonesian registration projects typically involve arrangements with a local agent, authorised representative, importer or registration holder. Companies need to confirm in advance whether the local partner is responsible only for submitting documents, or whether it also handles regulatory communication, certificate maintenance, post-market event reporting, variation applications and renewal reminders. Different boundaries of responsibility directly affect certificate control and subsequent market stability.

Labels, IFU and authorisation documents also cannot simply be translated. Companies should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorised representative information and after-sales contact details. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation conversion is to transform reusable evidence into a submission structure acceptable in the target country, rather than writing a separate set of documentation from scratch.

Post-Market Maintenance and Long-Term Planning

Registration is not the end of compliance work. Companies must also maintain certificate validity, variation records, distributor authorisations, complaint handling, adverse event reporting, recall procedures, label versions and records of regulatory updates. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance, so that when a manufacturing address change, model extension, IFU update or agent replacement occurs, the certificate and market sales can become disconnected.

AIMEILI recommends managing this question within an annual international registration plan: first define the priority of target markets, then build a reusable documentation package and a national gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value of this approach is not only greater efficiency in an individual country; more importantly, it enables the company to build a replicable overseas compliance capability and to reduce the cost of rebuilding documentation from zero each time it enters a new market.

Further Reading

• Why do registration timelines for Indonesian medical devices become extended?
• How is post-market surveillance conducted for Indonesian medical device registration?
• How should documentation for Malaysian medical device registration be prepared?
• How is product classification determined for Malaysian medical device registration?
• How should the technical file for Malaysian medical device registration be structured?
• How should labelling and IFU be localised for Malaysian medical device registration?
• How should clinical evaluation documentation be prepared for Malaysian medical device registration?
• Can test reports be reused for Malaysian medical device registration?

Content Review and Scope of Application

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team.

Source principles: priority is given to official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials; industry media and project experience are used only as supporting references.

Scope of application: this article is intended for preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target country regulator, testing conclusions or legal advice.