Device Master File — What CDSCO Actually Expects

Device Master File (DMF) — What CDSCO Actually Expects

By Ankur Khare — Biomedical Engineer | Regulatory Affairs Specialist | Founder, MedReg Intel


The Device Master File is the single most important document in any CDSCO application. It is also the document most frequently responsible for deficiency notices.

Not because manufacturers are careless. Because nobody clearly explains what a DMF actually needs to contain — and what it needs to avoid.

This article is that explanation.


What the DMF Is — and What It Is Not

The Device Master File is a structured compilation of all technical information about your device. It tells CDSCO's reviewer everything they need to know to assess whether your device is safe, effective, and manufactured to a consistent standard.

It is not a product brochure. It is not a collection of certificates. It is not a summary of your device's features.

A DMF is a technical argument — built from evidence — that your device does what you say it does, poses the risks you have identified, and controls those risks through validated means. Every section must support that argument. Sections that contradict each other, use marketing language, or make claims without evidence will generate deficiency notices.


The Legal Basis

Under MDR 2017, Schedule IV, Appendix II prescribes the Device Master File format and contents. Applications filed under MD-14 (import), MD-7 and MD-9 (manufacture), MD-26 and MD-27 (new devices) all require DMF submission as a core component of the technical dossier.

The DMF is reviewed against the Essential Principles of Safety and Performance listed in Schedule IV of MDR 2017. Every claim in your DMF must connect, directly or indirectly, to demonstrating compliance with these principles.


The Core Sections — What Each One Requires

Section 1: Device Description and Specification

This section describes what your device is — physically, functionally, and technically. It must include the device name, the intended use statement, the device classification with justification, a description of the components and materials, and the operating principle.

The intended use statement here is the same statement that appears on your SUGAM application form and your product labelling. It must be identical across all three locations. A word-for-word match. Any variation — even a minor rephrasing — will generate a deficiency query asking you to reconcile the inconsistency.

Write the intended use statement once, carefully, and copy it exactly into every document where it appears.

Section 2: Indications, Contraindications, and Precautions

Indications are the clinical conditions and patient populations for which the device is intended. Contraindications are the conditions under which the device should not be used. Precautions are the conditions requiring special care.

This section is where manufacturers most commonly overclaim. Indications written as marketing statements — "suitable for all patients" or "effective across a wide range of conditions" — attract immediate scrutiny. Write indications as a clinician would document a patient selection criterion. Specific, bounded, clinically defensible.

Section 3: Risk Management Summary

MDR 2017 requires risk management per ISO 14971. This section is not a risk register — it is a summary of your risk management process and its outputs.

It must demonstrate that you have identified the hazards associated with your device, estimated and evaluated the associated risks, implemented risk controls, and verified that those controls are effective. The summary must reference your full risk management file, which should be available for audit.

The most common error here is treating this section as a formality — a one-paragraph statement that risk management has been conducted. CDSCO reviewers are increasingly expecting substantive content: the key hazards identified, the risk control measures implemented, and the residual risk conclusion. A substantive summary demonstrates competence. A placeholder invites a query.

Section 4: Design and Manufacturing Information

This section describes how the device is designed and how it is manufactured. For importers, this information comes from the foreign manufacturer's technical documentation and must be provided with the manufacturer's authorization.

The manufacturing site address here must match the address on the manufacturer's ISO 13485 certificate — word for word, including abbreviations for Road, Street, and similar terms. A mismatch between these two addresses is one of the most common deficiency triggers in MD-14 applications.

Section 5: Standards Compliance

This section lists the standards your device complies with and the evidence of compliance. Under MDR 2017 Rule 7, Indian Standards (IS) take precedence over ISO or international standards where an IS standard exists for your device category.

This is where the BIS standards document becomes relevant. Before listing ISO compliance, verify whether an IS standard exists for your device type. If it does, compliance with the IS standard must be demonstrated. ISO compliance is supplementary, not substitutive.

The evidence of compliance — test reports, certificates, declarations of conformity — must be current and issued by a competent body. Expired certificates will generate a deficiency notice regardless of how recent the expiry date is.

Section 6: Clinical Evidence

The clinical evidence section demonstrates that your device performs as claimed in its intended use and patient population. The nature and volume of evidence required depends on your device class and classification pathway.

For Class B devices with a well-established Indian predicate, published literature on the predicate device, combined with a clinical evaluation report demonstrating equivalence, is generally sufficient. For Class C devices and new devices under MD-26 or MD-27, the evidence requirements are significantly more demanding — potentially including clinical investigation data specific to the Indian population.

The clinical evaluation report must be a structured document, not a literature summary. It must assess the clinical evidence systematically, address the intended use and indications specifically, and reach a conclusion on the clinical safety and performance of the device that is supported by the evidence presented.

Section 7: Labelling and Instructions for Use

Every label and IFU that will be used with your device in India must be included here. They must comply with the labelling requirements of Chapter VII of MDR 2017 — including all mandatory fields, the language requirements, and the specific formatting for license numbers, manufacturing dates, and use-by dates.

The intended use on the label must match the intended use in Section 1 of the DMF. The device name on the label must match the device name in your SUGAM application. If your product will be sold under a brand name different from the manufacturer's model designation, both names must be clearly accounted for.


The Document That Most Applicants Skip

Before submitting your DMF, prepare a one-page DMF Completeness Checklist — a simple table listing every required section, confirming that it is present, and confirming that the content within it is consistent with the SUGAM application form and with every other section of the DMF.

This exercise takes two hours. It routinely surfaces inconsistencies that would otherwise become deficiency notices — inconsistent intended use wording, mismatched addresses, expired certificates, missing sections.

Two hours of internal review can prevent three months of deficiency delays.


What a Strong DMF Looks Like

A strong DMF tells a coherent story about one device. Every section connects to every other section. The intended use in Section 1 is the basis for the indications in Section 2, which define the hazards in Section 3, which inform the design controls in Section 4, which are validated by the standards compliance in Section 5, which is supplemented by the clinical evidence in Section 6, which is reflected in the labelling in Section 7.

When a reviewer reads a strong DMF, they can follow that story from beginning to end without encountering a contradiction, a gap, or an unanswered question. That is what approval looks like before the application is filed.


Final Thought

The DMF is the application. The SUGAM portal is just where you submit it.

Manufacturers who treat DMF preparation as a documentation exercise — assembling certificates and uploading scans — consistently generate deficiency notices that extend their timelines by months. Manufacturers who treat the DMF as a technical argument — built carefully, reviewed internally, and consistent throughout — consistently move through review faster.

The quality of your DMF is the quality of your regulatory strategy. Build it accordingly.


For regulatory strategy support: ankur@medregintel.com

MedReg Intel publishes practical regulatory intelligence for Indian medical device manufacturers, importers, and startups. Visit medregintel.com

This article is for educational purposes and does not constitute formal regulatory or legal advice.

Comments

Popular posts from this blog

The ₹50 Lakh Mistake Killing Indian MedTech Startups — And How to Avoid It

A Practical Roadmap for Developing Medical Devices in India

Make in India for Medical Devices — The Reality No One Is Talking About