Applying the ASEAN CSDT Template in Malaysian Registration: Key Filing Points

1. Key takeaways

The CSDT is the mandatory architecture for a Malaysian device dossier. The Common Submission Dossier Template is the technical documentation format harmonised across ASEAN. In Malaysia it is prescribed in Appendix 2 of the Third Schedule to MDR 2012, and the governing guidance document is MDA/GD-03. Technical documentation for Class B, C and D registration has to be prepared according to the CSDT, which means the template is not a convenience but the structure against which the submission is read.

The submission itself is made through the MeDC@St online application, which is normally organised into eight modules: basic information, manufacturer information, reference authority information, grouping information, post-market vigilance history, verification information, the attestation, and submission. The vigilance history is a standalone module rather than a footnote to the device description, and it must disclose recalls, reportable adverse events, and bans or field corrective actions recorded in other countries.

• Format: CSDT, set out in Appendix 2 of the Third Schedule to MDR 2012, applied through guidance MDA/GD-03.
• Scope: technical documentation for Class B, C and D registration.
• Platform: the MeDC@St form, normally eight modules, with vigilance history kept separate.
• Content spine: device description and intended use, classification and grouping basis, design and manufacturing, EPSP clause-by-clause evidence, risk management, testing, clinical evaluation, labelling.
• Most common failures: claims without matching evidence, missing classification basis, undisclosed vigilance history, confused version control.
• Reuse: a CE or FDA dossier can supply the structure, but the content has to be localised to Malaysian requirements.

2. Legal basis

Two instruments do the work here. MDR 2012 supplies the legal force: Appendix 2 of the Third Schedule defines the dossier template, so a submission that departs from it is not merely untidy but non-conforming. MDA/GD-03 supplies the operational reading: it explains what each part of the template is expected to contain and how the parts relate to one another. The application form adds a third layer, since the eight MeDC@St modules determine the order in which a reviewer encounters the material. The references below were verified on 19 October 2026.

The substantive content of the CSDT is broader than a product description. It covers the device description and intended use, the classification and grouping basis, design and manufacturing information, clause-by-clause evidence of conformity with the Essential Principles of Safety and Performance, a risk management summary, biocompatibility and performance testing, software and sterilization items where applicable, a clinical evaluation summary, and labelling samples. Read as a whole, the template asks a single question in a series of parts: what the device is, what it claims, and what proves each claim.

3. Expert insights

Insight 1: the eight modules are a reading order, not a filing cabinet. Applicants often treat the MeDC@St form as administrative packaging and put the substance in an attachment. That reverses the reviewer experience. The grouping information module, for instance, is where the classification and grouping argument is first seen, so an inconsistency between the grouping entry and the technical documentation surfaces early and colours the reading of everything that follows. Filling the modules as though they were a summary of the dossier, rather than a cover sheet over it, prevents that mismatch.

Insight 2: vigilance history is a substantive test. Because the module is separate, it is easy to complete it with a nil declaration and move on. The module asks specifically about recalls, reportable adverse events, and bans or field corrective actions in other countries. A registration that omits a recall recorded elsewhere is not a documentation slip; it is a disclosure failure that a reference authority check can expose, and it undermines the credibility of the rest of the file. The discipline is to assemble the vigilance answer from regulatory databases and internal quality records together, not from memory.

Insight 3: the four recurring errors are all traceability errors. The pattern is consistent. Claims that outrun their evidence appear when marketing language is copied into the intended use statement. A missing classification basis appears when the class is stated but the rule and its reasoning are not. Under-reported vigilance history appears when the search is limited to one jurisdiction. Version confusion appears when the technical documentation version and the label version drift apart. Each is a break in the link between what is asserted and what is filed, and each is cheapest to fix at drafting stage.

Insight 4: reuse is a mapping exercise, not a copy exercise. A CE or FDA dossier can supply the structure, but the content must be localised. That means rebuilding the conformity mapping principle by principle against the Malaysian EPSP, and adjusting label language and registration information to Malaysian requirements. Companies holding CE or FDA files are well placed to do this, and are advised to run a gap analysis first (see article 16), because the gaps tend to sit exactly where the two frameworks describe the same requirement in different words.

4. Practical recommendations

• Build an evidence index at drafting stage. Every claim should point to a specific report number and page, so that a reviewer can locate the support without a round of questions.
• Write the classification and grouping basis as an argument. Name the rule applied and the reasoning, not only the resulting class.
• Assemble the vigilance module from records. Search recalls, reportable adverse events and foreign bans or field corrective actions systematically, and keep the search record.
• Freeze versions before submission. Align the technical documentation version with the label and IFU version, and record both on the covering index.
• Run a gap analysis before localisation. Map an existing CE or FDA file against the CSDT and the Malaysian EPSP to see what has to be rebuilt rather than reformatted.
• Keep the modules consistent with each other. The grouping entry, the intended use statement and the labelling sample should say the same thing in the same words.

The economics are straightforward. An evidence index costs a few days at drafting and typically cuts the number of deficiency rounds in half, because a reviewer who can locate the support does not need to ask for it. The same index keeps working after approval, when a change has to be assessed against the registered file.

5. Verification checklist

• □ Technical documentation structured to the CSDT under Appendix 2 of the Third Schedule to MDR 2012
• □ Guidance MDA/GD-03 read against each CSDT heading
• □ All eight MeDC@St modules completed, with vigilance history as a separate entry
• □ Recalls, reportable adverse events and foreign bans or field corrective actions disclosed
• □ Classification stated together with the rule and reasoning relied on
• □ Every claim traceable to a report number and page in the evidence index
• □ Technical documentation, label and IFU versions aligned and recorded

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