Skip to main content

Suspected Adverse Drug Reactions: Clinical Records and PvPI Reporting

Record a suspected adverse drug reaction as a clinical event with the medicine exposure, symptoms, timing, care provided and uncertainty. Do not wait for proof of causation before considering a PvPI report. Keep immediate care, the reviewed allergy/adverse-effect record and external reporting as separate actions. A submitted report does not establish that a medicine caused the event or that the patient’s care is complete.

By Bractis · Updated · 16 min read

Indian doctors, nurses and pharmacists documenting suspected medicine reactions and coordinating reporting to the Pharmacovigilance Programme of India.

Treat the clinical event before completing the reporting workflow

If a patient has an acute serious reaction, arrange the appropriate clinical assessment and urgent care first. The reporting form must not delay treatment, transfer or communication with the receiving service. Record the actual event and care chronology once the immediate response permits.

A medicine taken before an event is part of the exposure history, not automatic proof of causation. Retain the clinician’s current assessment and competing explanations. A report can remain suspected while further information is obtained.

PvPI’s reporting materials encourage reports of suspected reactions, including known and unknown or serious and non-serious events. They describe a surveillance process that can receive uncertainty. The clinic should not require an internally “confirmed allergy” status as a prerequisite to considering a report.

Source: Indian Pharmacopoeia Commission: General Suspected ADR Reporting Form, version 1.4

Source: Indian Pharmacopoeia Commission: PvPI Handbook, 2025

Build a chronology from exposure to follow-up

Record when the medicine was started, the relevant use before symptoms, symptom onset, changes made, treatment received and the subsequent course. Use actual dates and times where known; mark approximate recollections instead of manufacturing precision.

Preserve every relevant product identity, including strength, formulation and route when available. A combination medicine needs its components established. Also record other treatments and circumstances that the clinician considers relevant rather than declaring the most recently added drug responsible by default.

If information comes from a caregiver, an outside discharge note or a later phone call, identify that source. The date the clinic learned about the event is separate from the date it occurred. A retrospective entry should show both.

Record what happened after a medicine was changed or stopped if that is known. Do not deliberately re-expose a patient merely to complete a causality field. Unknown follow-up information is an honest state, not a reason to invent a response.

Keep severity, seriousness and causation separate

In ordinary conversation, “severe” describes how intense a symptom felt. Reporting seriousness uses outcome-based criteria. The IPC form lists outcomes such as death, a life-threatening event and hospitalisation among serious-reaction criteria. A dramatic symptom description and a regulatory seriousness assessment should not be collapsed into one dropdown without explanation.

Record the actual outcome and the clinician’s assessment using the reporting tool’s definitions. Do not infer that an event was non-serious merely because the patient is now attending the clinic, or that hospitalisation proves which medicine caused it.

Causality is a separate assessment. PvPI materials describe review through the monitoring-centre and national programme process. The clinic’s initial report should provide useful evidence and retain uncertainty, rather than claim the authority of a completed external causality assessment.

Source: Indian Pharmacopoeia Commission: General Suspected ADR Reporting Form, version 1.4

Coordinate three records without pretending they are one

The clinical event note, the patient’s reviewed medicine-warning record and the external report serve different purposes. They should refer to the same underlying event while retaining their own status and history. Updating one does not automatically complete the others.

On a narrow screen, scroll the table horizontally to read all columns.

Separate actions after a suspected medicine reaction
Record or actionWhat it establishesWhat it does not establish
Clinical event noteSymptoms, exposures, assessment and actual care providedConfirmed causation from temporal association alone
Allergy/adverse-effect reviewClinician’s current classification and future medicine adviceThat every adverse effect is an allergy
Patient explanationWhat advice was given and how understanding was checkedThat outside records or pharmacy copies changed automatically
PvPI report preparedInformation assembled in the appropriate reporting formatSuccessful submission or acknowledgement
Report submitted or acknowledgedTransmission evidence or a programme reference if receivedExternal confirmation of causality or completed patient follow-up
Later report updateAdditional facts linked to the same event and reportA new unrelated event unless the evidence supports one
Clinical closureThe responsible team’s documented follow-throughThat surveillance review is finished or no future information can arise

Prepare the report from evidence and the current form

The general IPC form marked version 1.4 identifies minimum patient, reaction, suspected-medicine and reporter information, and distinguishes an initial case from a follow-up case. Use the form appropriate to the event; a special-purpose COVID-19 form is not the generic clinic template. Check the current official version and complete relevant additional information. Required fields do not create a universal legal reporting deadline for every private clinic.

The 2025 PvPI handbook directs reports to the programme’s ADR Monitoring Centres and describes reporting options. Use the current official IPC materials to verify the route and form. This article does not submit a report, create an account or guarantee that an old contact detail remains operational.

Retain a local reference to the clinical event, the version submitted and any acknowledgement obtained. If the outcome is uncertain after transmission, record it as uncertain rather than repeatedly submitting indistinguishable reports. Follow the programme’s process for clarification or additional information.

Supply information through the appropriate clinical reporting channel and preserve confidentiality. Do not place a real patient’s reaction narrative in a public support ticket, product demonstration or marketing lead form merely to ask how the feature works.

Source: Indian Pharmacopoeia Commission: General Suspected ADR Reporting Form, version 1.4

Source: Indian Pharmacopoeia Commission: PvPI Handbook, 2025

Worked example: later hospital evidence changes the record, not the event date

Fictional event ADR-57 is reviewed at a clinic in Udaipur after urgent care was provided elsewhere. The patient recalls starting product X on 22 October and using product Y on the morning of 23 October. A rash and light-headedness began at about 10:30 on 23 October, according to the family. The clinic first documents the account on 24 October. Those dates have different meanings; the later note must not make the reaction appear to have started at the clinic.

At the first review, the family says the patient was “kept in hospital”. That phrase alone does not establish whether the patient attended an emergency department, remained under observation or was admitted. The clinician records the reported care and seeks the actual evidence, while making the appropriate initial assessment and reporting decision from the information available. Reporting should not wait for an invented certainty, and clinical care should not wait for the report.

A hospital document received on 26 October confirms admission on 23 October at 11:20 and discharge on 25 October. It supplies an outcome-based seriousness fact that was not established from the family’s wording alone. It does not identify which product caused the event. The discharge description “improving” also does not prove full recovery on 29 October. Preserve the document date, receipt date and relevant clinical facts separately.

The two products remain suspects for review in this exercise. X’s pack is available; Y’s initial photograph is incomplete. A clearer Y label arrives on 28 October and resolves an identity detail. That change improves the exposure record, but it is not a new reaction and does not automatically convert either suspect into a confirmed allergy. No intentional re-exposure is performed to answer the reporting form.

On a narrow screen, scroll the table horizontally to read all columns.

ADR-57: event time, evidence arrival and what can be concluded
SourceEvent describedWhen the clinic learned itEvidence limit
Patient accountX reportedly started on 22 October24 October consultationRecollection; exact use still requires reconciliation
Family accountY used on 23 October; symptoms about 10:3024 October consultationApproximate chronology; temporal association is not causation
Outside hospital recordAdmission 23 October at 11:20; discharge 25 OctoberDocument received 26 OctoberSupports hospitalisation history, not a particular causal medicine
Clearer Y labelIdentity detail for the already reported productImage received 28 OctoberAn exposure clarification for the same event, not a new reaction
Current follow-upPresent recovery and patient understanding need checkingOpen at the 29 October reviewDischarge improvement does not establish today’s outcome

Source: Indian Pharmacopoeia Commission: General Suspected ADR Reporting Form, version 1.4

Link report updates to the same event and retain uncertain transmission

Use a simulation to separate reporting activity from clinical events. For ADR-57, R0 is an initial report version containing the information available on 24 October. U1 adds the hospital evidence on 26 October. U2 adds the clarified product identity on 28 October. These are three reporting actions about one event in one fictional patient. Two suspected products do not turn it into two patients, and two follow-up versions do not turn it into three reactions.

The general IPC form’s initial/follow-up distinction supports linking new information to an existing case. Retain the local event reference, the original reporting reference if received, the added facts and their sources. Make the difference from the earlier version easy for the receiving team to understand. Do not copy an entire new initial narrative without identifying its relationship to the previous report.

In this local test, R0 and U1 receive simulated acknowledgements, while U2’s transmission outcome is uncertain. The correct summary is three attempted reporting actions with two simulated receipt confirmations and one unresolved outcome. It is not three confirmed submissions, and it says nothing about causality or clinical recovery. Save the exact attempted version and resolve the uncertainty through the appropriate reporting contact rather than creating an indistinguishable new case.

A later correction should be explicit. If a source turns out to describe a different patient, or a date was transcribed incorrectly, identify the affected fact and send a correction through the appropriate process. Do not silently rewrite the locally retained report to imply that the recipient saw the corrected information originally. Keep the clinical record and the reporting record aligned through traceable updates while respecting their separate purposes.

On a narrow screen, scroll the table horizontally to read all columns.

One fictional event with three simulated reporting actions
Action and dateInformation in that versionSimulated transmission evidenceAccurate description
R0 — 24 OctoberInitial symptoms, reported exposure and unresolved outside-care detailsReceipt acknowledged in the simulationInitial report about ADR-57; no causality confirmation
U1 — 26 OctoberHospital evidence of admission and dischargeReceipt acknowledged in the simulationLinked follow-up to ADR-57; seriousness evidence added
U2 — 28 OctoberClarified identity of the already reported product YOutcome uncertain; no acknowledgement recordedLinked update attempted; receipt still needs clarification

Source: Indian Pharmacopoeia Commission: General Suspected ADR Reporting Form, version 1.4

Close clinical and reporting tasks on their own evidence

The treating clinician still needs a usable current assessment and patient plan. A report acknowledgement cannot explain which products the patient should discuss before future use, what the present symptoms mean or when further care is needed. Review the medicine-warning entry and communicate the actual advice without adding a blanket class allergy from an unconfirmed association. Preserve the suspected products and the qualifications that matter to the next prescriber.

For ADR-57, the reporting contact owns clarification of U2’s receipt. The treating clinician owns the current outcome review and medicine advice. A staff member obtaining a discharge paper is helping with evidence collection, not conducting the causality assessment. These named responsibilities make a small clinic’s handover usable when one doctor is absent; a single “ADR completed” status would conceal the open work.

Explain the reporting purpose in language the patient understands. A suspected report contributes information to medicine-safety surveillance. It does not itself prove an allergy, identify negligence or replace the clinical discussion. The patient may have their own report or reference; retain that information so the programme can assess possible duplicates rather than assuming every report concerns a new person. Do not suppress a relevant account merely because another facility may also have reported.

Use only appropriate reporting channels for identifiable clinical information. The public guide’s demonstration should use invented records such as ADR-57, not a screenshot of a real discharge summary. In an actual handover, preserve sufficient patient linkage for the care and reporting purpose while avoiding unnecessary disclosure in general support or employer correspondence. A programme reference should not become a public-facing patient identifier.

The filled note below is a bounded status report, not a completed official submission. Its open items have different completion evidence: a reviewed outcome, current medicine advice explained to the patient, and confirmation of what happened to U2. No patient, report or message in this teaching case was sent to PvPI. A clinic can test these distinctions locally before deciding whether its software supports the workflow it needs.

Source: Indian Pharmacopoeia Commission: PvPI Handbook, 2025

Review future medicine advice without making every event an allergy

The clinician should decide how the event belongs in the allergy, adverse-effect and clinical-history parts of the record. A non-allergic adverse effect may still be important for future prescribing. Conversely, a suspected allergic event must not disappear because the reporting form has not yet been completed.

Give the patient a clear account of the current assessment, which medicine information matters and the instructions that apply now. Keep uncertain names or causes visibly qualified. An unreviewed “all drugs caused reaction” label can be as misleading as an empty warning field.

When the assessment changes after specialist review or further evidence, preserve the earlier entry and the reason for revision. Address relevant patient copies, referrals and pharmacy communication through the appropriate correction process. A local record edit cannot establish that every other provider has received the update.

Use a combined event-and-report tracking note

This original outline links the work without replacing the official reporting form. Complete the clinical facts and reporting status separately. It is useful for a clinic where the treating doctor, the person assembling records and the reporting contact may be different people.

Test a later outcome update and a separate clinical decision

In a fictional workflow test, record an event involving two recently used medicines with uncertain causation. Prepare a simulated report without sending it, then add a later hospital outcome. The system should link the update to the original event while preserving what was known at each stage.

Separately revise the clinician’s medicine-warning assessment. Confirm that a report reference does not automatically mark every suspect medicine as a confirmed allergy and that an updated allergy status does not falsely imply an external report was amended.

For local quality review, count events, reports and updates separately. One event with an initial submission and two follow-up updates is one event with three reporting actions, not three affected patients. Document the denominator before interpreting reporting activity.

Evaluate the current Bractis workflow using fictional data and a mocked reporting state. This article does not claim a live PvPI integration, automatic causality assessment or independent validation of adverse-reaction decision support.

Fictional example: the reaction date and report date tell different stories

A medicine was started on 7 November, symptoms appeared on 8 November and immediate clinical care was provided. The clinic later assembled a reporting record on 11 November. Those three dates remain distinct, and causation is still recorded as uncertain while another recent medicine is reviewed. A later outcome update is linked to the same event. The reporting date does not rewrite the clinical timeline, and the external-report status does not decide the patient’s allergy classification.

Suspected ADR Event and Reporting Review

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Chronology
Can you distinguish exposure, reaction, care, documentation and reporting dates?
Assessment scope
Are severity, seriousness and causation represented as different questions?
Connected records
Do the clinical event, reviewed warning record and external report retain separate statuses?
Follow-up ownership
Who obtains new information, updates the report and completes the patient’s clinical handover?

Questions doctors ask

Must a clinic prove causation before considering a PvPI report?

PvPI accepts suspected reaction information. Provide the evidence and uncertainty rather than requiring a confirmed allergy diagnosis before considering reporting.

Should every adverse drug reaction become an allergy entry?

No. The clinician should classify the actual event and preserve relevant adverse-effect history and future advice. Reporting status does not automatically determine allergy classification.

Are “severe” and “serious” the same in ADR documentation?

Symptom intensity and outcome-based reporting seriousness are different concepts. Record the facts and use the reporting tool’s seriousness definitions rather than relying on the adjective alone.

Does a reporting acknowledgement confirm that the medicine caused the event?

No. It is evidence about report receipt or processing. Causality assessment and the patient’s clinical follow-up remain separate matters.

How should an initial report and two later updates be counted?

If they concern the same event, retain one event linked to three reporting actions. Do not report the actions as three separate patients or reactions.

What if hospitalisation is confirmed after the initial suspected ADR report?

Record the new source and what it establishes, reassess the relevant clinical and seriousness information, and provide a linked follow-up through the reporting process. Keep the original event date and earlier report version; hospitalisation does not by itself establish which medicine caused the event.

Should an unacknowledged ADR update be recorded as successfully received?

No. Retain the attempted version, route and available transmission evidence, and clarify the outcome using the existing case reference where available. Keep uncertain receipt separate from failed transmission, a new reaction and the patient’s clinical follow-up.

Sources and scope

Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Trace a fictional suspected reaction through clinical care, a separately reviewed warning record and a mocked report with later updates, preserving uncertainty and event identity.

Request a clinic demo