A patient support program (PSP) is a set of manufacturer-funded services that helps patients start a prescribed therapy, afford it and stay on it. Services include enrollment, benefits and prior authorization help, financial assistance, nurse and adherence support, education and logistics.
PSPs matter most for specialty and newly launched therapies. Specialty drugs made up 50% of US drug spending in 2021, and nearly two-thirds of prescriptions for newly launched drugs go unfilled in their first year.
The evidence is positive but uneven. In a 64-study systematic review, 66% of the studies that measured adherence found a positive effect, but fewer than a quarter of studies measured costs.
Regulators treat a PSP as an organised data collection system, so adverse events heard in a PSP are handled as solicited reports.
Strong programs are measured on time to therapy, abandonment, persistence and safety-reporting timeliness, not on call volumes.
A patient support program (PSP) is a set of services, usually funded by a pharmaceutical manufacturer, that helps patients get on a prescribed therapy, afford it and stay on it. Typical services include enrollment and consent, benefits verification and prior authorization support, financial assistance, nurse and adherence support, disease education, and logistics such as home delivery or travel to a treatment centre. In pharma, the abbreviation PSP almost always means patient support program (or "patient support programme" in UK and EU usage).
This guide covers what PSPs are, the main types, how a program works step by step, who runs them, what the evidence says, the compliance rules that shape every program, the KPIs worth tracking, and how platforms are changing delivery. It is written for patient services leads, commercial operations teams and anyone scoping a new program. Zelthy is an AI-native platform that pharmaceutical companies use to build and run patient support programs. It is deployed across 12+ countries, has been used to manage more than 1 million patient journeys, and its customers include Roche, BMS, AstraZeneca and Novo Nordisk. Where we draw on our own deployments, we say so.
What is a patient support program?
In everyday use, a PSP is the umbrella for everything a manufacturer does to help patients between the prescription and long-term therapy success. Some programs are a single phone line and a copay card. Others combine nurse case managers, specialty pharmacy coordination, home infusion and data feeds back to medical affairs.
Regulators define the term more precisely, and the definition carries obligations. The FDA's final ICH E2D(R1) guidance on post-approval safety data describes PSPs as organised data collection systems (ODCSs) "initiated by an MAH" (the marketing authorisation holder) that include "a mechanism for two-way communication" between the company and patients or healthcare professionals. Put simply: if a manufacturer runs a program that talks to patients, regulators expect it to listen for safety information. The compliance section below covers what that means in practice.
PSP vs PAP vs hub services vs specialty pharmacy
These four terms are often used interchangeably, but they describe different things. The short answer to the most common question is that a patient assistance program (PAP) is one financial tool that usually sits inside a broader PSP. For how the split works under different regulatory regimes, see our guide to how patient support programs work in the US and EU.
Term
What it is
Typical scope
Usually run by
Patient support program (PSP)
The umbrella program supporting a patient across the therapy journey
The manufacturer, often through one or more vendors
Patient assistance program (PAP)
A financial component that provides free or discounted medicine to eligible patients
Eligibility and income checks, drug supply, re-certification
The manufacturer or a manufacturer-affiliated foundation
Hub services
A US operating model that centralises access services for a therapy
Intake, benefits investigation, prior authorization, copay support, routing to pharmacy
A third-party hub vendor or an in-house team
Specialty pharmacy
A licensed pharmacy that dispenses high-cost or complex medicines
Dispensing, clinical counselling, refill management, data reporting
A pharmacy operator, often in a limited network
One regional caveat: in much of Asia-Pacific, "PAP" usually means patient access program, and programs are often split differently. Our guide to PAP vs PSP vs CAP vs DTP in Asia-Pacific covers those differences.
Why patient support programs matter more in 2026
Four trends explain why PSPs have moved from a nice-to-have to a core part of launch planning.
Specialty medicines dominate spending. According to the US Department of Health and Human Services, specialty drugs represented 50% of total drug spending in 2021, even though they rarely exceeded 20% of retail prescriptions. These are the therapies with complex administration, cold chain requirements, prior authorization and high cost-sharing, which is exactly where patients need help.
PSPs cluster around the therapies that need them most. A 2023 cross-sectional study in Canada found that 256 of 2,556 marketed prescription drugs (10.0%) had a manufacturer-sponsored PSP, concentrated around brand-name, biologic, orphan and high-cost drugs. Higher-priced drugs were far more likely to have a program, which matches what patient services teams see in practice.
Access and reimbursement support. Benefits investigation, prior authorization submission and follow-up, appeals, and finding alternative coverage. In the US this is usually delivered through a hub.
Financial assistance. Several tools sit under this heading: copay cards for commercially insured patients, patient assistance programs that supply free medicine to uninsured or underinsured patients, bridge or quick-start supply while coverage is pending, and referrals to independent charitable foundations. US federal program rules shape who can receive which tool, as covered below. For how a PAP connects to product tracking and adherence, see our overview of complete therapy management.
Clinical and nurse support. Nurse educators, injection training, side-effect management, home infusion coordination and case management for complex patients.
Adherence and persistence programs. Refill reminders, scheduled check-ins, and outreach triggered by a missed refill or a change in a patient's risk profile.
Education and engagement. Disease and therapy education for patients and caregivers through calls, SMS, email, apps and printed materials.
Logistics and concierge support. Home delivery, cold chain coordination, and travel and lodging for patients who must be treated at specialist centres.
Early and special access. Programs that provide medicines before approval or outside normal channels, such as US expanded access and EU compassionate use. Our guide to expanded access programs for sponsors explains when and how these run.
How a patient support program works: the patient journey
Whatever the mix of services, most PSPs follow the same sequence. Each step is a point where a patient can drop out, so each one needs an owner, a service level and data that flows to the next step.
Identification and referral. A healthcare professional prescribes the therapy and refers the patient to the program, on paper, by fax or through an electronic referral.
Enrollment and consent. The program captures patient details and the consents it needs for each purpose, such as a HIPAA authorization in the US or explicit consent under GDPR in the EU.
Benefits investigation and prior authorization. The team confirms coverage, identifies out-of-pocket costs and supports the prescriber's prior authorization or appeal.
Financial assistance matching. The patient is matched to the right tool: copay support, PAP, bridge supply or a foundation referral.
Fulfillment and first dose. The prescription is routed to a specialty pharmacy, home delivery is arranged, or a treatment appointment is scheduled.
Onboarding and education. A welcome call, nurse visit or training session prepares the patient for treatment.
Adherence and persistence support. The program tracks refills and check-ins, and focuses outreach on patients most at risk of stopping.
Safety capture and outcomes. Adverse events and product complaints are captured at every touchpoint and routed to pharmacovigilance, and outcome data is collected where consent allows.
Each handoff is a point where patients can be lost, and every touchpoint is a source of safety information
In many programs, these steps are split across several vendors: a hub for access, a pharmacy for dispensing, a nursing agency for clinical support and a call centre for adherence. Each runs its own system, so no one sees the whole patient. We cover the cost of that fragmentation, and how a shared data layer across the four pillars of a PSP addresses it, in a separate guide.
Who runs a patient support program?
The manufacturer funds and is accountable for the program, but day-to-day operations can be organised in four broad ways.
Model
How it works
Strengths
Trade-offs
In-house
The manufacturer's own team runs operations on its own systems
Full control of experience and data
Slow to staff and build; hard to scale across therapies and countries
Outsourced hub or service provider
A vendor runs intake, access and support on the vendor's systems
Fast to start; ready-made staff and processes
Data sits with the vendor; switching vendors means migrating patients
Specialty pharmacy-led
The dispensing pharmacy provides most clinical and adherence support
Close to dispensing and refill data
Support tied to one channel; patients outside the network are missed
Hybrid on a manufacturer-owned platform
The manufacturer owns the system of record; vendors work inside it
Want one patient record, whichever vendors run your PSP?
Zelthy lets manufacturers run patient support programs on a platform they own, with hub, pharmacy and nursing vendors working inside one shared patient record. It is built on the open-source Zango framework, so the code stays yours.
Do patient support programs work? What the evidence says
The short answer is yes, on adherence and persistence, with important caveats about study quality and economics.
The broadest review. A 2016 targeted systematic review of 64 PSP studies found that 27 of the 41 studies that measured adherence (66%) reported a positive effect, and 64.1% of studies reported at least one significantly positive clinical outcome. Only 15 studies (23.4%) reported cost or utilisation outcomes, and 12 of those were positive.
Pooled effect sizes. A 2015 meta-analysis of 17 studies in inflammatory and immunologic diseases found programs increased adherence (odds ratio 2.48) and persistence (odds ratio 2.26). Programs that combined informational and behavioural strategies performed best, with an adherence odds ratio of 3.68.
The European picture. A 2022 systematic review of PSPs in Europe found that 75% of the 20 studies of programs meeting the EMA definition reported achieving their objectives, but only 45% of those studies were comparative. The authors called for a standardised definition of patient support programs.
A recent therapy-specific example. In severe asthma patients on a biologic, a 2024 systematic review and indirect comparison found 48-week discontinuation of 5.9% with a PSP versus 16.0% without. The study was manufacturer-funded and the comparison was observational, so confounding is likely.
Two practical lessons follow. First, programs that combined informational and behavioural strategies showed the largest effect in the meta-analysis, so design for both. Second, most published studies do not measure economics, which makes their value hard to defend at budget time. Build measurement into the program design from day one.
PSP data is also increasingly used as real-world evidence. A 2022 retrospective study of a Canadian psoriasis PSP database, for example, reported treatment persistence of 90.4% at one year. Studies like this have no non-PSP comparator, so they describe outcomes inside a program rather than proving its effect, but they show why clean, consented PSP data has value beyond operations. For more on effectiveness across regions, see our analysis of whether PSPs really work in the US and EU.
Compliance guardrails every patient support program must design for
PSPs sit close to patients, prescribers and money, so several regulatory regimes apply at once. The summary below states what regulators have published. It is not legal advice, and program teams should confirm their approach with their own regulatory, pharmacovigilance and legal functions.
In practice, this means every channel (calls, SMS, chat, nurse visits, pharmacy contacts) needs an adverse event intake path and trained staff. Because many PSP interactions run through vendors, sponsors also need contracts and processes that move safety information to pharmacovigilance fast enough to meet these clocks. We cover the architecture in detail in pharmacovigilance in patient support programs.
US fraud and abuse rules for financial assistance
Financial support is where US programs face the most scrutiny. In a 2014 Special Advisory Bulletin, the HHS Office of Inspector General (OIG) said that pharmaceutical manufacturers that offer copayment coupons may be subject to sanctions if they fail to take appropriate steps to prevent coupons being used for drugs paid for by federal health care programs such as Medicare Part D. This is why manufacturer copay cards are typically limited to commercially insured patients. The OIG also issued supplemental guidance on independent charity patient assistance programs in the same year, which shapes how manufacturers may support foundations that help federally insured patients.
PSPs collect health data, so privacy rules apply at every step. In the US, HIPAA applies to covered entities such as providers and health plans and to their business associates. A manufacturer is generally not a covered entity, but the providers and pharmacies that hold patient records usually are, so programs rely on signed patient authorizations to receive data. Under 45 CFR 164.508, using protected health information for marketing requires an authorization. In the EU, GDPR Article 9 treats health data as a special category, and explicit consent for specified purposes is one of the permitted exceptions. India's DPDP Act adds its own consent model, which we cover in DPDP compliance for patient support programs in India.
A good rule of thumb: model consent per purpose (program services, safety reporting, outcomes research, marketing) rather than as one checkbox, and keep pharmacovigilance obligations separate from program consent, because safety reporting duties do not depend on whether a patient opts in to other services.
How to measure a patient support program: the KPIs that matter
Many programs report activity: calls handled, cases opened, materials sent. Those are service levels, not outcomes. The KPIs below follow the patient journey and connect program work to whether patients start and stay on therapy.
Whether the program reaches the patients it was built for
Access
Benefits investigation and prior authorization turnaround; approval rate
Where access friction is slowing patients down
Therapy start
Time from referral to first dose; abandonment rate
How many approved patients never start, and why
Ongoing therapy
Persistence at 6 and 12 months; adherence (for example, proportion of days covered)
Whether support keeps patients on therapy
Safety
Share of adverse events forwarded to pharmacovigilance within internal timelines; reconciliation completeness
Whether the program meets its regulatory obligations
Experience
Patient satisfaction or effort score; burden on HCP offices
Whether the program is easy to use for patients and prescribers
Economics
Cost per enrolled patient; cost per persistent patient-month
Whether the program's value can be defended at budget time
Measure the funnel, not the call volume. Each drop between stages has a KPI that tracks it.
Remember the evidence gap noted above: fewer than a quarter of published PSP studies reported economic outcomes. Teams that can show cost per persistent patient, alongside safety and adherence metrics, are in a stronger position when budgets are reviewed.
Patient support for cell and gene therapy and rare disease
These therapies are often given once, at a small number of qualified treatment centres, after a manufacturing process tied to the individual patient. Support needs change accordingly. For autologous CAR-T therapies, for example, the FDA notes that under current labeling patients should remain within proximity of a healthcare facility for at least two weeks and avoid driving for two weeks. That makes travel, lodging and caregiver support part of the treatment pathway, not an extra. Programs also coordinate apheresis and infusion scheduling, chain of identity, and long-term follow-up.
Rare disease programs face a different constraint: very small patient numbers spread across many countries. A single program design that can be configured for each market is usually more practical than building separate programs country by country. Zelthy's approach to these workflows is described on our advanced therapies page.
How digital platforms and AI are changing patient support programs
Traditional PSPs were built around call centres, fax, spreadsheets and several disconnected vendor systems. Platform-based programs change three things.
One patient record across channels and vendors. Self-service portals, e-consent, SMS, apps, nurse visits and pharmacy data feed a single case, so every team sees the same patient.
Configuration instead of rebuilds. Programs are designed around therapy complexity, patient digital literacy and market rules. US programs emphasise insurance navigation, while EU programs place more weight on outcomes measurement and industry codes, as our US vs EU PSP comparison explains. A platform lets one core design carry these differences as configuration.
AI applied to the bottlenecks. The highest-value uses are enrollment document validation, predicting which patients are at risk of stopping therapy, and detecting possible adverse events in unstructured conversations. Our guide to AI in patient support programs maps six capabilities across the PSP lifecycle.
Programs also need oversight across countries and vendors, especially for safety and promotional compliance. We describe how to approach this in global patient program compliance monitoring.
Zelthy's approach. Zelthy is a configurable, AI-native platform for building patient support programs, built on the open-source Zango framework so customers retain ownership of their code. Programs deployed on Zelthy include India's largest oncology patient assistance program for a global pharmaceutical company, and a government program that monitors more than 1 million HIV-positive patients in India. In one cancer therapy PSP deployed on Zelthy, adherence improved by 45%, onboarding was 60% faster and operating costs fell by 30%. See the Zelthy patient support program platform for the full set of use cases.
What a patient support program cannot fix
Being clear about limits makes programs more credible with payers, regulators and patients.
A PSP does not fix coverage or pricing policy. It can help patients through the system, but it cannot change what a plan covers or how much a therapy costs.
Technology does not replace people. Automation removes paperwork and delays, but nurses, case managers and pharmacists still carry the relationships that keep patients on therapy.
Program design is scrutinised. Because PSPs are funded by manufacturers, regulators and researchers watch closely how support, data use and commercial activity are separated. Keep that separation clear in both design and documentation.
Planning a patient support program: five questions to answer first
Where exactly do patients drop off for this therapy today, and what does each drop-off cost?
Which program types (access, financial, clinical, adherence, logistics) address those drop-offs in each market?
Who will run each step, and who will own the patient record and data across vendors?
How will safety information be captured on every channel and routed to pharmacovigilance?
Which KPIs, including economic ones, will prove the program works, and are they built in from launch?
A patient support program is the operational bridge between a prescription and a patient who stays on therapy. The programs that perform best combine several support types, follow the patient journey end to end, treat safety capture and consent as design requirements, and measure outcomes rather than activity. If you are planning or re-platforming a PSP, talk to the Zelthy team about how programs are configured on our platform.
Frequently asked questions
What is a patient support program (PSP) in pharma?
A patient support program is a set of services, usually funded by a pharmaceutical manufacturer, that helps patients start a prescribed therapy, afford it and stay on it. Services typically include enrollment, benefits and prior authorization support, financial assistance, nurse and adherence support, education and logistics.
What are the main types of patient support programs?
The main types are access and reimbursement support, financial assistance, clinical and nurse support, adherence and persistence programs, education and engagement, logistics and concierge support, and early or special access programs. Most programs combine several types depending on the therapy and market.
What is the difference between a PSP and a PAP?
A patient assistance program (PAP) provides free or discounted medicine to eligible patients, while a patient support program (PSP) is the broader umbrella that can include a PAP alongside access, clinical, adherence and education services. In Asia-Pacific, PAP often means patient access program instead.
What is the difference between hub services and a specialty pharmacy?
Hub services centralise access work for a therapy, such as intake, benefits investigation, prior authorization and copay support. A specialty pharmacy is a licensed pharmacy that dispenses high-cost or complex medicines and provides clinical counselling and refill management. A hub typically routes patients to a specialty pharmacy.
Do patient support programs improve adherence?
Generally yes. In a 64-study systematic review, 66% of the studies that measured adherence reported a positive effect, and a meta-analysis in inflammatory and immunologic diseases found programs increased adherence with an odds ratio of 2.48. Most evidence is observational, so results vary by program design.
Do patient support programs have to report adverse events?
Yes. Regulators treat PSPs as organised data collection systems, so adverse events heard in a PSP that meet reporting criteria are handled as solicited reports with a causality assessment under FDA's ICH E2D(R1) guidance and EMA's GVP Module VI. Every program channel needs an adverse event intake path.
How do you measure the success of a patient support program?
Measure the patient journey rather than activity: enrollment rate, prior authorization turnaround, time to first dose, abandonment, persistence at 6 and 12 months, adverse event reporting timeliness, patient satisfaction and cost per persistent patient. Fewer than a quarter of published PSP studies report economic outcomes, so build them in from launch.
Who runs patient support programs?
Manufacturers fund and are accountable for PSPs, but operations may be run in-house, outsourced to a hub or service provider, led by a specialty pharmacy, or run as a hybrid on a manufacturer-owned platform. In a Canadian study, half of programs used a third-party administrator.
Related Solution
Looking for a patient support program platform?
Zelthy is pharma's patient support program platform, deployed across 12+ countries and used to manage more than 1 million patient journeys. Configure enrollment, consent, access, adherence and adverse event intake once, then carry one program design across therapies and markets without rebuilding it.