Patient Support Program for a Pharma Launch in Saudi Arabia: The First 90 Days

Short answer: A patient support program for a pharma launch in Saudi Arabia should be designed before the first prescription, not after it. The launch-ready version has a defined enrolment route, recorded consent, a first-contact standard, a safety-reporting path, clear data roles and a 90-day review rhythm. The first 90 days are for finding where patients stall and fixing it fast.

Why the first 90 days matter

Launch teams often treat patient support as something to switch on once the product is moving. IQVIA's launch guidance argues the opposite: patient engagement and support should run before, during and after launch, begin from day one, and anticipate barriers such as self-administration burden, side effects and administrative or financial obstacles. The same piece describes the first six months after launch as a strong bellwether of a product's likely success (IQVIA, Powering launch excellence with patient engagement and support, 2024). It is an industry publication and a global one, so treat it as a planning frame and not as Saudi evidence.

For a Saudi launch, the argument is practical. New therapies often enter through a small number of hospitals, prescriber groups and pharmacies. Patients may be new to self-injection, new to a specialist, and unsure what happens between the prescription and the first dose. Each stall is a place where a program either helps or fails to notice.

Five decisions to lock before day one

1. Enrolment route. Who enrols the patient: the prescriber's team, the hospital pharmacist, the patient directly or a nurse educator? Each route needs a form, an owner and a target time.
2. Consent. How is consent captured, in Arabic and English, for which purposes, and how can the patient withdraw? Review with your data-protection adviser against current Saudi requirements . Our article on digital PSP enrolment and consent under PDPL covers the principles.
3. First contact standard. Define who calls or messages the patient after enrolment and within what time. Write it down as a service level so you can report it.
4. Safety information. Define how adverse events or product complaints that surface through the program are captured and passed to pharmacovigilance within the timelines your safety team requires . See adverse event reporting in digital PSPs.
5. Data roles. Decide who is controller, who processes, what the sponsor sees (usually aggregate and de-identified) and what the vendor contract says about data quality. Our guide to PSP data quality checks lists six checks to include.

A 90-day plan in four windows

Before launch (about 60 to 90 days out). Map the likely patient journey from prescription to first dose to the first refill. Mark where patients commonly stall: prior approval, pharmacy availability, injection training, travel to a clinic. Build Arabic and English education content, train the enrolment team, test the consent flow with real forms, and agree the reporting definitions.

Days 1 to 30: open and observe. Launch with a small number of sites. Review enrolment funnel counts weekly: referrals received, consent recorded, first contact made, first dose supported. Look for the stage with the largest drop. Do not scale to new sites until the first-contact standard is being met.

Days 31 to 60: fix and extend. Resolve the top two friction points found in the first month. Add sites in waves. Check that every report uses the same definitions of "enrolled" and "active". If the definitions are loose, the 90-day figures will not be comparable. Our article on PSP sponsor reporting definitions and denominators explains why this matters.

Days 61 to 90: review and decide. Hold one structured review with the brand, medical, safety and vendor teams. Agree what the data shows, what it cannot show, and what changes for the next quarter.

A 90-day scorecard that stays honest

Report operational signals, each with a clear numerator and denominator:

• Referrals received and share with a completed enrolment form.
• Share with recorded consent.
• Median time from enrolment to first contact.
• Share reaching the first dose with program support recorded.
• Share of patients inactive for more than a set number of days, and the stage at which they stopped.
• Number of safety reports passed to pharmacovigilance and the share within timeline.

Resist turning these into claims. Early drop-off figures say where the process loses people, not why the medicine works or does not. Any statement about adherence, persistence or clinical outcomes needs clinical and medical-affairs review first . Our article on PSP KPIs for enrolment, activation and retention shows how to define each measure.

An illustrative scenario

This is a planning scenario, not a customer case. A sponsor launches a self-injected biologic through three specialist hospitals in Riyadh and Jeddah. Before launch, the team maps the journey and finds that the most likely stall is between the first clinic visit and the first injection: the patient has to arrange training, collect the medicine from a hospital pharmacy and understand a storage instruction.

The program assigns a nurse educator to call every enrolled patient within a defined time of consent, send Arabic injection-training content, and confirm the pharmacy collection date. In the first 30 days, the weekly funnel shows enrolments are completing but most patients who stop do so before the pharmacy step. The team adds a pharmacy-collection reminder and a named hospital contact. The 90-day review reports the change as an operational improvement in the funnel, not as a clinical result.

Where PSP Connect fits

CareSync PSP Connect is built for pharma patient support programmes: enrolment, consent capture, patient communication, educator workflows and sponsor reporting in one platform. The exact modules, timelines and integrations available for a given launch should be scoped with the product team . If you are selecting a platform for a launch, start with the PSP evaluation checklist and the biologics digital onboarding guide.

FAQ

When should a pharma company plan a patient support program for a launch?

Before launch. Planning ahead lets the team map patient barriers, build the enrolment and consent flow, train staff and agree reporting definitions so the program can support patients from the first prescription.

What should a launch PSP decide before day one?

Who enrols patients, how consent is recorded, who makes first contact and how quickly, how safety information is captured and passed on, and who controls the data. These are the five decisions that are hardest to fix once patients are enrolled.

What should a PSP measure in the first 90 days?

Operational signals: referrals received, consent recorded, time to first contact, enrolments completed, drop-off stage and safety reports passed on. Define each with a numerator and denominator and avoid presenting them as clinical outcomes.

How do you handle adverse events reported through a patient support program?

Capture them in a defined workflow and pass them to the sponsor's pharmacovigilance team within the timelines that team requires. Confirm responsibilities and timelines with your safety team and current SFDA guidance.

Can early PSP data prove the medicine is working?

No. Early program data shows how well the enrolment and support process works. Claims about adherence or clinical outcomes need clinical and medical-affairs review and appropriately designed evidence.

---