Sri Lanka Medical Device Definition: Software and Ayurveda Exclusions

1. Key takeaways

The statutory definition of a “medical device” in Sri Lanka contains five key elements: first, the object covered is an instrument, apparatus, appliance, software, material or other article, whether used alone or in combination, and including software necessary for its proper application; second, the intended purpose is that set by the manufacturer; third, the place of use is in or on the human body; fourth, five categories of intended use are enumerated; and fifth, there is a mechanism exclusion — a device does not achieve its principal intended action through pharmacological, immunological or metabolic means, although it may be assisted by such means. The definition also expressly excludes Ayurveda devices and homeopathy devices. Together these elements form the entry gate for every classification decision, and a product must be assessed against all of them before any risk class or registration route is discussed.

• The definition covers instruments, apparatus, appliances, software, materials and other articles, alone or in combination.
• Software is mentioned twice: as an object in its own right and as software needed for proper application.
• The intended purpose is the purpose set by the manufacturer, for use in or on the human body.
• Five intended-use categories are listed, from diagnosis and treatment to conception control.
• Ayurveda and homeopathy devices are expressly excluded from the device definition.

2. Legal basis

The table below sets out each element of the statutory device definition and its source. All rows are drawn from the definition clause of Act No. 5 of 2015 as cited on the NMRA website, and each element should be verified against the product file during classification.

3. Expert insights

Insight 1: software is written into the definition twice. The definition both lists “software” among the objects that can be devices and adds a separate sentence stating that the definition includes software necessary for the proper application of the device. This repetition is not a drafting error; it deliberately brings both standalone software (software as a medical device) and driver or application-assist software within the scope of regulation. For a manufacturer, the practical effect is that a software product cannot be assumed to fall outside the framework simply because it is not a physical article, and a hardware product cannot shed its accompanying software from the regulatory scope. Both categories must be documented, classified and, where required, registered.

Insight 2: the exclusion clause is a distinctive feature of the Sri Lankan framework. The definition expressly excludes Ayurveda devices and homeopathy devices, which reflects the arrangement in Sri Lanka whereby the traditional medicine systems and modern device regulation run in parallel. Products intended for use within those traditional systems follow a different regulatory track from the device track described here. When positioning a product for this market, a company must first determine which track its product falls on, because preparing a device dossier for a product that belongs to the traditional medicine track wastes effort and invites a rejection or a re-routing of the application at review.

Insight 3: the mechanism exclusion uses a “principal action” standard. The statutory wording is that the article “does not achieve its intended action … by pharmacological, immunological or metabolic means but which may be assisted in its function by such means”. This means that drug-device combination products may still fall within the device definition: the decisive question is which means produces the principal intended action, not whether any pharmacological, immunological or metabolic effect is present at all. A device that delivers or is used together with a medicinal substance can therefore remain a device if its principal action is physical or mechanical, and the assessment should be documented around the principal-action standard rather than around the mere presence of an ancillary effect.

4. Practical recommendations

• At the classification stage, run a definition gate test before any other work: check the scope of objects covered, the manufacturer-set purpose, the place of use, the five intended-use categories and the mechanism exclusion, item by item, against the product file.
• Proceed to risk classification only when all five elements are satisfied; a product that fails the gate needs a different track, not a different device class.
• For products that contain software, confirm separately whether the software is standalone software or device-accompanying software, because the technical documentation expectations differ between the two, and record that determination in the project file.
• Where the mechanism exclusion is close to the boundary, prepare a written rationale based on the principal-action standard so that the classification can be defended during review.
• Confirm early that the product is not an Ayurveda or homeopathy device, since that check determines whether the device track applies at all.

5. Verification checklist

• □ It has been checked whether the product falls within the statutory scope of objects covered by the device definition.
• □ The intended purpose set by the manufacturer has been confirmed.
• □ It has been confirmed that the product is not an Ayurveda or homeopathy device.
• □ It has been judged whether the principal intended action is achieved by non-pharmacological, non-immunological and non-metabolic means.
• □ For software-containing products, standalone software and accompanying software have been distinguished.

Regulatory information verified as of 28 October 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across South Asia, including Sri Lanka. Our team prepares dossiers to NMRA expectations, manages submissions and deficiency responses, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com