Technical Documentation Requirements by Device Class

1. Key takeaways

Myanmar’s requirements for technical documentation are tiered by risk class, forming a comparison table that runs from simple to complex. The table tells the manufacturer, at a glance, what the Myanmar FDA expects at each of the four classes, and it is the single most useful planning artefact for the dossier. The requirements for the six core documentation areas at each class are as follows:

GRZAN note: device description and intended use, and labelling with the IFU, are required at every class; these are the only two items with no exemption whatsoever. The class-based differences appear mainly along three dimensions: the depth of risk management, the breadth of design verification, and the strength of clinical evidence. Reading the table column by column, rather than row by row, is the fastest way to see where a given class departs from the one below it.

2. Legal basis

3. Expert insights

Insight 1: Class A does not mean no requirements; it means reduced depth. Class A products must still submit the device description, labelling and the IFU, risk management may be simplified, and design verification is minimal. Companies must not equate Class A with exemption from scrutiny, because the universal items still apply in full. In practice, the most common Class A deficiency is not a missing technical study but an incomplete description or an IFU that omits one of the required elements.

Insight 2: the key dividing line for escalation is Class C. From Class B to Class C, sterilisation validation and stability data change from where applicable to required, clinical evaluation changes from case by case to required, and design verification changes from required to extensive. Class C is the watershed at which the volume of document preparation jumps, and project budgets built on Class B experience will systematically underestimate a Class C project. Planning resources around the class boundary, not around the product family, keeps the estimate honest.

Insight 3: risk management uniformly follows the ISO 14971 summary form. This is consistent with other ASEAN markets, which makes it easier for companies to reuse existing documents rather than author new ones for Myanmar alone. The summary form also keeps the reviewer’s reading burden proportionate to the risk of the device.

Insight 4: active devices and software carry an additional layer of requirements. Declarations of conformity to IEC 60601-1 and software lifecycle documents under IEC 62304 are a review focus newly added in 2026, so companies in these categories should expect the reviewer to look specifically for these files. Preparing them as standard dossier components, rather than as reactive additions, is the cheaper path.

Insight 5: the documentation areas must remain internally consistent. The device description, the labelling, the risk management file and the clinical evaluation must support one another, and any contradiction between them will be caught by the reviewer. A claim made in the description must reappear, consistently, in the risk file and in the labelling, and the intended use stated in one place must match the intended use stated everywhere else.

4. Practical recommendations

• Prepare item by item against the class comparison table, neither skipping levels nor dropping below them. Once the classification conclusion is fixed, follow the table strictly and record the mapping between each dossier item and the corresponding cell of the table for the reviewer’s convenience.
• Set the universal mandatory items as the quality baseline for all classes. Prepare the device description and the labelling and IFU to the highest standard regardless of class, since these items are never simplified and a strong version at Class A carries directly into any later upgrade.
• Start sterilisation and stability studies early for Class C and Class D. These two data sets have long generation timelines, and starting them only after classification is confirmed has cost more projects their schedule than any other single planning error.
• Prepare the IEC standard documents in parallel for active and software products. Include them in the dossier according to the latest review expectations.
• Establish a cross-consistency checking mechanism across documents. Complete a full mutual review of the document set before submission.

5. Verification checklist

• □ Technical documents have been prepared item by item against the class comparison table
• □ It has been confirmed that the device description and intended use are complete at every class
• □ It has been confirmed that the labelling and IFU meet the language requirements
• □ The depth of the risk management documents matches the class
• □ Sterilisation and stability data have been completed for Class C / D
• □ IEC standard documents have been prepared for active and software products
• □ A cross-consistency check across the full document set has been completed

Regulatory information verified as of 29 October 2026.

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