Getting a medical device license from CDSCO is a milestone. It is not the end of regulatory responsibility.
Under the Medical Device Rules 2017, manufacturers and importers must monitor products after they reach the market — collecting complaint data, investigating adverse events, and reporting serious incidents to CDSCO. This is post-market surveillance (PMS), and it connects directly to your QMS: CAPA, complaint handling, vigilance reporting, and management review.
Many manufacturers treat PMS as a regulatory checkbox. Then a serious adverse event occurs and they discover their complaint log is incomplete, investigations are undocumented, and reporting timelines were missed.
What CDSCO expects after market launch
Post-market obligations include:
- Monitoring product performance in real-world use
- Collecting and investigating complaints from hospitals, distributors, and patients
- Reporting adverse events — particularly serious adverse events (SAEs)
- Maintaining vigilance records with full investigation documentation
- Periodic safety update reporting for certain device classes (as notified)
- Field safety corrective actions (FSCA) when product must be recalled or corrected in the field
Exact reporting timelines and formats are specified in CDSCO guidance and the Materiovigilance Programme of India (MvPI). Serious events require prompt reporting — delays are regulatory violations, not administrative oversights.
Building a complaint handling system
Every complaint — however minor it seems — should be logged:
- Complaint date and source (hospital, distributor, patient, internal)
- Device name, model, batch or serial number
- Description of the problem
- Was patient or user harmed?
- Immediate containment actions
- Investigation assignment and timeline
- Root cause and CAPA linkage
- Response to complainant
- Regulatory reporting decision and date
"Minor complaint, handled over phone, not logged" is a finding. If that same issue recurs across multiple customers, you have no data to detect the trend.
When to escalate to vigilance reporting
Not every complaint is reportable. Your vigilance procedure should define criteria — typically aligned with CDSCO and GHTF/IMDRF guidance:
- Death or serious injury potentially related to the device
- Device malfunction that would likely cause death or serious injury if it recurred
- Unanticipated adverse reactions
- Labeling or IFU inadequacies leading to user error with harm
When in doubt, document the decision. "Evaluated on [date], determined not reportable because [reason], reviewed by [QA head]" is defensible. No documentation is not.
Linking PMS to CAPA and design
Post-market data feeds back into product improvement:
- Complaint trends → CAPA → process or design change
- Field failures → design review → specification update
- User error patterns → IFU revision → training for distributors
ISO 13485 clause 8.2.1 (feedback) and 8.2.2 (complaint handling) require this loop. Auditors trace a complaint through investigation to CAPA closure and verify effectiveness.
PMS data in management review
Management review must include post-market surveillance data — complaint rates, vigilance reports filed, open investigations, FSCA status. This is ISO 13485 clause 5.6.1. If your management review minutes do not mention PMS, the system is disconnected from leadership oversight.
Useful metrics:
- Complaints per 1000 units sold (by product)
- Average investigation closure time
- Reportable vs non-reportable complaint ratio
- Repeat complaints on same root cause
- Open vigilance reports
Common PMS failures in Indian manufacturers
No centralized complaint log. Complaints handled by sales, never reaching QA.
Batch/serial number not captured. Cannot trace complaint to production record.
Investigations without root cause. "Replaced unit" is not an investigation.
Missed reporting timelines. SAE identified but reported weeks later.
No trend analysis. Same failure mode across 15 complaints, never aggregated.
PMS disconnected from production. Manufacturing never learns about field failures.
Digital PMS vs paper complaint registers
Paper registers work for low complaint volumes. As product volume and distribution grow, you need:
- Searchable complaint database by product, batch, date, severity
- Automatic escalation for reportable events
- Link to batch traceability and CAPA
- Dashboard for management review
- Audit trail on investigation updates
Integrated QMS platforms connect complaints to batch records, CAPA, and document control — so a field failure triggers the same closed-loop process as an internal deviation.
Need complaint handling linked to batch traceability and CAPA? RapidFacto supports post-market surveillance workflows integrated with your manufacturing QMS. Book a demo.