Clinical Evidence Requirements in Malaysia: When Additional Clinical Data Is Mandatory

1. Key takeaways

Clinical data is not compulsory across the board, and that is precisely why it needs a decision. Principle 11 of Appendix 1 to the Third Schedule of MDR 2012 requires performance evaluation, including clinical evaluation where appropriate. The qualifier does the work: whether clinical evidence is required depends on the nature of the device, its maturity, and the adequacy of the evidence already available. The judgement is made by the CAB during technical documentation review, not by the applicant alone.

Because the test is appropriateness rather than category, the same device family can be treated differently depending on how well its performance is otherwise supported. That makes the clinical evidence question an argument to be constructed in the CSDT rather than a box to be checked, and it explains why the deficiency requests in this area read as disagreements about sufficiency rather than as requests for a missing document.

• Rule: performance evaluation, including clinical evaluation where appropriate — principle 11, Appendix 1, Third Schedule.
• Decision-maker: the CAB, during technical documentation review.
• Usually requires clinical evidence: innovative devices or new intended uses, high-risk devices without comparable marketed data, unsubstantiated performance claims, and cases where another regulator has already raised a clinical requirement.
• Reuse: CE clinical evaluation reports, FDA or PMA approvals and Japanese approvals are strong starting points.
• Reuse test: extrapolation to the Malaysian intended use and population, not the nationality of the data.
• Mature categories: non-clinical testing plus literature plus equivalence is usually accepted, with systematic argument in the CSDT.

2. Legal basis

The requirement sits in the Essential Principles rather than in a stand-alone clinical rule, which is why it is answered as part of the conformity mapping. Principle 11 of Appendix 1 to the Third Schedule of MDR 2012 requires performance evaluation including clinical evaluation where appropriate. Guidance documents MDA/GD-02 and MDA/GD-03 carry that requirement into practice, the first on the Essential Principles and the second on the CSDT, where clinical evaluation appears as an identified dossier element.

The framework does not create a separate clinical investigation obligation for every device. It creates an obligation to evaluate performance, and to demonstrate that the evaluation is adequate for the claims being registered. Where the non-clinical package and the literature fully support the claims, the clinical element can be satisfied by argument; where they do not, the gap has to be closed by data. The same principle explains why a novel claim is harder to support than a novel device: the claim is what has to be evidenced.

3. Expert insights

Insight 1: maturity, not risk class alone, decides the route. A well-established device with published clinical literature and a clear equivalence case can often proceed on a literature and comparison basis, even where the device carries a higher classification. An innovative device with no comparable marketed data usually cannot, even where its classification is moderate. Reading the requirement as a function of risk class alone leads applicants to prepare the wrong package in both directions.

Insight 2: reuse is about extrapolation, and extrapolation is an argument. Clinical evidence generated for a CE mark, an FDA clearance or PMA, or a Japanese approval is a strong starting point and does not need to be repeated. What the CAB examines is whether the data can reasonably be extrapolated to the Malaysian intended use and population. Differences in intended use, user profile, epidemiology or standard of care are the points to address, and addressing them explicitly is what converts foreign data into usable evidence.

Insight 3: the combination route needs to be argued, not assembled. For mature categories such as some implant consumables and routine IVD, a combination of non-clinical testing, literature and comparison with an equivalent device is usually accepted. Acceptance is not automatic: the CSDT has to set out why the combination is sufficient, which means stating the equivalence basis, the relevance of the literature, and the residual uncertainty that remains. Emerging AI and software products face notably stricter evidence expectations, and the same combination argument will not carry them.

Insight 4: insufficiency is a schedule risk, not a rejection. Where the clinical evidence is judged inadequate, the CAB issues a supplementary requirement for further clinical evaluation or an investigation, and the file enters a deficiency round. This is one of the main reasons Class C and D projects lose control of their timelines, because a clinical investigation cannot be compressed once it has started. An evidence sufficiency assessment before submission is therefore worth more than a faster response afterwards.

4. Practical recommendations

• Build a clinical evidence decision tree into project initiation. Innovative device or new intended use leads to a clinical evaluation report; mature device leads to equivalence plus literature; uncertain cases lead to technical pre-communication with the CAB.
• Ask the CAB early. Some CABs offer a paid pre-review, which is usually cheaper than a deficiency round.
• Document the extrapolation argument. Address intended use, user profile and population differences explicitly rather than asserting generalisability.
• State the equivalence basis. Where a comparison device is used, set out the basis on which equivalence is claimed.
• Map the evidence to the claims. Each performance claim in the intended use should point to the clinical or non-clinical evidence supporting it.
• Treat software and AI as a stricter category. Do not assume that a combination argument accepted for a mature device will transfer.

The practical discipline is to answer the sufficiency question before the reviewer does. A file that states where the evidence is strong, where it is thin and why the thin parts are nevertheless adequate reads as a considered position; a file that presents the same evidence without that discussion invites the reviewer to reach the opposite conclusion.

5. Verification checklist

• □ Principle 11 addressed explicitly in the EPSP mapping, with the appropriateness judgement recorded
• □ Clinical evidence route selected and justified: clinical evaluation report, literature with equivalence, or a combination
• □ Reused CE, FDA or Japanese evidence accompanied by an extrapolation argument for Malaysian intended use and population
• □ Equivalence basis stated where a comparison device is relied on
• □ Each performance claim traceable to supporting clinical or non-clinical evidence
• □ Software and AI products assessed against stricter evidence expectations
• □ Pre-submission sufficiency review completed, with CAB pre-communication where the position is uncertain

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including Malaysia. Our team prepares dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with the MDA, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com