India consumes an enormous volume of medicines, yet contributes a disproportionately small share of the individual case safety reports held in the WHO's global VigiBase database, and most Indian reports originate from a limited number of hospital-based ADR Monitoring Centres. The community pharmacy, where patients collect medicines every day, sits outside this loop: Suspected ADR Reporting Forms are usually not stocked, pharmacists are frequently unaware of the PvPI procedure and the nearest AMC, and consumers have no idea that a side effect is something one reports rather than merely tolerates.
Nobody measures this gap at the counter level, and nothing at the counter tells a patient that reporting is even possible. There is a need for (a) a simple, ethically sound measurement of ADR-reporting awareness among community pharmacists and consumers, and (b) a low-cost, visible, PvPI-aligned reporting desk that converts a pharmacy from a passive dispenser into an active drug-safety outpost — the role the Pharmacy Practice Regulations, 2015 already envision for the registered pharmacist.
Abstract
Adverse drug reactions are a quiet but heavy burden on Indian patients, yet the reports that reach the national pharmacovigilance system come mostly from a limited set of hospital-based ADR Monitoring Centres. This project studies the gap where it actually lives: the community pharmacy counter. Run across the final six weeks of the ER-2020 practical training, the study measures ADR-reporting awareness among 25 registered community pharmacists and 100 consumers using an anonymised, aggregate-only KAP questionnaire, audits the model pharmacy's reporting readiness before and after an intervention, and installs a working ADR reporting desk aligned to PvPI procedures.
Introduction
India runs one of the world's largest pharmacovigilance networks. The Pharmacovigilance Programme of India was launched in July 2010, and since April 2011 the Indian Pharmacopoeia Commission, Ghaziabad has functioned as its National Coordination Centre, with roughly 250 ADR Monitoring Centres — medical colleges, district and corporate hospitals — feeding individual case safety reports into the WHO's VigiBase through VigiFlow. Consumers can also call the toll-free helpline 1800-180-3024 or use the ADR PvPI mobile app.
But the network's entry points remain largely institutional. The community pharmacist — often the first and last health professional a patient speaks to — is rarely equipped to recognise a suspected reaction and pass it on, even though the Pharmacy Practice Regulations, 2015 frame patient counselling and the maintenance of medication records as professional duties of the registered pharmacist. The counter where lakhs of Indians collect medicines every day is, at present, a blind spot of the safety system.
Existing vs proposed
- Existing practice: ADR reporting is treated as a hospital activity; Suspected ADR forms are not stocked at most counters; patients mention side effects casually and are often told simply to stop the medicine; there is no record, no referral and no data.
- Proposed: measure the exact awareness gap with a structured KAP instrument for pharmacists and consumers; fix the counter with a visible desk (form rack, signage, AMC referral card); rehearse the correct flow through ten role-played, fully simulated cases; report findings and recommendations to the pharmacy owner so the desk survives after the training ends.
Feasibility
- Technical: the study needs printed forms, a clipboard, consent scripts and Excel — all within a D.Pharm student's reach during the placement.
- Economic: total cost stays under ₹500 for printing and signage; the desk occupies one shelf of the counselling corner.
- Operational: the preceptor supervises every step; respondents give informed consent; the desk adds about a minute to a counselling interaction once installed.
- Ethical: the design deliberately avoids identifiers — the report never names a respondent, a patient or a prescription, only counts and patterns. Every demonstration case is simulated, so the study never creates or submits a fabricated real-world ADR report.
In scope
- One model community pharmacy (Sahyadri Medicals, a fictional stand-in for your training site) plus five neighbouring pharmacies for the pharmacist survey.
- 25 registered pharmacists and 100 adult consumers, surveyed only after informed consent.
- Awareness, attitude and self-reported practice regarding ADR reporting; a desk-readiness audit; simulated role-play cases.
- Descriptive statistics (frequencies, percentages, means, cross-tabs) computed in Excel.
- Awareness poster and handbill in the local language, plus the mini-report and training diary.
Out of scope (and out of ethics)
- No real patient identifiers, prescriptions or case records are collected, and no government ID numbers are ever stored.
- No causality assessment beyond what the Suspected ADR form itself asks — the study does not practise medicine.
- No actual submission of real ADRs: every demonstration case is simulated. If a genuine reaction appears during training, the standing rule is to refer the patient to the pharmacist or physician and use the pharmacy's normal referral channel.
- No clinical trials, no paediatric respondents, no laboratory or clinical measurements.
- No inferential claims: a six-week, single-locality sample cannot prove why reporting rates differ, and the report says so plainly.
Research design. A cross-sectional, descriptive KAP study with an embedded pre-test/post-test audit of the model pharmacy's reporting desk. The design is deliberately simple: the training window is short, respondents include lay people, and the ethical bar — anonymised, aggregate-only data — must be easy to maintain in a busy shop.
| Phase | Weeks | Activities | Output |
|---|
| Orientation and review | 1 | PvPI and PPR-2015 review; site mapping; draft instruments | Annotated reference notes |
| Instrument development | 2 | Draft KAP questionnaire (pharmacist and consumer versions); preceptor and faculty review; pilot on five respondents each; revise | Final instruments |
| Survey administration | 3–4 | Consented administration at counters; sheets coded A01, A02…; same-evening Excel entry with random re-checks | Completed response set |
| Desk intervention | 4–5 | Pre-audit, desk installation, ten simulated role-play cases, post-audit | Audit scores, rubric sheet |
| Analysis and reporting | 6 | Descriptive statistics, charts, recommendations; diary consolidation | Mini-report and awareness poster |
Sampling. Pharmacists: purposive sampling of one registered pharmacist per pharmacy across six outlets in the locality, extended to a second pharmacist where staffing allows, up to 25. Consumers: systematic convenience sampling — every fifth consenting adult customer during assigned counter hours, until 100 responses. Both questionnaire versions share one structure: 10 knowledge items (true/false/unsure), 5 attitude items on a five-point Likert scale, and 5 practice items (ever reported, ever seen the form, knows the helpline 1800-180-3024, knows the nearest AMC).
Instruments. (1) The two KAP questionnaires, content-validated by the preceptor and one pharmacy-practice faculty member and pilot-tested on five respondents each. (2) A ten-point desk-readiness checklist: form rack stocked, signage visible, AMC referral card current, counselling corner marked, counter staff briefed. (3) A five-criterion role-play rubric — recognition, empathy, form accuracy, referral guidance, documentation habit — applied to ten simulated cases written by the student and cross-checked by the preceptor.
Analysis plan. All data goes into one Excel workbook with a written code book. Analysis is descriptive: frequencies and percentages per item, mean attitude scores, cross-tabs of pharmacist awareness against qualification and years in practice, and a pre/post comparison of the desk audit.
Ethics. Verbal informed consent precedes every questionnaire; participation is voluntary and refusal changes nothing about service. No names, phone numbers or ID numbers are recorded — sheets carry codes only, and the preceptor keeps the master code list, which is destroyed after the report is graded.