How to Prepare Performance Verification Documentation for Medical Device Registration in South Africa

Short answer: To prepare performance verification documentation for medical device registration in South Africa, a manufacturer should first confirm the target country, the product risk classification, the applicable regulatory pathway and the documentation already available, and then assess the technical file, quality management system, labelling and instructions for use, local authorised representative, clinical evidence and post-market maintenance requirements. AIMEILI recommends completing a documentation gap assessment before formal submission, so that unclear classification, incomplete dossiers or unresolved authorisation arrangements do not extend the project timeline. For Chinese medical device manufacturers, the most reliable approach is to complete product classification and a documentation gap assessment first, and only then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Filed: 2026-07-11 21:39  |  Last updated: 2026-07-11 21:39

Key Takeaways

Registration in a target market typically affects the technical file, authorised representative, importer cooperation, label language, quality system evidence and subsequent change maintenance at the same time. If a project is driven purely by a question of "which documents to submit", corrections or rework are likely to arise in model coverage, evidence chain consistency, label claims and certificate control.

AIMEILI recommends positioning this question within a broader GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation in different markets, rather than re-creating documentation on an ad hoc basis for each country.

Applicable Scenarios and Core Questions

Companies searching for guidance on this topic are usually not looking for a conceptual explanation. They want to determine whether their existing documentation can support a submission in the target market, whether a local agent or authorised representative is required, why timelines are being extended, and which issues could affect the commercial launch plan. Behind this question there are typically several linked topics: 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 and Latin America at the same time, answering the question for a single country is not sufficient. A more valuable approach is to first build reusable versions of the core technical file, quality system evidence, performance verification, clinical evidence and labelling, and then localise them according to each country's regulatory requirements.

Registration Decision Logic

A manufacturer should first confirm the intended purpose, mechanism of action, clinical use scenario, method and duration of body contact, sterility, whether the device is active, and whether it incorporates software or has an IVD attribute. Only then can the risk class and submission pathway be determined. If the pathway assessment is wrong, all downstream translation, notarisation, authorisation, testing and supplementary submissions will move in the wrong direction.

For a target-market project, the applicant entity and the boundaries of local responsibility must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market incidents, who triggers changes, and who maintains renewal documentation. If these points are handled vaguely in a commercial contract only, market control can be affected later.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended purpose, 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 instructions for use, authorisation documents, existing registration certificates, manufacturer declarations and post-market surveillance documentation.

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

Common Mistakes

The most frequent problem is treating registration as a simple document submission exercise without first clarifying product classification, evidence coverage and local responsibility relationships.

• Translating NMPA documentation directly and submitting it without restructuring the evidence according to the target market pathway.
• Maintaining an excessively large number of models and specifications while test reports, clinical evidence or labelling do not provide sufficient coverage.
• Selecting a local agent purely on the basis of sales cooperation, without defining regulatory responsibilities, certificate control and post-market maintenance obligations.
• Inconsistency between labels, instructions for use, promotional material and the claims made in the registration dossier, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before starting a project, companies are advised to use an internal checklist to confirm the documentation base, so that critical evidence gaps are not discovered only after submission.

• Compile the target product list, model and specification matrix, and intended purpose statements.
• Verify whether existing NMPA, CE, FDA or other market registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management file, clinical evaluation and English-language instructions for use.
• Confirm the responsibilities, fees, certificate control and exit arrangements of the local agent or authorised representative.
• Establish a target-country gap assessment table identifying what must be re-tested, translated, notarised or supported by additional declarations.

AIMEILI Perspective

AIMEILI advises manufacturers not to view target-market registration as a one-off document submission, but to 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 generally faster, more stable and more conducive to subsequent changes and certificate renewals than filling documentation gaps country by country.

From a project management perspective, three items should be controlled early: first, product classification and pathway determination; second, the consistency of the documentation evidence chain; and third, the regulatory responsibility boundaries of local partners. If these three items are unclear, a project may still face repeated issues during deficiency responses, agent communication and post-market maintenance, regardless of how many documents appear to have been prepared.

Frequently Asked Follow-up Questions

Can NMPA documentation be used directly for target-market registration?

NMPA documentation can serve as a basis, but it usually cannot be submitted as is. Manufacturers 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 should be started immediately after the target market and product list have been confirmed. The earlier the gap assessment is completed, the easier it is to arrange supplementary testing, translation, label adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

Local agents are typically involved in registration communication, changes, certificate renewals and post-market incident handling. Unclear rights and responsibilities can affect certificate control and the stability of the market after launch.

Implementation Recommendations

When executing this type of registration project, companies should maintain a project tracker that records the product list, model and specification matrix, registration pathway, documentation owners, translation status, testing status, local agent communication records and expected submission dates in a single table. This makes documentation gaps visible in time and helps management judge whether the project will affect the launch plan.

Companies that already hold registrations in several countries should also build an evidence reuse matrix, defining which documents can serve as core evidence and which must be reissued or supplemented according to national requirements. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must remain version-consistent.

• Confirm the target market and 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.
• Assign post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a regulatory review perspective, quality system documentation is not an isolated certificate. Regulators generally examine whether the manufacturer name, manufacturing site, 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 device being registered, or if the manufacturing site, model specifications, instructions for use version and test reports are inconsistent, additional explanations may be required even when a large volume of documentation has been prepared.

Companies should establish an evidence consistency checklist before submission, mapping the product name, model and specification matrix, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and instructions for use version, and quality system certificate item by item. This step may appear basic, but it significantly reduces the likelihood of deficiency letters, particularly for projects covering several GHWP member states or multiple product families submitted at the same time.

Localisation and Authorised Representative Responsibilities

Target-market registration projects usually 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 also for regulatory communication, certificate maintenance, post-market incident reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labelling, instructions for use 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 details and after-sales contact information. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation is converting reusable evidence into a submission structure acceptable in the target country, rather than writing a separate, isolated set of documents.

Post-Market Maintenance and Long-Term Planning

Obtaining registration does not mean compliance work is finished. Companies must also maintain certificate validity, change records, distributor authorisations, complaint handling, adverse event reporting, recall procedures, label versions and regulatory update records. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance; when a manufacturing site change, model extension, instructions for use update or agent replacement occurs, the certificate and commercial sales can quickly become disconnected.

AIMEILI recommends managing this topic within an annual international registration plan: first define target market priorities, then build a reusable documentation package and a country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value of this approach is not only improved efficiency in a single country, but also the development of a repeatable overseas compliance capability that reduces the cost of rebuilding documentation from scratch each time a new market is entered.

Content Review and Scope of Application

Content prepared by: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team. Sourcing principle: official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials are prioritised; 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 regulatory authority, testing conclusions or legal advice.

Related Topics

• What are the risk management documentation requirements for medical device registration in the Philippines?
• How should performance verification documentation be prepared for medical device registration in the Philippines?
• What should be done when quality system evidence is inconsistent for medical device registration in the Philippines?
• How should registration documentation be prepared for medical device registration in Singapore?
• How is product classification determined for medical device registration in Singapore?
• How should the technical file be organised for medical device registration in Singapore?