How to Prepare Performance Verification Documentation for EU Medical Device Registration

Direct answer: Performance verification documentation for an EU MDR submission should not be prepared as a standalone document set. It must be built as one link in a continuous MDR evidence chain. A manufacturer should first confirm the device classification, intended purpose and applicable conformity assessment route, then run a documentation gap assessment against MDR Annex I General Safety and Performance Requirements (GSPR), the technical documentation requirements in Annexes II and III, and the chosen Annex IX or XI route. Performance verification reports, including analytical performance and, where applicable, clinical performance, must be traceable to the device description and specification matrix, the risk management file, the clinical evaluation report and the PMS/PMCF plan. MDD-era data can be used as a starting point, but the overall file must be reorganised around MDR expectations and must cover every model, variant and configuration claimed in the declaration of conformity, the labels and the instructions for use.

Published: 2026-07-15 22:32  |  Updated: 2026-07-15 22:32

Key Takeaways

EU MDR technical documentation covers the device description, design and manufacturing information, GSPR conformity, risk management, performance verification, clinical evaluation, labelling and instructions for use, PMS/PMCF, and the declaration of conformity. Manufacturers cannot simply carry over legacy MDD documents; the technical file must be reorganised around the MDR evidence chain.

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. Target market registration typically affects the technical file, authorised representative arrangements, importer cooperation, label language, quality system evidence and subsequent change maintenance. If a project is driven only by the question of which documents to submit, corrective deficiency letters and rework are likely to arise in areas such as model coverage, evidence chain consistency, label claims and certificate control.

AIMEILI recommends positioning this question within a GHWP member state and multi-country access strategy, using one reusable core technical file to support localisation in different markets rather than rebuilding documentation country by country. Manufacturers should also make project-based judgments based on the latest requirements of the target country regulator, the existing technical file basis, the device risk class and the launch plan, instead of preparing documents mechanically against a checklist.

Applicable Scenarios and Core Questions

Companies searching for guidance on how to prepare performance verification documentation for EU medical device registration are usually not looking for a conceptual explanation. They want to know whether their existing documentation can support a target market submission, whether a local agent or authorised representative is required, why timelines become extended, and which issues may affect the launch plan. Behind this question there are typically several linked considerations: product classification, registration pathway, evidence chain, label localisation and post-market maintenance responsibilities.

If a company plans to enter several GHWP member states or markets in Southeast Asia, the Middle East and Latin America at the same time, answering the process for a single country is not sufficient. A more valuable approach is to first develop 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 Assessment Logic

Manufacturers should first confirm the intended purpose, mechanism of action, clinical use scenario, mode of contact with the human body, duration of use, sterility, whether the device is active, and whether it incorporates software or has IVD attributes. Only then can the risk class and submission pathway be determined. If the pathway is misjudged, all downstream activities, including translation, notarisation, authorisation, testing and supplementary documentation, will move in the wrong direction.

For a target market project, the applicant entity and the boundaries of local responsibility must also be clarified: who holds the certificate, who handles regulatory communication, who manages importation and post-market incidents, who triggers changes, and who maintains documentation for certificate renewal. If these points are left vague in a commercial contract, market control can be compromised later.

Documentation and Evidence

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

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

Common Pitfalls

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

• Submitting NMPA documentation after direct translation, without reorganising the evidence according to the target market pathway.
• Declaring too many models and specifications while test reports, clinical evidence or labels do not cover them adequately.
• Selecting a local agent purely on commercial sales criteria, without defining regulatory responsibilities, certificate control and post-market maintenance duties.
• Inconsistency between labels, instructions for use, promotional materials and registration claims, leading to deficiency letters or post-market compliance risk.
• Failure to plan multi-country documentation reuse in advance, resulting in duplicated preparation in every country and inflated cost and timelines.

Company Preparation Checklist

Before launching a project, companies should use an internal checklist to confirm the documentation basis, 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 documentation, clinical evaluation and English-language instructions for use.
• Confirm the responsibilities, fees, certificate control and exit mechanisms of the local agent or authorised representative.
• Establish a target country gap assessment table identifying what must be retested, translated, notarised or supported by supplementary 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 entering multiple countries, establishing a clear core technical file and evidence matrix first, and then converting it according to national requirements, is usually faster, more stable and better for subsequent changes and certificate renewal than preparing documents country by country on an ad hoc basis.

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

Frequently Asked Follow-up Questions

Can domestic documentation be used directly for target market registration?

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

When is the best time to start a gap assessment?

It is recommended to start immediately after the target markets and product list have been confirmed. The earlier the gap assessment is completed, the more time there is to arrange retesting, translation, label adjustments and agent selection.

Why does the choice of local agent affect registration quality?

Local agents typically participate in registration communication, change notifications, certificate renewal and post-market incident handling. Unclear allocation of rights and responsibilities can affect certificate control and the stability of the market after approval.

Project Execution Recommendations

When executing this type of registration project, companies should maintain a project tracker that records the product list, model specifications, registration pathway, document owners, translation status, testing status, local agent communication records and planned submission dates in a single table. This makes documentation gaps visible early and helps management assess 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 must in particular be kept at consistent versions.

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

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not an isolated certificate. Regulators typically 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 declared products, or if the manufacturing site, model specifications or instructions for use version differ from the test reports, the manufacturer may be asked for supplementary explanations even if a large volume of documentation has been prepared.

Before submission, companies should create an evidence consistency checklist that maps the product name, model and specification, intended purpose, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling version and quality system certificate item by item. This step appears basic, but it can significantly reduce the probability of deficiency letters, particularly for projects submitted simultaneously across several GHWP member states or covering multiple product families.

Localisation Conversion and Agent Responsibilities

Target market registration projects usually involve arrangements with a local agent, authorised representative, importer or registration holder. Manufacturers need to confirm in advance whether the local partner is only responsible 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.

Labels, instructions for use and authorisation documents also cannot be handled by simple translation. 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 to the target country, rather than writing an isolated new set of documents.

Post-Market Maintenance and Long-Term Planning

Registration approval does not mark the end of compliance work. Manufacturers must also maintain certificate validity, change records, distributor authorisations, complaint handling, adverse event reporting, recall procedures, label versions and records of regulatory updates. Many companies invest heavily in obtaining approval but neglect post-market maintenance, so that when a manufacturing site change, model extension, instructions for use update or agent replacement occurs, the certificate and commercial distribution become disconnected.

AIMEILI recommends incorporating this question into an annual international registration plan: first clarify 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 for a single country registration, 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.

Continue Reading

• Previous: What are the requirements for the risk management file in EU medical device registration?
• Next: What are the requirements for the risk management file in Philippine medical device registration?

Recommended reading: How to select a local agent for medical device registration in Brazil; How to divide authorised representative responsibilities for medical device registration in Brazil; Why registration timelines for medical device registration in Brazil are extended; Common reasons for deficiency letters in medical device registration in Brazil; How to conduct post-market surveillance for medical device registration in Brazil; When registration changes must be reported for medical device registration in Brazil.

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 organisations 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 opinions.

Compiled from AIMEILI regulatory practice materials, the medical device international registration reference library and publicly available regulatory information. Specific projects should be based on the latest requirements of the target country regulator and the manufacturer's own product documentation basis.