Pharmacovigilance Setup for Clinical Trials in India

Most sponsors treat pharmacovigilance as a clause in the protocol and a folder for adverse event forms. It works that way right up until the first serious adverse event lands on a Friday evening, and it becomes clear that nobody has agreed who assesses it, who reports it, and to whom, by when.

A pharmacovigilance setup is not the safety section of the protocol. It is the operating system underneath it: named roles, a reporting clock that starts the moment someone becomes aware of an event, and documentation built to survive an inspection rather than to close a checklist. This is general, educational information on how that system is typically structured for trials conducted in India. It is not legal or regulatory advice, and current requirements should always be confirmed against the New Drugs and Clinical Trials Rules, 2019, and the latest CDSCO guidance before you rely on them.

Roles and responsibilities, defined before day one

Every trial has an investigator obligated to record and report events at their site, and a sponsor obligated to monitor safety across the whole trial. In practice that chain has several more links, and the setup work is making each one explicit rather than assumed.

The investigator identifies the event, provides the initial clinical assessment, and reports upward within the site. A sponsor-side safety physician or pharmacovigilance lead receives it, reviews it against the reference safety information, and decides what gets reported onward and on which clock. Where a CRO is running safety operations, the delegation of authority log has to state, in writing, exactly which of these steps the CRO performs and which the sponsor retains — reporting to a regulator is a sponsor obligation even when a CRO drafts the report.

The Ethics Committee sits alongside this chain rather than inside it. It receives safety reports as part of its ongoing oversight of the trial, and its secretariat needs to know, from the plan, what it will receive and on what schedule so a report is not the committee's first encounter with the process.

Reporting timelines: Ethics Committee and CDSCO

The structure below reflects how sponsors commonly organise SAE and SUSAR reporting under Indian trial regulation. Exact clock lengths and formats are set out in the current rules and periodic CDSCO circulars, and a qualified regulatory advisor should verify the specifics that apply to your trial and phase before you build them into a plan.

Serious adverse events, to the Ethics Committee

A serious adverse event occurring at a site is typically reported to that site's Ethics Committee on a short, fixed clock from when the investigator becomes aware of it, with a fuller follow-up report to complete the causality and outcome picture shortly after. The trigger is awareness, not confirmation. Teams that wait for a complete clinical picture before starting the clock are usually already late.

SUSARs, to CDSCO

A Suspected Unexpected Serious Adverse Reaction — an event that is both unexpected relative to the reference safety information and judged at least possibly related to the investigational product — is reportable to CDSCO on an expedited basis, with fatal or life-threatening cases moving on the shortest clock and a detailed follow-up required afterward. Other SUSARs and aggregate safety information are typically compiled into periodic reports. None of this is optional once a case meets the definition; the judgment call that matters is whether it meets the definition in the first place, which is where causality assessment does the real work.

The clock starts on awareness, not on completion of the causality assessment. Build the workflow so the report can go out provisionally and be updated, rather than held while someone tries to make it perfect.

Causality assessment, and why it is not one person's opinion

Causality — whether the event is plausibly related to the investigational product — decides whether a serious event is also a SUSAR, which decides which clock applies. Getting it right, and documenting how it was reached, matters more than most other safety paperwork.

Good practice separates two assessments rather than collapsing them into one. The investigator gives an initial clinical judgment, close to the patient and the event. The sponsor's safety physician gives an independent assessment against the full safety database, not just this one case, often using a structured tool such as the WHO-UMC categories or a Naranjo-style algorithm to keep the reasoning consistent across cases and reviewers. Where the two assessments disagree, the more conservative one — the one that treats the event as related — is generally what drives the reporting decision, and the disagreement itself gets recorded rather than quietly resolved.

Blinding adds a real constraint. Unblinding a case for expedited reporting should be limited to what the report requires, handled by people outside the trial's day-to-day conduct where feasible, and logged — who unblinded, when, and why — so the integrity of the ongoing comparison is not compromised by a process meant to protect participants.

Documentation a sponsor or CRO should have in place

An inspector, or an auditor doing due diligence before a partnership, is not looking for a folder of forms. They are looking for a system that would have caught a missed timeline before it became one. That system rests on a small set of documents.

A pharmacovigilance plan specific to the trial, naming roles, reporting lines, and timelines rather than pointing generically at the regulations. A current delegation of authority log covering safety tasks specifically, updated when personnel change. Written SOPs for case intake, causality assessment, expedited reporting, and periodic reporting, each with a named owner. A safety database or tracker reconciled periodically against the clinical database, since the two are usually maintained separately and drift apart without a scheduled check. Acknowledgment records from the Ethics Committee and CDSCO for each submission, not just the sponsor's own outbound log. Training records showing site staff were trained on recognition and reporting before enrolment, not after the first event. And where a report went out late or a case was reclassified, a short record of why and what changed as a result — the kind of documentation that turns a single miss into evidence of a functioning system rather than a pattern.

None of this is difficult to build. It is easy to skip, because it looks like overhead until the week it is the only thing that matters.