Consent and Privacy in Patient Support Programmes in Egypt: A Practical Guide

Short answer: a patient support programme (PSP) in Egypt should treat consent as a designed process, not a signature. Patients need to understand in plain Arabic what data is collected, why, who sees it and how to withdraw. Egypt's Personal Data Protection Law (Law No. 151 of 2020) treats data revealing physical, mental or genetic health as sensitive and requires explicit consent unless the law authorises otherwise. This guide is an operational overview, not legal advice; consent wording, legal basis and data flows must be approved by qualified legal, privacy, medical and pharmacovigilance reviewers before use.

• Law No. 151 of 2020 defines sensitive personal data to include data that reveals mental, psychological, physical or genetic health, so PSP enrolment data is likely to fall within it. Confirm applicability with your legal adviser.
• Article 2 of the law gives data subjects rights that include being informed of, accessing and obtaining their personal data and withdrawing prior consent for its retention or processing.
• For sensitive data the text we reviewed (Article 12) points to a licence from the Personal Data Protection Center and, unless the law expressly permits otherwise, written and explicit consent. Which route applies to a given programme is a legal determination.
• We have not verified the current status of the executive regulations or Center licensing procedures, so confirm the latest position before launch.
• Consent for the support service is separate from any safety reporting duty: if a patient reports a possible side effect, route it through the sponsor's approved pharmacovigilance process regardless of marketing consent choices.

Why consent design matters in a PSP

A PSP typically collects identity, contact details, diagnosis or treatment information and call or visit notes. Patients are often anxious or newly diagnosed, may have limited health or digital literacy, and may be asked to consent on a phone call or through a nurse. Poorly designed consent erodes trust and may leave the programme without a valid basis for the data it holds. Good design is also practical: a clear consent makes it easier for coordinators to know what they can do next.

What the law text says, in brief

From our reading of Law No. 151 of 2020: Article 1 defines sensitive personal data to include health data; Article 2 sets out data subject rights, including to be informed, to access their data and to withdraw prior consent; Article 12 addresses processing of sensitive data and refers to a licence from the Center and to written, explicit consent unless the law expressly permits otherwise; and Article 19 establishes the Personal Data Protection Center as the authority. This is a summary from the law's English translation for orientation only. Do not rely on it for decisions; obtain Egyptian legal advice, including on the executive regulations and any sector-specific rules for pharmaceutical companies and health data.

Designing the consent journey

1. Separate the purposes

List each purpose separately: enrolment in the support service, nurse or educator contact, reminders, sharing information with the treating doctor, and any optional research or feedback use. Avoid one bundled consent for everything. Patient support must not be mixed with promotion; any marketing use needs separate, explicit and legally approved handling, and patient data should never be repurposed for sales targeting.

2. Say it in plain Arabic

Write short, respectful consent text in clear Arabic at a reading level your audience can follow, and offer to read it aloud. Test the draft with a few non-specialist readers. Provide a copy the patient can keep. Do not promise outcomes or imply that support is a condition of treatment.

3. Tell patients what you collect and who sees it

State the categories of data, the organisations involved (sponsor, programme operator, nurse providers, platform vendors), whether any data leaves Egypt, how long it is kept and how to contact the programme about their data. If the sponsor receives only de-identified or aggregated reports, say so.

4. Make withdrawal simple

Explain how to withdraw consent, through the same channel used to give it, and what happens next, including that safety information already reported may still need to be retained as required by pharmacovigilance rules set by the sponsor's qualified staff. Check withdrawal text with legal and pharmacovigilance.

5. Record consent properly

Keep a record of what was agreed, when, by whom, in which version of the wording and through which channel. For verbal consent on a call, agree with legal whether and how it must be documented in writing. Audit samples regularly.

6. Minimise and protect data

Collect only what the service needs, restrict access by role, use secure systems, train coordinators on handling health data and agree incident response with the vendor. Contracts with vendors should define roles, instructions, subcontractors and return or deletion of data on exit; legal should review them.

Common pitfalls

• One long consent form that bundles support, marketing and research.
• Consent taken by a coordinator who cannot explain it, or without offering a copy.
• No version control, so nobody knows which wording a patient agreed to.
• Treating withdrawal as 'unsubscribe from calls' while data keeps flowing to other systems.
• Sharing identifiable data with sales or marketing teams.
• Launching before legal, privacy, medical and pharmacovigilance sign-off.

Measuring consent quality

Track aggregate, non-identifying indicators: the share of enrolments with a complete, correctly versioned consent record, the number of withdrawals and how quickly they were actioned, and patient feedback on whether the explanation was clear. Define the denominator and time window for each indicator, and avoid publishing small numbers that could identify patients. Our guide on patient support programme KPIs explains how to define metrics.

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. The scope of any programme, including consent, data flows, staffing and reporting, is defined with each sponsor and approved by their legal, medical and pharmacovigilance teams; Hospitalia does not give legal advice or promise outcomes.