Resources

Adverse Drug Reaction Reporting for Clinics in India: PvPI Documentation and Follow-Up Workflow

A patient reports a new symptom after starting a medicine. The prescribing doctor needs the treatment history. The pharmacist may need to identify the dispensed brand and batch. A nurse may have recorded the first call. The clinic owner needs to know whether the event was reported and followed up.

In this guide15 sections
  1. 01Separate immediate patient care from reporting
  2. 02Identify which safety workflow applies
  3. 03Open an initial case when there is reasonable suspicion
  4. 04Capture the minimum PvPI reporting information
  5. 05Build a clear medicine and reaction timeline
  6. 06Record seriousness and outcome separately
  7. 07Preserve evidence without changing the original clinical record
  8. 08Submit through a current PvPI channel
  9. 09Keep patient identity and confidentiality controlled
  10. 10Treat follow-up as part of the report
  11. 11Learn from the event without assigning blame automatically
  12. 12Assign responsibility by clinic role
  13. 13Test the workflow with fictional data
  14. 14Questions to ask CliniKite
  15. 15Conclusion

Separate immediate patient care from reporting

The first workflow is the patient's clinical care. The second is documentation and reporting.

A reporting form must never delay an urgent clinical assessment or the clinic's emergency process. Staff should first route the patient to the responsible clinician according to the symptoms, circumstances, and clinic protocol.

Once the immediate situation is being managed, open a safety record containing:

  • Patient and encounter reference
  • Date and time the clinic learned about the event
  • Person who reported it
  • Current contact details
  • Suspected medicine
  • Description of the event
  • Current clinical status
  • Clinician assigned
  • Immediate actions recorded by that clinician
  • Whether outside care or escalation occurred
  • Person responsible for the PvPI report
  • Next review date

The safety record should not replace the consultation note. It should link the patient-facing clinical record to the reporting workflow.

Identify which safety workflow applies

Not every medicine-related problem is the same.

Suspected adverse drug reaction

An ADR concerns a harmful, unintended response associated with a medicine used at normal therapeutic doses. A report may be submitted based on suspicion. The clinic does not need to prove that the medicine caused the reaction before reporting.

The current PvPI healthcare-professional form states that reporting is voluntary and provides separate fields for the suspected reaction, medicine, clinical history, seriousness, outcome, and reporter. PvPI ADR Reporting Form, version 1.4.

Adverse event

An adverse event is a medical occurrence after exposure to a pharmaceutical product without requiring an established causal relationship.

Record the chronology and relevant facts. Do not convert a temporal association into a confirmed diagnosis or causal conclusion.

Medication error or near miss

Examples include selecting the wrong patient, medicine, strength, route, quantity, frequency, or batch. An error may be intercepted before it reaches the patient.

A medication-error or near-miss workflow should capture what happened, where it was intercepted, contributing conditions, and the corrective action. If the event also involves a suspected adverse reaction, both workflows may be relevant.

WHO distinguishes reporting and learning systems for medication errors from pharmacovigilance while explaining how the systems can support one another. WHO medication-error reporting guidance.

Product-quality problem or recall

A leaking container, damaged strip, suspected counterfeit product, contamination concern, or notified recall needs a product and batch investigation. If the patient also experienced a suspected reaction, do not force staff to choose only one record.

Use the drug recall workflow for stock freezing, batch tracing, supplier communication, returns, and reconciliation.

Vaccine or medical-device event

The PvPI ADR form notes that serious events following immunisation can use the Serious AEFI notification form. Medical-device adverse events have separate Materiovigilance Programme of India resources.

Do not send every incident through a generic medicine ADR form merely because it occurred inside the clinic. IPC Materiovigilance reporting tools.

Open an initial case when there is reasonable suspicion

Waiting for complete certainty can produce an incomplete chronology and lost follow-up.

The PvPI form distinguishes an initial case from a follow-up case. A practical clinic workflow should do the same.

Create the initial case when a healthcare professional or patient reports a possible relationship between a medicine and an event. Record uncertainty honestly:

  • Suspected relationship
  • Relationship unclear
  • Alternative explanation being assessed
  • Information incomplete
  • Follow-up required
  • Report submitted without a final causal conclusion

Do not label the medicine as the confirmed cause unless the responsible professional has made and documented that assessment.

The clinic's internal case number should remain separate from the patient's UHID, prescription number, PvPI report reference, and any AMC reference. Store the relationships between them rather than reusing one identifier for every purpose.

Capture the minimum PvPI reporting information

The version 1.4 healthcare-professional form identifies essential reporting information including:

  • Patient initials
  • Age at the onset of the reaction
  • Reaction term or description
  • Reaction onset date
  • Suspected medicine
  • Reporter information

The form also allows a clinic to provide substantially more useful context.

Patient and event information

Record:

  • Patient initials for the report
  • Internal patient and encounter reference
  • Age or date of birth
  • Gender
  • Weight, when relevant and available
  • Reaction start and stop dates
  • Description of the event
  • Management recorded by the responsible clinician
  • Outcome
  • Seriousness classification
  • Relevant investigations with dates
  • Relevant medical and medication history

The internal record can maintain the verified patient identity. The external report should follow the information requested by the official form and the clinic's approved privacy process.

Suspected medicine information

Capture:

  • Brand and generic name
  • Manufacturer, when known
  • Batch or lot number
  • Expiry date, when known
  • Dose
  • Route
  • Frequency
  • Therapy start and stop dates
  • Indication
  • Action taken after the event

If the clinic dispensed the medicine, connect the ADR case to the prescription, pharmacy sale, batch, inward invoice, and dispensing pharmacist.

If the medicine came from another pharmacy, record the information actually available. Do not invent a batch, manufacturer, or dispense date merely to complete the form.

Concomitant products and relevant history

The form asks about other medical products, including self-medication and herbal remedies, as well as relevant history such as allergies, pregnancy, hepatic or renal dysfunction.

Preserve what the patient or clinician reported and its source. Do not silently copy an old medicine list and present it as confirmed current use.

Build a clear medicine and reaction timeline

A useful ADR report explains sequence.

The timeline should show:

  • When the medicine was prescribed
  • When the patient started it
  • Dose, route, and frequency actually reported
  • When the event began
  • When the clinic learned about it
  • Relevant investigations or observations
  • What action the clinician recorded
  • Whether the medicine was changed or stopped
  • Whether the event improved, persisted, or changed
  • When the initial report was submitted
  • When follow-up information was sent

Do not use the software to recommend withdrawal, dose modification, or reintroduction. Those are clinical decisions.

The PvPI form contains fields concerning action taken and whether a reaction reappeared after reintroduction. Record such information only when it genuinely exists. A clinic should never perform an unsafe reintroduction merely to complete a reporting field.

The digital prescription guide explains why issued prescriptions, later changes, and medicine instructions must remain attributable rather than being overwritten.

Record seriousness and outcome separately

The PvPI form lists serious outcomes including:

  • Death
  • Life-threatening event
  • Initial or prolonged hospitalisation
  • Disability
  • Congenital anomaly
  • Another medically important event

Seriousness describes the consequences of the event. It does not prove that the suspected medicine caused it.

Outcome

Record the outcome separately:

  • Recovered
  • Recovering
  • Not recovered
  • Recovered with sequelae
  • Fatal
  • Unknown

Avoid using 'closed' as a substitute for the clinical outcome. A case may be administratively closed while the outcome remains unknown. It may also remain open because the clinic is waiting for follow-up information.

Preserve evidence without changing the original clinical record

An ADR report can reveal that the medical record is incomplete or wrong. For example, the medicine start date may have been entered incorrectly, the dispensed batch may belong to another transaction, or an allergy may have been documented after the prescription was issued.

Do not edit the old record silently.

The correction should preserve:

  • Original value
  • Corrected value
  • Reason
  • Source of the correction
  • Person making it
  • Clinical approval where required
  • Date and time
  • Documents or reports affected
  • Whether the PvPI submission needs follow-up information

The medical-record correction workflow describes how to correct current information while preserving the earlier entry and downstream history.

Submit through a current PvPI channel

The official PvPI ADR page encourages healthcare professionals and patients to report suspected adverse events and links the healthcare-professional form, consumer forms, monitoring centres, mobile application, and helpline. IPC PvPI ADR reporting.

The current version 1.4 form lists these routes:

  • Send the completed form to the nearest Adverse Drug Reaction Monitoring Centre
  • Submit it to the National Coordination Centre for PvPI
  • Email [email protected]
  • Call the PvPI helpline at 1800 180 3024
  • Use the ADRPvPI mobile application

The form lists the helpline hours as Monday to Friday, 9:00 AM to 5:30 PM.

The official AMC page was updated on 31 July 2026 and links the current national list. Use that page rather than storing an old centre count or address in the clinic's procedure. Current ADR Monitoring Centre directory.

Submission evidence

After submission, record:

  • Submission date and time
  • Channel
  • Form version
  • Person submitting
  • Destination
  • Files sent
  • Reference or acknowledgement
  • Follow-up requested
  • Next review date

A 'report prepared' status is not the same as 'report submitted.'

Keep patient identity and confidentiality controlled

The PvPI form states that the patient's identity is handled confidentially. The clinic must still control how information leaves its own systems.

Before submission:

  • Confirm the intended PvPI or AMC destination
  • Use the information requested by the official form
  • Avoid attaching an unrestricted medical-record export
  • Remove unrelated patient and family information
  • Restrict report preparation and export to authorised staff
  • Record who downloaded or transmitted the report
  • Protect the clinic's retained copy
  • Do not send the report through an unapproved personal account

Consumer reporting forms are available in multiple Indian languages. If the patient reports directly, the clinic should distinguish the patient's report from the clinic's own professional documentation. PvPI programme profile.

Treat follow-up as part of the report

The initial report may not contain the final outcome, investigation result, discharge information, or complete medicine history.

Create a follow-up worklist containing:

  • Case number
  • Initial submission date
  • Missing information
  • Person responsible
  • Patient contact status
  • Investigation status
  • Outcome status
  • AMC or PvPI query
  • Due date
  • Follow-up submission date
  • Final administrative status

Do not overwrite the first report with the later version. Preserve the initial report, each follow-up, and the differences between them.

The patient may be lost to follow-up or may decline further contact. Record that outcome honestly. Do not mark 'recovered' merely to close the task.

Learn from the event without assigning blame automatically

A pharmacovigilance report contributes to medicine-safety monitoring. The clinic also needs to examine its own workflow.

Ask:

  • Was the prescription clear?
  • Was the current medication list available?
  • Were allergies and relevant history visible?
  • Was the correct patient selected?
  • Did the pharmacy dispense the prescribed product and batch?
  • Were patient instructions documented?
  • Could the patient contact the clinic easily?
  • Did staff recognise the reportable event?
  • Was a clinician available to review it?
  • Was follow-up assigned and completed?
  • Did access controls protect the record?
  • Could the report be reconstructed later?

WHO's incident-reporting guidance emphasises structured reporting and learning as mechanisms for improving patient safety and preventing recurrence. It also cautions that reporting data has strengths and limitations. WHO patient-safety incident reporting.

An incident total should not be used as a simple performance ranking between doctors or staff. Reporting volume can reflect reporting culture, workload, case mix, or process maturity rather than a direct measure of safety.

Assign responsibility by clinic role

A practical responsibility model may look like this:

Use individual accounts. A shared 'clinic' login cannot show who assessed, edited, exported, or submitted the report. See the role-based access checklist.

Doctor or dentist

  • Assesses the patient and records the event
  • Confirms suspected medicines and relevant history
  • Reviews seriousness and outcome
  • Approves the professional content of the report

Pharmacist

  • Verifies the dispensed product, strength, batch, expiry, and quantity
  • Reconciles the prescription and pharmacy transaction
  • Records returns and stock actions
  • Supports medicine-history verification

Nurse or authorised coordinator

  • Records the first contact
  • Gathers approved follow-up information
  • Tracks investigations and appointments
  • Escalates clinical questions

Clinic owner or administrator

  • Defines the procedure and assigns access
  • Reviews overdue cases
  • Maintains training and audit records
  • Verifies that submissions are completed

Test the workflow with fictional data

Use a non-production environment and a fictional patient.

Create:

  • A completed fictional consultation
  • A signed prescription for Medicine A
  • A pharmacy dispense with a fictional batch
  • A reported event two days later
  • A relevant fictional investigation
  • An initial outcome of 'recovering'
  • An initial PvPI report
  • A later follow-up with a final outcome

Also create a medication near miss with no patient harm and verify that it does not become a fabricated ADR.

Demonstration steps

Ask staff to demonstrate that they can:

  • Open the case without changing the issued prescription
  • Build the medicine and reaction timeline
  • Retrieve the dispensed batch
  • Include concomitant medicines and relevant history
  • Record seriousness and outcome separately
  • Export only the information needed
  • Record submission and acknowledgement
  • Add follow-up without deleting the initial report
  • Correct a date through an attributable amendment
  • Produce the complete case history

Questions to ask CliniKite

CliniKite's public pages describe connected consultations, prescriptions, laboratory records, pharmacy dispensing, batches, role-based access, audit logs, backups, and exports. CliniKite features.

These capabilities provide relevant source information for an ADR workflow. The public pages do not currently claim automatic PvPI submission, automated causality assessment, a dedicated ADR module, or regulatory filing on the clinic's behalf.

During a demonstration, ask:

  • Can an ADR case link to the consultation and prescription?
  • Does the original prescription remain unchanged?
  • Can staff retrieve the exact dispensed batch?
  • Can concomitant medicines and relevant history be reviewed?
  • Are seriousness and outcome recorded separately?
  • Are initial and follow-up reports preserved separately?
  • Do corrections preserve their history?
  • Who can view, export, and submit the report?
  • Is each action attributable in the audit history?
  • Can the clinic create a restricted export?
  • Can the case be restored from backup?
  • Which parts of the workflow remain manual?

Ask for the answers using fictional data and obtain written confirmation for requirements essential to the clinic's pharmacovigilance procedure.

Conclusion

A dependable ADR workflow begins with the patient's clinical needs, not the reporting form.

Record the suspected event without prematurely declaring causality. Connect the patient, medicine, prescription, pharmacy batch, clinical history, investigations, seriousness, outcome, and reporter. Submit through a current PvPI route, preserve the initial report, and treat follow-up as part of the same case.

The operational test is reconstruction. Months later, the clinic should be able to explain what was reported, what medicine exposure was known, what care was documented, where the report was sent, what follow-up occurred, and who completed each action.

Evidence used

Sources and claim notes

  • PvPI ADR Reporting Form, version 1.4

    Primary source for voluntary reporting, initial and follow-up reports, patient and medicine fields, seriousness, outcomes, reporting routes, confidentiality, and minimum reporting information.

  • IPC PvPI ADR reporting

    Official reporting page linking healthcare-professional and consumer forms, monitoring centres, the mobile application, and the PvPI helpline.

  • Current ADR Monitoring Centre directory

    Official current directory for locating ADR Monitoring Centres without relying on a stored centre count or address.

  • PvPI programme profile

    Official overview supporting the description of PvPI reporting resources, consumer reporting, and Indian-language forms.

  • WHO medication-error reporting guidance

    Supports the distinction between medication-error reporting and pharmacovigilance and explains how the systems can complement one another.

  • WHO patient-safety incident reporting

    Supports structured incident reporting and learning while noting the limitations of reporting data.

  • IPC Materiovigilance reporting tools

    Official source for the separate reporting resources applicable to medical-device adverse events.

  • CliniKite features

    Supports only the stated public descriptions of consultations, prescriptions, laboratory records, pharmacy dispensing, batches, access controls, audit logs, backups, and exports.

  • CliniKite security and data

    Supports the evaluation questions concerning clinic data control, role-based access, audit history, backups, exports, and connected-service boundaries.

A useful next step

Test an ADR reporting workflow in a CliniKite demonstration

Bring the real clinic workflow, current plan and people who run the day. We will show the connected path and its limits clearly.

This article provides general clinic-operations, software-evaluation, documentation, and pharmacovigilance-readiness information. It is not medical, pharmaceutical, legal, regulatory, licensing, or patient-specific advice. Clinics should follow their emergency and clinical protocols and confirm reporting requirements, report content, timelines, confidentiality controls, and submission routes with PvPI, the relevant AMC, applicable authorities, and qualified professionals.