On-site corporate medical services•Pre-employment medical assessments•Annual employee health check-ups•Workplace vaccination programs•Occupational health evaluations•Chronic disease management•Home nursing care•Post-surgery home care•Doctor home visits•Physiotherapy at home•Elderly home care•Lab tests at home•ECG, echo & X-ray at home•Patient Support Programs (PSP)•Medication delivery & adherence follow-up•School medical services & student check-ups•Digital health & tailored health technology•White-label digital health platforms•
Patient Support

Patient Journey Mapping for a Patient Support Program in Egypt: A Step-by-Step Guide

Updated: 20 min readHospitalia Editorial Team
Illustrative patient support care team discussing a program

Quick answer

A practical guide for pharma patient-access, PSP and medical teams: how to map a patient support program from referral to follow-up, find where patients stall or stop, assign ownership of every handover, and build consent, privacy and Arabic-language needs into the map.

A patient journey map for a patient support program (PSP) is a one-page picture, built with the people who run the program, that shows each step from referral to a stable follow-up routine, where patients can stall or stop, and who owns every handover. In Egypt, build it around consent, Arabic-language contact and the treating team's role.

What a PSP journey map is, and what it is not

Patient journey mapping, in a PSP, is the practice of documenting each step a patient takes from being referred to a program until they are settled on therapy or leave the program, and recording the contact, the owner, the information passed on and the friction at each step. The result is a shared picture that the pharma team, the PSP operator and, where possible, the treating team can look at together.

It helps to be clear about what the map is not:

  • It is not a marketing funnel. A funnel counts how many people move forward. A journey map asks why a person did not, and who was responsible for the step where they stalled.
  • It is not a clinical pathway. The treating clinician decides diagnosis, prescription and treatment. The map covers the support around that care, and it should show clearly where PSP staff stop and the clinician starts.
  • It is not the program design document. A design document says how the program is meant to work. A journey map records how it works now, including the workarounds that staff use and the steps that were never written down.
  • It is not a one-off exercise. Programs change, therapies change and staff change. A map that is not revisited becomes a poster.

The best maps are short enough to read in a few minutes and specific enough to act on. A map that has forty boxes and no owners is a diagram. A map that has seven stages, named owners and three marked friction points is a management tool.

Why mapping matters: what the adherence evidence says

PSPs exist because starting and staying on a prescribed therapy is difficult for many patients. The WHO report Adherence to long-term therapies: evidence for action (2003) states that in developed countries adherence to long-term therapies in the general population is around 50%, and that it is much lower in developing countries. It describes adherence as a multidimensional phenomenon determined by the interplay of five sets of factors, and a WHO news item from 1 July 2003 adds that improving adherence may well result in better health outcomes than making available new technologies. These are international figures from 2003. They are not Egyptian data, and they should not be quoted as the adherence rate for any Egyptian therapy.

Two other sources shape how a PSP should think about the map. NICE's guideline on medicines adherence (CG76, parts of which have since been replaced by later NICE guidance on medicines optimisation) defines adherence as the extent to which the patient's action matches the agreed recommendations, says that non-adherence should not be seen as the patient's problem, and recommends recognising that non-adherence is common and that most patients are non-adherent sometimes. It also advises asking patients what they know, believe and understand about medicines before prescribing new treatments. The practical consequence for a PSP is that each contact is an opportunity to understand a patient's barriers, not to assign blame.

The Cochrane review of interventions for enhancing medication adherence (Nieuwlaat and colleagues, 2014) is a useful caution. It found that the characteristics and effects of interventions varied among studies, that effects were inconsistent from study to study, and that only a minority of the lowest-risk-of-bias randomised trials improved both adherence and clinical outcomes. NICE similarly notes that although adherence can be improved, no specific intervention can be recommended for all patients. Mapping does not guarantee better adherence. What it does is show you where your own program loses people, so you can test changes where they matter instead of adding contacts everywhere.

The adherence taxonomy published by Vrijens and colleagues in the British Journal of Clinical Pharmacology (2012) is especially useful for mapping, because it divides adherence into three phases. Initiation occurs when the patient takes the first dose of a prescribed medication. Implementation is the extent to which the patient's actual dosing corresponds to the prescribed dosing regimen, from initiation until the last dose. Discontinuation occurs when the patient stops taking the prescribed medication, for whatever reason. These three phases map directly onto the three kinds of drop-off described later in this guide.

The seven stages of a PSP journey

Every program is different, so treat the stages below as a starting structure to adapt, not a standard. Industry sources describe similar stage models: an IQVIA article from February 2026 identifies access and affordability, treatment initiation and ongoing support as the stages where patients are most at risk, and a vendor guide from Courier Health describes six stages from awareness to post-treatment. Both are industry sources written largely for the US market, so use them for vocabulary and not as evidence about Egypt. The seven stages below are our own working structure.

StageWhat happensTypical frictionSuggested ownerWhat to capture
1. ReferralA treating clinician, pharmacist or patient refers into the programReferral form incomplete; patient does not know the program exists; referral sits in an inboxPSP intake coordinatorDate received, source, completeness, time to first contact attempt
2. Consent and enrolmentPatient receives an explanation, gives consent for specific purposes and is enrolledConsent explained in jargon; caregiver signs but patient is unaware; patient hesitates and is not recontactedPSP coordinatorConsent type, language used, date, withdrawal route given
3. Onboarding and first contactWelcome contact, contact preferences agreed, education plan set, expectations explainedWrong phone number; contact time clashes with work; patient expects services the program does not offerPSP coordinator and educatorPreferred channel, preferred time, caregiver details with permission
4. Access and startPrescription, pharmacy or supply arrangements, first dose or first visitPatient has a prescription but cannot find the product or does not know how to start; first visit not scheduledTreating team and supplier; PSP coordinates the informationDate of first dose or visit as reported, and who confirmed it
5. Early follow-upFirst weeks of support: check that the patient knows what to do and can manage practicalitiesFirst follow-up call missed; early side-effect worries not routed; patient stops without telling anyonePSP educator or nurseContact made or not, questions raised, issues routed, safety information forwarded
6. Ongoing supportScheduled education, reminders if agreed, practical problem-solvingContact fatigue; messages in the wrong language; refills and appointments driftPSP teamContact outcomes, barriers recorded in agreed categories
7. Review, transition or exitPeriodic review; transfer to routine care, program closure or patient withdrawalPatient leaves without a handover; the treating team is not toldPSP coordinator with the treating teamReason for exit as stated, handover note sent, final contact
A seven-stage PSP journey: what happens, where it stalls, who owns it

The stages map onto the Vrijens phases. Stages 1 to 4 are about initiation: did the patient start? Stages 5 and 6 are about implementation: is the patient following the plan as agreed? Stage 7, and any unplanned exit during stages 5 and 6, relates to discontinuation. Keeping this mapping in view stops the team from treating all drop-off as one problem.

How to run the mapping workshop in six steps

NHS Improving Quality's guide to service improvement describes process mapping as a technique used to identify all the interconnected pathway steps and decisions in a process and to turn this information into a highly visual diagram. NHS Lothian's quality improvement guidance adds that mapping should show everyone in a team how a process works in practice now, rather than what they think is happening, and that it should involve all team members in accurately capturing the current process. Those principles translate well to PSPs. A half-day workshop is usually enough for a first map.

  1. Prepare. Agree the objective, such as understanding where patients are lost between referral and the first follow-up call. Agree the scope: one therapy, one referral route, one region. A map of everything is a map of nothing. Collect the documents you already have: the program design, scripts, forms, approved materials and any activity reports.
  2. Invite the people who actually do the work. Include the intake coordinator, the educator or nurse, the person who answers the phone, someone from the pharma team who owns the program, a representative of the supplier or pharmacy route if there is one, and, if you can arrange it with consent and care, a treating clinician. Include at least one person who speaks to patients in Arabic every day. Do not run the workshop with managers only.
  3. Set ground rules. The purpose is to understand the process, not to blame people. Agree that nobody in the room will be criticised for describing a workaround, because the workarounds are where the information is. Agree that no patient identifiers will be used in the room.
  4. Map the current state. Agree the start and end points, and start at a high level before adding detail. Walk the seven stages, or your adapted version, and for each ask: what triggers this step, what happens, who does it, what information is passed on, what is recorded and where, and what happens if it does not happen.
  5. Mark the friction. Use a visible marker for delays, duplicated work, handovers with no owner, places where a patient has to repeat information, and steps that depend on one person. Ask the team where they believe patients stall or stop, and ask what evidence supports that belief.
  6. Check and agree next steps. Send the map back to the participants within a few days and ask them to correct it. Agree which two or three friction points will be examined first, who will look at them, and when the map will be reviewed.

Questions to ask at each touchpoint

  • What does the patient know at this point, and how do we know?
  • What does the patient need to do next, and who has told them?
  • What channel did we use, and was it one the patient chose?
  • What language, dialect and level of explanation did we use?
  • Who else is involved: a caregiver, a pharmacist, a nurse, a clinician?
  • What do we record, who can see it, and for what purpose?
  • What is the longest time a patient can wait at this step, and who notices when that is exceeded?
  • What happens if the patient says they are worried about a side effect or wants to stop?

Marking the drop-off points

The three adherence phases from Vrijens and colleagues help separate drop-off into three types. Each has different signals, different causes and different owners.

TypeWhat it meansSignals you may observeCommon causes to exploreWho usually owns the response
Never started (initiation gap)The patient was referred or enrolled but did not begin therapy or the first visitEnrolled with no confirmed start; first visit never booked; no response to the first contactsUnclear next step; cost or supply concern; fear or doubt; prescription not collected; wrong contact detailsPSP coordinator with the treating team
Partial use (implementation gap)The patient started but does not follow the agreed plan consistentlyMissed appointments; late refills where the program can see them; patient-reported missed doses; repeated confusion about instructionsComplex regimen; side-effect worry; forgetting; costs; family or work routine; misunderstandings about why the treatment mattersPSP educator or nurse, routing clinical questions to the treating team
Stopped (discontinuation)The patient stops taking the prescribed treatment, for whatever reasonPatient tells the team; contacts stop; refills stop; patient withdraws from the programSide effects; a perceived lack of benefit; a decision by the clinician; cost; loss of trust; moving or travellingTreating team for clinical reasons; PSP for support and information
Three kinds of drop-off and how to look for them

Two cautions apply. First, be honest about what the program can see. A PSP usually knows about contact outcomes and what patients report. It may not know whether a patient took a dose. Label patient-reported information as patient-reported, and do not present it as verified treatment use. Second, a stopped patient is not always a failure of the program. A clinician may have changed or stopped the treatment for good clinical reasons, and the PSP's job in that case is to close the loop cleanly, not to chase.

Ownership and handovers

Most journey friction sits at handovers: the moment one person or organisation passes a patient to another. In a PSP there are at least six. For each, the map should name the sender, the receiver, what must be passed, and the failure sign that tells you the handover has failed. Our guide to PSP referral handover goes deeper into the first of these.

HandoverFromToWhat must be passedFailure sign to watch
Referral to intakeTreating team, pharmacist or patientPSP intake coordinatorEligibility information, patient contact details with permission, treating team contactReferral with no first contact attempt after the agreed time
Intake to consent and enrolmentIntake coordinatorPSP coordinatorReferral record, patient's preferred language and contact routePatient contacted twice with the same questions
Enrolment to educator or nursePSP coordinatorPSP educator or nurseConsent scope, education plan, contact preferences, caregiver permissionsEducator does not know what the patient consented to
PSP to treating team (clinical question)Educator or nurseTreating clinicianThe question in the patient's words, relevant context, urgencyQuestion sits unanswered; patient told to wait without a route
Safety information to pharmacovigilanceAny PSP staff memberSponsor's designated safety contactSuspected adverse event or product complaint, as reported, within agreed timelinesEvent noted in a call record but not forwarded
Exit or transitionPSP coordinatorTreating team and patientReason for exit as stated, last contact, any open questionsPatient leaves and the treating team is not told
Six PSP handovers: owner, content and failure sign

A journey map that ignores consent and language will describe a program that works on paper. Build both into each stage.

  • Record consent by purpose, not as one blanket tick: contact by phone, contact by messaging, sharing information with the treating team, sharing aggregated information with the sponsor. Note how the patient can withdraw and who tells them.
  • Collect the minimum data each stage needs. If a step does not need a diagnosis, do not ask for one. Small patient groups can be identifiable even in summary reports, so decide report thresholds in advance.
  • Show the consent scope to every person who uses it. An educator who does not know what the patient agreed to will either over-share or under-serve.
  • Check legal requirements with qualified advisers. In an unofficial English compilation of Egypt's Personal Data Protection Law No. 151 of 2020 that we opened, health data is listed among sensitive data, sensitive data requires written and explicit consent, consent can be withdrawn, and transfer of personal data abroad is restricted. We could not verify this against an official source or the Arabic text, and it is not legal advice. Your legal team should confirm how the law applies to your program.

Arabic-language and accessibility needs

  • Plan contacts in the patient's own register of Arabic. Modern Standard Arabic suits written materials, but many patients are more comfortable in spoken Egyptian Arabic. Scripts should sound like a person, not a leaflet.
  • Assume mixed literacy and health literacy. Use short sentences, one idea at a time, and confirm understanding with a gentle question such as asking the patient to explain in their own words what they will do next.
  • Ask for channel and time preferences at onboarding, and respect them. A call at midday may be impossible for a patient who works shifts. A message may be seen by other family members, so check before sending anything that reveals a condition.
  • Include caregivers, with the patient's permission. Many patients, especially older adults and parents of children, rely on a family member for practical tasks. Record who can be contacted and for what.
  • Use approved materials only, and keep versions under control. Our guides to reminder messages and education material version control cover this.

The clinical and safety boundary

The map should show, at every stage where a patient might raise a clinical concern, where PSP staff stop and the clinician starts. PSP staff do not diagnose, prescribe, change doses or advise on missed doses. They listen, record, provide approved information and route the question to the treating team.

  • Suspected side effects and product complaints go to the sponsor's designated safety contact through the agreed route, within agreed timelines. Capture them whenever they are mentioned, even in a call about something else.
  • Urgent symptoms need urgent care, not a call-back from a support program. Scripts should tell the patient to contact emergency services or their clinician immediately, and staff should know exactly what to say.
  • Dosing questions, symptom questions and decisions to stop treatment go to the treating clinician. The PSP can help the patient prepare the question and book the contact, but it does not answer it.

From map to action

A map is useful only if it changes something. After the workshop, resist the urge to fix everything. Choose two or three friction points using three questions: how many patients does this affect, how early in the journey does it happen, and can we change it without changing the clinical protocol? Early stages are often the best place to start, because a patient lost at initiation never reaches the later stages.

For each chosen friction point, write a short test: what we will change, who owns it, how long we will try it, and what we will look at to judge whether it helped. Keep the change small. A different time for the first follow-up call, a clearer consent explanation, or a named owner for unreturned referrals are all changes that can be tested within weeks.

Choose a small scorecard of process measures and review it monthly. Examples are time from referral to first contact attempt, proportion of enrolled patients reached for the first follow-up, number of clinical questions routed and answered within the agreed time, and proportion of exits with a handover note. These are process measures. Our guide to PSP key performance indicators discusses how to define them and what not to claim.

A fill-in template

Use this table as the working surface of your workshop. Print it large, or draw it on a wall. Add rows for each distinct touchpoint, and leave cells blank rather than guess.

StageTouchpointChannel and languageOwnerWhat the patient needs to know or doFriction observedWhat we recordAction to test
ReferralReferral receivedForm or call; ArabicIntake coordinatorThat the program will contact themIncomplete referral formsDate, source, completenessRequired fields on the form
Consent and enrolmentConsent conversationPhone or visit; Egyptian Arabic, plain termsPSP coordinatorWhat they agree to, and how to withdrawConsent read out too fastConsent by purpose, dateShorter, plainer script
OnboardingWelcome contactPatient's preferred channel and timeCoordinator and educatorWhat the program does and does not doWrong time of dayPreferred time, caregiver detailsAsk the preferred time first
Access and startStart confirmationPhone or messageTreating team, with PSP supportHow and when to startUnclear next stepStart reported, by whomA one-page next-step sheet
Early follow-upFirst follow-up callPhone; ArabicEducator or nurseWho to call with a worryCall missed, not repeatedContact outcome, questions routedSecond attempt at a different time
Ongoing supportScheduled contactAgreed channelPSP teamHow to prepare questions for the clinicianContact fatigueBarriers in agreed categoriesReduce contact where not needed
Review or exitClosing contactPhone; ArabicCoordinatorWhat happens nextTreating team not toldReason for exit, handover sentStandard handover note
PSP journey map: working template

Common mistakes

  • Mapping the design instead of the practice. If nobody in the room admits to a workaround, the map is probably fiction.
  • Leaving out the people who talk to patients. Managers know the policy; coordinators and educators know the reality.
  • Starting too wide. One therapy and one referral route are enough for a first map.
  • Treating every drop-off as non-adherence. Never started, partial use and stopped are different problems, and some stops are a clinical decision.
  • Counting contacts as success. More calls are not better care. Ask whether the contact changed what the patient knew or did.
  • Forgetting consent. A map without consent scope will produce a program that contacts people it should not, or fails to contact people it could.
  • Ignoring language. A journey that works in English slides may fail in the first Arabic phone call.
  • Assigning handovers to a team rather than a person. A handover owned by a team is owned by nobody.
  • Claiming outcomes. A map can reveal friction. It cannot promise adherence, persistence or clinical benefit.

Two illustrative scenarios

These scenarios are illustrative. They are not real programs, clients or patients, and they use no real product names.

A PSP for a long-term injectable therapy has been running for several months. The pharma team notices that many referred patients are never enrolled, and assumes patients are not interested. The PSP convenes a half-day workshop with the intake coordinator, two educators, the phone team lead and a medical representative. They map the first three stages.

The map shows two things nobody had written down. First, the first contact attempt is often made in the afternoon, when many referred patients are at work, and a failed attempt is rarely repeated. Second, the consent conversation is read from a form that uses formal Arabic and several terms patients do not use, so some patients agree without understanding and others hesitate and are not recontacted. The team chooses two changes to test for six weeks: a second contact attempt in the evening, and a shorter consent explanation in plain Egyptian Arabic, with the formal wording kept in writing. They track time to first contact and the proportion of referrals reaching enrolment. They do not announce a result in advance. They report what they see, and they note that other factors, such as referral quality, also changed during the test.

Scenario 2: early follow-up for an oral long-term therapy

A program supports adults starting an oral long-term therapy. Patients are enrolled and receive a welcome call, then nothing is scheduled for several weeks. A few patients tell the educator, at the next contact, that they stopped after a short time because they were worried about a symptom and did not know whom to ask.

The map highlights stage 5. There is no early follow-up contact, and no clear route for a patient worried about a symptom. The team adds a short follow-up call in the first weeks, to check that the patient understands what to do and knows whom to call with a worry. The call script does not give medical advice. It tells the patient to contact their clinician for symptoms, and routes any suspected side effect through the agreed safety pathway. The team reviews, after a quarter, how many patients were reached, how many questions were routed, and how many were answered by the treating team within the agreed time. It does not claim any effect on how long patients stay on therapy.

How to judge whether the map is working

A map is working if it changes decisions. Review it quarterly with the same group and ask four things: did we fix the friction points we chose, did the process measures move in the direction we expected, did new friction appear, and are the owners still right? If the map has not changed in six months, either the program is remarkably stable or nobody is looking.

Be careful about the claims you make from it. A change in a process measure shows that a process changed. It does not show that patients are healthier, and many factors can move the numbers at the same time. Report what you observed, say what you do not know, and leave outcome claims to studies designed to examine them.

How Hospitalia can support your program

Hospitalia's Patient Support services cover onboarding, education, follow-up and care coordination for pharma programs in Egypt. If you are mapping a program, Hospitalia can take part in the planning conversation, help define who owns each step and each handover, and discuss how education, adherence support or clinically suitable home visits fit into the journey as separate, scoped modules. Scope, coverage, staffing, service hours and fees are confirmed in a proposal after that conversation.

Hospitalia delivers support services. It does not prescribe, diagnose or change treatment, it is not an insurer or an emergency service, and no program can guarantee treatment access, adherence or clinical outcomes. Responsibilities for consent, safety reporting and data access are agreed with the sponsor and documented before enrolment starts.

Plan a patient support program journey that is mapped, owned and consent-led. Call 01063151838 or send an enquiry through the website.
Discuss a patient support program

Frequently asked questions

What is patient journey mapping in a patient support program?

It is the practice of documenting each step a patient takes from referral to a stable follow-up routine or exit, and recording the contact, owner, information passed on and friction at each step, so the team can see where patients stall or stop.

Why is the patient journey important for a PSP?

Because starting and staying on a prescribed therapy is difficult for many patients, and the places where patients are lost are often handovers and early steps that nobody owns. A map makes those places visible. It does not guarantee better adherence.

How do you do patient journey mapping?

Choose one therapy and one referral route, invite the people who do the work, agree ground rules, map the current state step by step, mark the friction, check the map with participants, and choose two or three friction points to test. A half-day workshop is usually enough for a first map.

What is the purpose of journey mapping?

To show everyone how the process works in practice now, rather than what they think is happening, and to find where to make small, testable changes. It is a management tool and not a marketing funnel.

What is a patient support program?

A structured, scoped service that helps eligible patients move through an agreed care pathway, for example through enrolment, approved education and coordination, while the treating team keeps responsibility for treatment.

How do patient support programs work?

A patient is referred, consents to participate, is onboarded, receives agreed education and follow-up, and is referred back to the treating team for clinical questions. Safety information is routed to the sponsor's designated safety contact. The exact services depend on the program.

Where do patients usually drop out of a PSP?

Common points are between referral and first contact, between enrolment and starting therapy, and in the early weeks after starting. Separate patients who never started, who use therapy partially and who stopped, because each needs a different response. Your own map will show your own pattern.

Can a journey map guarantee better adherence?

No. Reviews of adherence interventions find inconsistent effects, and few high-quality trials improved both adherence and clinical outcomes. A map helps you focus changes on your own friction points and track process measures, but it cannot promise outcomes.

Related tags
#patient journey map patient support program Egypt#patient journey mapping#patient journey map pharma#PSP drop-off points#patient support program touchpoints#patient journey coordinator#how to do patient journey mapping#PSP process mapping workshop

Related articles