Published on
Last updated on
India Clarifies How Medical Device Software, and AI-Enabled Tools Are Regulated

On July 21, 2026, the Central Drugs Standard Control Organization (CDSCO) published its final Guidance Document on Medical Device Software under the Medical Devices Rules, 2017 (MDR 2017), following the draft release in October 2025.
Designed to support consistent implementation of MDR 2017 while encouraging innovation, patient safety, and timely market entry, the guidance clarifies how standalone, AI-enabled, and in vitro diagnostic (IVD) software is classified and licensed in India. It establishes clear expectations across five key areas:
- Technical documentation
- Quality management
- Applicable standards
- Cybersecurity
- Post-market monitoring
This framework helps manufacturers, importers, and applicants determine whether a software product qualifies as a Medical Device Software (MDSW) in its own right or forms part of a physical device. CDSCO emphasizes that the document introduces no new legal obligations, but rather provides a practical roadmap for applying existing rules across the software lifecycle, from cybersecurity and change controls to post-launch performance monitoring.
At a Glance: Key Regulatory Requirements
- Regulatory scope: Covers software intended for medical purposes — whether standalone (SaMD), embedded (SiMD), mobile, cloud-hosted, or AI-driven — as well as IVD software.
- Risk classification: Intended use and the First Schedule of MDR 2017 determine the risk class (A to D). Where multiple classification rules apply, the higher risk class takes precedence.
- Licensing: Test license applications go through the National Single Window System (NSWS). Other licenses and registrations are handled through the Online System for Medical Devices.
- Technical Compliance: Manufacturers must address software lifecycle quality management, cybersecurity, software bills of materials (SBOMs), performance monitoring and version-traceable post-market actions.
Which Software Products Are Regulated as Medical Devices in India?
The guidance uses the term medical device software (MDSW) for software that meets the definition of a medical device under the Drugs and Cosmetics Act, 1940 and MDR 2017. This encompasses standalone software (SaMD), software embedded within hardware, and in vitro diagnostic (IVD) software, unless explicitly exempted.
Not all health-related software is regulated. General wellness, fitness, healthy-lifestyle and routine body-parameter tracking applications are excluded where they have no medical purpose. However, software used for diagnostic image analysis or real-time patient monitoring is likely to qualify as a medical device.
How CDSCO Classifies Medical Software and Determines Licensing Requirements
MDSW is classified into four risk categories, from Class A (lowest risk) to Class D (highest risk), based on its intended use and the classification rules in the First Schedule of MDR 2017. If more than one rule applies, the higher risk class takes precedence.
The guidance also clarifies which authority handles each type of license:
CLA refers to the Central Licensing Authority (CDSCO), while SLA refers to the State Licensing Authority.
Test license applications must be submitted through the National Single Window System (NSWS). Other licensing and registration applications are processed through the Online System for Medical Devices.
Technical Documentation Required for CDSCO Applications
Sections 12.1 to 12.5 and Annexure A of the guidance outline the documentation required for MDSW applications.
Key dossier components include:
- Intended-use statement and software description
- Software architecture and design documentation
- Risk management documentation
- Clinical or performance evidence, as applicable
- Product labeling
- Quality management and post-market surveillance plans
Where a listed document does not apply, applicants must provide a proper justification.
Software Quality Management: QMS and Applicable Standards
CDSCO expects manufacturers to maintain a quality management system (QMS) covering the full software lifecycle, from planning and design to deployment, maintenance and updates.
This includes documented software validation, risk management, configuration control, traceable changes and defect management. Manufacturers must also maintain cybersecurity controls throughout the product lifecycle.
MDSW must comply with standards established by the Bureau of Indian Standards (BIS) or notified by the Ministry of Health and Family Welfare. Where no applicable standards exist, manufacturers should follow recognized ISO, IEC or other relevant standards, including pharmacopoeial standards.
Patient Data Protection and Digital Health Interoperability
For software handling patient information, CDSCO highlights secure data exchange, interoperability and privacy protection. Manufacturers must also address patient consent when sharing data and maintain auditable records to support accountability.
Cybersecurity and AI: Managing Software Vulnerabilities and Algorithm Changes
The guidance places particular emphasis on cybersecurity and the governance of AI-enabled software:
- Software Bill of Materials (SBOM): Manufacturers should maintain an SBOM documenting all third-party, open-source, and commercial software components used. This allows teams to identify known vulnerabilities quickly and manage security risks.
- AI & Machine Learning Disclosures: Applicants must explain how AI/ML tools generate outputs, detailing whether the system uses rule-based logic, machine learning, neural networks, or fixed versus adaptive algorithms. The degree of software autonomy must also be documented.
- Algorithm Change Protocols (ACP): Where appropriate, an ACP can define how future algorithm updates will be evaluated and managed without triggering unnecessary regulatory resubmissions.
- Post-Launch Performance: After launch, manufacturers must actively monitor for performance degradation, algorithm drift, and unintended outcomes.
Post-Market Surveillance, Reporting and Software Recalls
Medical device software remains subject to MDR 2017 requirements for adverse-event reporting, field safety corrective actions and recalls. Manufacturers must be able to trace these actions to the specific software version involved.
A software recall may require uninstalling an application or removing it from customer networks and connected hardware. Periodic Safety Update Reports (PSURs) apply specifically to software approved following clinical investigations, subject to the conditions set out in MDR 2017.
How Medical Software Manufacturers Should Prepare for CDSCO Requirements
Manufacturers and applicants should review their existing regulatory and quality processes against the new guidance. Key priorities include:
- Review intended-use claims: Ensure intended-use statements are consistent across product documentation, regulatory submissions, labeling and marketing materials. These claims directly influence whether software qualifies as a medical device and its risk classification.
- Document the classification rationale: Prepare a rationale for each intended purpose, applying the higher-class rule where multiple classification rules are relevant.
- Confirm licensing requirements: Identify the appropriate licensing authority and application portal for each planned activity, including testing, manufacturing and importing.
- Strengthen software change controls: Define how significant software and algorithm changes will be assessed, documented and managed. Ensure performance issues, complaints and corrective actions can be traced to the affected software version.
Final Thoughts: What the New Guidance Means for Medical Software Market Access in India
Software now reaches nearly every corner of care, from imaging to remote monitoring to hospital administration, and CDSCO’s guidance signals closer oversight of software-based products. As digital health tools and AI evolve, manufacturers will need a lifecycle approach to compliance that joins design, validation, quality management and cybersecurity. Early alignment with the guidance should smooth approvals under MDR 2017.
The challenge is the detailed guideline. A gap in classification, dossier evidence or post-market planning can hold up an approval for months. Cisema can run a gap assessment against the guidance, prepare the classification rationale and manage submissions through the right CDSCO portals.
For support with medical device software registration in India, contact Cisema to discuss your requirements.
Further Information
Explore Cisema’s services for Medical Device Registration in India.
References
Connect with Cisema
With more than 20 years of experience and a team of over 100 specialists, Cisema helps global companies achieve compliance across Asia Pacific with confidence and accelerate market entry.
Stay Informed with Monthly News and Analysis
Stay informed with the latest regulatory changes, expert insights, and market opportunities across APAC, delivered straight to your inbox.


