What Counts as a Medical Device: Act 737 Section 2 and Product Boundaries

1. Key takeaways

Section 2 of the Medical Device Act 2012 (Act 737) defines a medical device by reference to what it is, what it is for and how it works. The object may be an instrument, an apparatus, a machine, an implant, an in vitro reagent or calibrator, software or a comparable article. It must be intended by the manufacturer to be used, alone or in combination, for human beings for specified purposes such as diagnosis, prevention, monitoring, treatment or alleviation of disease. And it must not achieve its principal intended action in or on the human body by pharmacological, immunological or metabolic means, although it may be assisted in its function by such means. Three tests therefore sit inside one sentence: the nature of the article, the intended purpose claimed for it, and the mechanism by which the principal effect is produced.

• The definition in Section 2 is functional rather than list-based: an article is a device because of its intended purpose and principal mode of action, not because it appears in a catalogue.
• The exclusion is narrow and specific: a product whose principal intended action is achieved by pharmacological, immunological or metabolic means falls outside the definition, and assistance by such means does not remove a device from it.
• Section 2(b) operates as a residual clause, allowing an article declared by the Minister to be a medical device to be treated as one even where the primary definition is not obviously engaged.
• Software is expressly within the scope of the definition, so a program whose output serves a medical purpose may itself be a device.
• Disinfection of medical devices is named in Section 2 as a device purpose, which brings disinfectant products into consideration rather than leaving them outside.
• Where classification is disputed between an establishment and a CAB, Section 3(2) provides a statutory route: the question is submitted to the MDA for a ruling.

2. Legal basis

Section 2 supplies the operative words. The purposes enumerated there are diagnostic, preventive, monitoring, therapeutic and palliative in character, together with the disinfection of medical devices, and the article must be intended by its manufacturer for one or more of them. The manufacturer’s intention is therefore a legal fact, established by the claims made for the product, the labelling, the instructions for use and the technical documentation. A product described as diagnostic in one document and as general wellness in another has not avoided the definition; it has created an evidential problem about its own intended use.

The mechanism test is the second limb. A device does not achieve its principal intended action in or on the human body by pharmacological, immunological or metabolic means. The qualification that it may be assisted in its function by such means is what allows devices with ancillary medicinal content to remain devices, while products whose therapeutic effect depends on pharmacological action remain outside the definition. The boundary is drawn at the principal action, which is why the analysis cannot be performed on the ingredient list alone; it requires the mode of action to be characterised and the claim to be matched against it.

Section 2(b) completes the structure by preserving a declaratory route. An article that is not plainly within the primary definition may still be treated as a medical device if the Minister declares it to be one. In practice this means that the absence of an obvious fit is not the end of the analysis; the question becomes whether the article has been, or could be, brought within the scope by declaration.

Section 3(2) then provides the procedural counterpart for classification disagreements. Where an establishment and a CAB reach different conclusions on classification, the dispute is referred to the MDA for decision. This is a statutory mechanism rather than an informal escalation, and it exists precisely because classification is a judgement applied to facts that the parties may characterise differently.

3. Expert insights

Boundary questions are best handled with three questions asked in a fixed order. First, what is the intended use claimed, expressed in the terms the manufacturer actually uses in its labelling, promotion and technical file. Second, what is the principal mode of action, and is it pharmacological, immunological or metabolic, or is it physical or mechanical with only ancillary support from such means. Third, does the article fall within the declaratory clause in Section 2(b) even if the first two questions do not resolve it. Asking the questions in this order prevents the most common analytical error, which is to begin with the material or the technology and then work backwards to a purpose.

Software deserves separate attention because it is named in the definition and because its classification as a device turns entirely on output. A program that produces a medical purpose output, such as an interpretation or a diagnostic conclusion, may be a device in its own right, irrespective of the hardware it runs on and irrespective of whether it is distributed as an application. Framing the product as a lifestyle tool, a tracker or a wellness aid does not alter the analysis if the output is diagnostic in character; it merely puts the claim in tension with the function.

Three misjudgements recur in practice. The first is treating dressings as a single low-risk category: a dressing that carries a medicinal component may be classified differently or may raise combination product questions, so the category label cannot substitute for the assessment. The second is treating AI-enabled health applications as outside the framework: where there is a diagnostic output, the software may be a device and may need to be handled as software as a medical device. The third is overlooking disinfectants: Section 2 names the disinfection of medical devices as a device purpose, so a disinfectant presented for that use is not automatically a general chemical product. Each of these errors has the same shape, which is the substitution of a familiar category for the statutory test.

Where the answer remains uncertain after the three questions, there is an official route. An applicant may approach the MDA for a product classification determination, which produces the Authority’s own view rather than an internal one. A self-argued position recorded in the CSDT, with the reasoning and the evidence preserved, is a reasonable interim measure, but it should be understood as a documented position rather than a determination, and it should be revisited if the claims change.

4. Practical recommendations

• Write the intended use statement once, in the terms the company will use everywhere, and treat every deviation in labelling, promotion or the technical file as a defect to be corrected rather than a variant to be tolerated.
• Characterise the principal mode of action explicitly in the technical documentation, separating the principal action from any ancillary pharmacological, immunological or metabolic assistance.
• Assess software products against their output rather than their form, and document the conclusion where the output serves a diagnostic or therapeutic purpose.
• Do not accept category labels such as dressing, disinfectant or application as substitutes for the Section 2 analysis; run each product through the tests individually.
• Where a CAB and the establishment disagree on classification, use the Section 3(2) route and refer the question to the MDA rather than adopting a compromise class for convenience.
• Keep a written record of the classification rationale, with the claims and evidence it relies on, so that the position can be defended in a review or revisited if the product changes.

5. Verification checklist

• □ Act 737 Section 2 read in full, including the mechanism exclusion and the declaratory clause in paragraph (b) (pending verification).
• □ Act 737 Section 3(2) confirmed as the route for referring a classification dispute to the MDA (pending verification).
• □ MDA Guidance Document on the Definition of Medical Device (MDA/GD-01) reviewed in its current edition (pending verification).
• □ MDA website page on the overview of medical device registration checked for the product classification application entry point (pending verification).
• □ Intended use statement, labelling and promotional material compared line by line for consistency of claim (pending verification).

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