Adverse Event Reporting in Patient Support Programmes in Egypt: A Practical Guide

Short answer: a patient support programme (PSP) must treat every mention of a possible side effect as safety information, record it factually, and pass it to the pharmacovigilance team of the product owner within the time agreed in the contract. Nurse educators and coordinators speak to patients more often than most healthcare professionals do, so they hear about side effects early. European and UK regulators expect companies to take appropriate measures to collect and collate all reports of suspected adverse reactions, including those arising from patient support programmes. This guide turns that expectation into an operating procedure suited to programmes in Egypt. It is educational and operational; it does not replace your pharmacovigilance procedures, legal advice or medical advice.

• Every PSP contact can generate safety information. Staff should record suspected adverse events whether the patient volunteers them or the programme asks about them.
• Programme staff capture and forward. They do not judge causality, change treatment or give medical advice; the product owner's pharmacovigilance team assesses reports.
• A usable report needs four minimum elements (ICH E2D): an identifiable reporter, an identifiable patient, a suspected medicine and a suspected event. Missing details should be followed up.
• UK regulator guidance says measures should be proportionate to how likely the programme is to generate safety data, and lists staff training, written procedures and contractual wording with third parties as appropriate measures.
• In Egypt the Egyptian Drug Authority (EDA) offers an online reporting form to citizens through the WHO-UMC VigiFlow platform.
• Forwarding timelines are not set in this article. We have not verified Egyptian time limits, so agree them in the contract and confirm with your pharmacovigilance team.

Why patient support programmes matter for drug safety

A PSP typically includes onboarding, education, injection or device training, adherence follow-up and care coordination. Each of these contacts is a conversation about how the patient feels on treatment. That is valuable for safety, and it is also a compliance risk if staff do not know what to do with what they hear. A patient who mentions a rash during an adherence call has given the programme safety information, even if the call was about refills.

What counts as an adverse event report

An adverse event is an unwanted medical occurrence in a patient using a medicine, whether or not the medicine is thought to be the cause. ICH E2D describes four minimum elements for a valid individual case: an identifiable reporter, an identifiable patient, a suspected medicine and a suspected adverse event. UK regulator guidance adds that a report which gives only an outcome, such as a death, with no clinical details is not a valid suspected adverse reaction report, and that the company should follow up with the reporter for the clinical circumstances. For programme staff the practical rule is simple: if a patient mentions a health problem while on the product, record it and forward it, then let the pharmacovigilance team decide what it is.

Solicited and spontaneous reports

Regulatory guidance distinguishes between reports from organised data collection and spontaneous reports. A programme that actively asks patients about their treatment experience, for example through scheduled follow-up calls, is organised data collection. Reports from such programmes are treated as solicited and need a causality assessment by the company to decide what must be reported. Programmes without organised data collection may produce spontaneous reports. Which category your programme falls into is a decision for your pharmacovigilance and regulatory team, not for the field staff, and it should be written down.

A seven-step capture and forwarding procedure

1. Listen and record: write down the patient's own words, the product, the date the event started and the date of the report.
2. Identify the elements: who is reporting, who is the patient, which medicine, which event. Ask for missing details politely and once.
3. Do not interpret: avoid writing that the medicine caused or did not cause the event.
4. Escalate urgent situations: if the patient has severe symptoms, tell them to call 123 or contact their doctor immediately and involve the programme clinician.
5. Forward on the agreed channel and within the agreed time to the pharmacovigilance team, using the approved form.
6. Follow up: when the pharmacovigilance team requests more information, obtain it from the patient or treating doctor and send it back.
7. Reconcile: compare the programme's log with the pharmacovigilance database at an agreed interval to confirm nothing was missed.

Training that fits the risk

UK regulator guidance says the intensity of measures should be proportionate to how likely the programme is to generate safety data, and that programmes designed to solicit product information are expected to have more robust measures, such as detailed written procedures, training and adverse event forms. Training for company staff and third parties on pharmacovigilance concepts and on the data collection tools is listed as an appropriate measure. In practice, train all programme staff before they speak to patients, repeat the training when procedures change, and keep a training record.

Contracts and reconciliation

The same guidance lists contractual wording with third parties on collecting and forwarding safety information as an appropriate measure, and suggests checking that reports reach pharmacovigilance through reconciliation between departments or parties, audits and source data verification. A programme contract should therefore state who captures, who forwards, by what channel, within what time, who follows up, and how often the two parties reconcile. Because we have not verified Egyptian forwarding deadlines, leave the number of hours or days to your pharmacovigilance and regulatory advisers.

How patients and professionals can report to the EDA

The Egyptian Drug Authority states on its website that citizens can report adverse drug reactions, adverse events following immunisation, cosmetics-related events and medical device problems. Reports are made through an online form on the WHO-UMC VigiFlow platform and are assessed by the Egyptian Pharmacovigilance Center. The EDA notes that contact details are requested so the centre can follow up, and that the identities of reporter and patient are kept confidential. A PSP should not replace a patient's own right to report; it should tell patients this route exists and respect their choice.

Common gaps to check

• Staff treat adherence calls as logistics and do not log symptoms mentioned in passing.
• Notes are kept only in free text in a CRM and never reach pharmacovigilance.
• Staff try to reassure patients by saying a symptom is probably unrelated, which is interpretation.
• Reports lack the four minimum elements and nobody follows up.
• Subcontracted call centres or nurses are not covered by the same training and contract wording.

Measuring the process

Track process indicators rather than patient outcomes: the share of staff with current pharmacovigilance training, the time from first awareness to forwarding, the share of reports that are complete on first submission, and the result of each reconciliation. Report aggregated figures only, and read this alongside our guide on patient support programme KPIs.

How Hospitalia can help

Hospitalia is an Egypt-based integrated home healthcare and corporate medical services platform. Its patient support services cover onboarding, education, follow-up and care coordination. Responsibility for causality assessment and regulatory reporting stays with the product owner; the programme scope, forwarding channel and timelines are agreed with each client in writing before launch.