Patient Support Programs for Chronic & Rare Disease Therapies in Egypt: Designing by Therapy Area
Quick answer
Most PSP content treats patient support as one generic model. Therapy area changes almost everything — from whether adherence or patient identification is the first problem to solve, to what a nurse actually does on a visit.
Almost every article written about patient support programs describes a single generic model: enroll the patient, educate them, call them, report on adherence. That model is not wrong, but it is an average of three very different things — and averages are a poor basis for designing a program that has to work for a specific therapy in a specific market.
In practice, a PSP for a chronic oral therapy, a PSP for a specialty biologic, and a PSP for a rare disease launch share a reporting backbone and almost nothing else. The staffing profile differs, the first problem to solve differs, the unit economics differ, and — most importantly for anyone briefing a partner — the definition of success differs. This guide sets out how to design each, and what stays constant across all three.
Chronic disease programs — support at scale, over years
For diabetes, cardiovascular disease, and the large autoimmune indications, the defining characteristics are duration and volume. Patients stay on therapy for years, the cohort is large, and the risk is not a dramatic failure but a slow, silent drift off treatment that nobody notices until an HbA1c or a lipid panel comes back wrong.
- Long-duration adherence tracking: the program has to still be meaningfully engaged with the patient at month 18, not just month two, which means follow-up cadence must be designed to survive fatigue on both sides.
- Refill and appointment reminders at scale: low-touch, high-frequency contact where efficiency and consistency matter more than clinical depth on any single call.
- Self-administration and lifestyle education: injection technique for self-injected therapies, plus the practical guidance around diet, activity, and symptom monitoring that determines whether a patient feels in control of their condition.
- Caregiver involvement: in Egyptian households, an elderly patient's regimen frequently depends on a family member who changes over time — a program that only ever speaks to the patient loses continuity when that happens.
- Recurring low-touch follow-up: cost per patient must stay low enough to be sustainable across thousands of patients for several years, which pushes the design toward structured contact-centre work with nursing reserved for defined needs.
Biologic and specialty therapy programs — a clinical delivery model
Once the therapy is a nurse-administered injection or an infusion, the program stops being a coordination exercise and becomes a clinical operation. The centre of gravity moves from the call centre to the home visit.
- Home injection and infusion logistics: scheduling qualified nurses around each patient's dosing cycle, with the travel and coverage planning that implies outside major cities.
- Cold-chain handling considerations: therapies with temperature requirements need defined handling and verification steps before administration, and nurses trained to recognise when a dose should not be given.
- Closer nurse–patient relationships: patients on specialty therapy see the same clinical professional repeatedly, and that continuity is one of the strongest predictors of whether they stay on treatment.
- More intensive early-treatment monitoring: the first weeks carry the highest discontinuation risk — early side effects, infusion reactions, and injection anxiety all peak before the patient has any evidence the therapy is working.
- Tighter integration with the prescriber: a specialty program that cannot get information back to the treating physician quickly is a program that generates escalations nobody acts on.
Chronic, specialty biologic, and rare disease programs need different designs. Tell us the therapy and we will scope the model around it.
Talk to the clinical teamRare disease programs — identification is the first challenge, not adherence
This is where most generic PSP thinking breaks down entirely. In a rare disease launch, you do not begin with a cohort of patients who need support. You begin with the near-certainty that eligible patients exist, are scattered across the country, and are largely undiagnosed, misdiagnosed, or known only to a handful of specialists who may never have had a therapy to refer them toward.
Our team's direct experience includes mapping the Egypt and Saudi markets for rare disease patient identification, including leading pre-launch activities for a first-in-category gene therapy for Dystrophic Epidermolysis Bullosa. That work was not nursing logistics. It was physician mapping, referral-pathway construction, and education delivered to clinicians who needed to recognise a presentation they had rarely been able to act on.
- Physician and centre mapping: identifying which specialists, in which governorates, plausibly see these patients — often dermatology, genetics, paediatrics, and tertiary referral centres rather than any single obvious specialty.
- Referral pathway construction: building the route from suspicion to diagnosis to treatment centre before enrollment can exist, because a patient nobody can refer is a patient no program can support.
- Clinician education as a pre-launch activity: medical-science-liaison-style groundwork, delivered credibly, because the goal is diagnostic recognition rather than product promotion.
- Family and caregiver navigation: rare disease families frequently arrive after years of diagnostic odyssey, and the support they need starts with orientation and expectation-setting, not adherence prompts.
- Small-cohort, high-intensity economics: a rare disease program may serve dozens of patients, not thousands, with far more clinical and coordination time per patient — per-patient benchmarks from chronic programs are meaningless here.
The practical implication for a brand or medical affairs lead is a sequencing one. If you scope a rare disease PSP as a support program, you will be ready to serve patients who have not been found yet. Scope it as an identification program that becomes a support program, and the same budget produces enrollments.
What stays constant across all three — the reporting backbone
Therapy area changes the front end of the program almost completely. It does not change what a sponsor needs to see, or the operational discipline that makes any of it defensible.
| Constant | What it means in practice | Why it holds regardless of therapy |
|---|---|---|
| 24-hour referral response | Every referral receives a first contact within one working day | The gap between referral and first contact is where patients are lost in every therapy area |
| Monthly KPI pack | Referral-to-contact time, visit completion, adherence, escalation volume | Sponsors cannot defend a program internally on anecdote, whatever the indication |
| Safety / PV-aligned reporting | Defined capture and escalation pathway for adverse events | A non-negotiable obligation for any pharma-sponsored program |
| Bilingual patient education | Arabic-first materials and conversations, English where needed | Comprehension is the precondition for every other outcome the program targets |
| Named point of contact | The patient and family know exactly who to call | Discontinuation frequently begins with an unanswered question |
These are the six-module foundation described on our patient support page, and they are the part of a program that should look the same whether you are running a diabetes cohort of two thousand or a rare disease cohort of twenty.
A therapy-area fit checklist for pharma teams
Before briefing any PSP partner, answer these six questions. The answers determine which of the three models above you are actually buying.
- Expected patient population size: thousands, hundreds, or dozens? This single answer determines whether you need scale economics or intensity.
- Treatment complexity: oral, self-injected, nurse-administered, or infusion — and does administration require cold-chain handling?
- Home-administration requirement: must the therapy be delivered at home, or is home delivery an adherence improvement rather than a necessity?
- Referral network needs: do referring physicians already exist and know to refer, or does the pathway have to be built first?
- Data and reporting obligations to global HQ: what does headquarters require, in what format, and does any of it need to reconcile with a global PSP dataset?
- Risk window: when in the treatment journey is discontinuation most likely, and does the proposed program concentrate its effort there?
See the six modules that form the backbone of every Hospitalia-managed patient support program, then tell us where your therapy needs something different.
Explore patient support programsFrequently asked questions
Can one PSP partner run programs across multiple therapy areas at the same time?
Yes, provided the partner treats them as separate operational designs rather than one template applied three times. What can legitimately be shared is the backbone: referral intake, the 24-hour response standard, reporting infrastructure, safety escalation pathways, and the nurse network itself. What must differ is the visit model, the follow-up cadence, the education content, and the staffing intensity per patient. When evaluating a partner, ask them to describe two of their programs in different therapy areas and listen for whether the operational details actually differ.
How does patient identification work for a newly launched rare disease therapy?
It starts well before enrollment exists. The work involves mapping which specialists and referral centres plausibly see the condition — often across several specialties and multiple governorates — then delivering clinician education focused on diagnostic recognition rather than product messaging, and building a practical referral route from suspicion through to a treating centre. Only once that pathway functions does the support program have patients to support. Budgeting an identification phase separately from the support phase is the most common structural fix we recommend to rare disease brand teams.
What is operationally different about a program for an injectable versus an oral therapy?
An oral therapy program is built around coordination and education: enrollment, adherence follow-up, refill support, and reporting. An injectable program adds a clinical delivery layer — a qualified nurse attending the patient's home on a dosing schedule, technique and safety checks, cold-chain handling where required, and a post-administration monitoring window. That layer changes the staffing model, the geographic planning, the cost base, and the escalation pathway. It also tends to produce stronger adherence, because removing the travel burden for an injectable therapy addresses the most common practical reason patients stop.
