Companies must be able to demonstrate how the programme was designed, approved, delivered, monitored, documented and, where relevant, reflected in transparency reporting.
That distinction matters because a PSP occupies a regulated space between clinical support and commercial activity. The service may involve patients, caregivers, healthcare professionals, vendors and patient organisations, all within the same operating model. A weakness at any one point can alter the regulatory character of the entire programme.
The ABPI definition is functional. A PSP involves direct interaction with patients or caregivers to support the management of a medicine or disease, including awareness, education and adherence support. It may also provide healthcare professionals with assistance for their patients. The purpose is therefore central, but purpose alone does not settle compliance. The way the programme communicates, the items it supplies, the people who approve it and the records it creates are equally important.
The practical challenge is to preserve the programme’s non-promotional character in operation, not merely in the launch documentation.
Defining the Scope: Patient Support Programs vs. Promotional Activity
A non-promotional PSP should support clinical management without becoming an alternative route for promoting a prescription-only medicine to the public. The distinction is not determined by the programme’s name. It is determined by the totality of the activity: the content, the audience, the channel, the materials, the role of the healthcare professional and the commercial context.
Direct-to-consumer advertising of prescription-only medicines remains prohibited in the United Kingdom. A patient support service cannot be used to recreate that advertising relationship through adherence messages, branded resources or repeated patient contacts. Even when the stated objective is education, materials can become promotional if they go beyond what is necessary to support appropriate use or present the medicine in a persuasive way.
The same analysis applies to items supplied to healthcare professionals for distribution to patients. Patient support kits, educational resources, adherence aids and treatment accessories need a clear connection to the management of the medicine or disease. The relevant question is not simply whether an item is inexpensive. It is whether the item has a genuine patient-care function and whether that function is documented.
Under the Code provisions governing items provided to healthcare professionals and subsequently passed to patients, the cost limit is only one part of the assessment. A product can fall within the financial threshold and still create a problem if it has no meaningful treatment-related purpose. Conversely, a clinically relevant item still requires the right programme structure, approval and records.
A sound scope assessment should establish:
- the clinical or practical problem the programme is intended to address;
- the patient or caregiver need that justifies the interaction;
- the precise role of the healthcare professional;
- the reason each patient-facing item is necessary;
- the boundaries between education, adherence support and product promotion;
- the information that may be collected during the interaction;
- the route by which safety information will reach the pharmacovigilance function; and
- the records needed to demonstrate that the programme operated as approved.
This assessment should be completed before materials are finalised. It should also be revisited when the programme changes. A service that begins as a narrowly defined adherence intervention can acquire promotional features through a revised script, a new digital channel or a broader set of patient materials.
The non-promotional character of a PSP is something the company must preserve in practice, not simply describe in the launch approval.
Patient support items and the treatment-management test
The Code does not turn every useful object into an acceptable patient benefit. The more general the item, the harder it is to establish a direct connection with treatment management.
An item designed to help a patient store, administer, transport or understand a treatment may have a defensible purpose, depending on the circumstances. An item that functions primarily as a lifestyle product, gift or convenience benefit is more difficult to justify. Size, design, branding and the way the item is presented can all affect the assessment.
The compliance file should therefore explain why the item is needed, how it will be used and why the chosen specification is proportionate. It is not sufficient to record only its unit cost. A cost calculation without a functional rationale leaves the central question unanswered.
The same principle applies to digital resources. A patient portal, mobile service or reminder system may support adherence, but its content and functionality should be limited to the stated patient-support purpose. Product claims, comparative language, unnecessary brand prominence and calls to discuss treatment outside the agreed clinical pathway can shift the activity towards promotion.
The 2024 ABPI Code Update: Mandatory Procedural Shifts
The 2024 Code of Practice took effect on 1 October 2024, with the transition period ending on 31 December 2024. For PSP operators, the change was not confined to a new set of substantive rules. It also increased the importance of procedural evidence.
A company may have a clinically reasonable programme and still face difficulty if it cannot show who approved it, which version was used, what the vendor was required to do or how transparency obligations were addressed. The compliance record is not an afterthought. It is part of the programme’s control environment.
Written agreements
Written agreements should define the relationship between the pharmaceutical company and every material participant in the programme. Depending on the model, this may include healthcare professionals, patient organisations, service providers, call-centre operators, nurses, logistics providers and technology vendors.
The agreement should do more than describe the commercial relationship. It should allocate practical responsibilities, including:
- the scope and purpose of the programme;
- the services to be delivered and the materials to be used;
- the approval process for scripts, training and patient communications;
- the handling and escalation of adverse events and product complaints;
- data protection and information-security responsibilities;
- the retention and availability of programme records;
- restrictions on promotional activity;
- requirements for staff training and supervision; and
- audit, monitoring and termination rights.
A contract cannot transfer the pharmaceutical company’s responsibility under the Code or under pharmacovigilance rules. It can, however, make the operational chain visible and enforceable. Vague clauses that simply require the vendor to comply with “all applicable laws” do not provide the same control as a documented reporting pathway with named responsibilities and escalation routes.
Disclosure UK and the company website
The transparency requirements need to be described precisely. The Code does not create a universal obligation for companies to publish the existence of every PSP as a standalone public listing. The relevant obligations depend on what the programme involves and whether it creates a reportable transfer of value or relationship with a patient organisation.
Companies should maintain the required public information on their own website, including the appropriate link to the relevant Disclosure UK information where the reporting framework applies. The website arrangement should allow readers to find the company’s transparency information without having to infer that a PSP exists from promotional or corporate material.
Where a PSP involves a patient organisation, the company must consider the disclosure requirements applying to that relationship. This can include identifying the patient organisation and reporting the nature and value of relevant financial support or significant non-financial support, in line with the applicable Code requirements. The disclosure should correspond to the underlying arrangement and the reporting period; it should not be replaced by a vague statement that the company supports patient engagement.
The key distinction is between:
1. the existence of a PSP, which is not automatically subject to a universal public-listing requirement; and
2. reportable transfers of value or relationships, which may require disclosure through the applicable transparency process and supporting information on the company website.
This distinction prevents two opposite errors. The first is over-disclosure: treating every PSP as though it must be publicly listed regardless of its structure. The second is under-disclosure: assuming that a programme is exempt simply because it is described as patient support.
Annual reporting and supporting records
Annual transparency reporting should be planned alongside programme delivery. It should not be left until the reporting deadline, when the company may have to reconstruct the value, nature and recipient of support from incomplete operational records.
For patient-organisation relationships, the relevant file should identify what was provided, to whom, for what purpose and at what value. Financial support is usually easier to trace than non-financial support. Staff time, meeting facilities, training, services and other in-kind contributions may require an agreed valuation method and a clear record of the assumptions used.
A practical reporting file may contain:
- the written agreement and any amendments;
- approval records for the activity;
- invoices and payment records;
- descriptions of non-financial support;
- calculations for in-kind contributions;
- records of the reporting period;
- confirmation of the recipient’s legal or organisational identity;
- the final disclosure entry; and
- evidence that the website information and relevant Disclosure UK link were maintained.
The precise reporting treatment can depend on the nature of the relationship and the type of support. The compliance team should resolve that classification before the activity begins, rather than attempting to decide after the fact whether a service was sponsorship, a grant, a donation, consultancy or another form of support.
Medical Signatory Oversight and Certification Requirements
Medical signatory involvement is a control at programme conception, not merely a final approval stamp. The signatory’s role is to assess whether the programme’s purpose, content and operating model remain consistent with the Code and with the clinical information governing the medicine.
That review should cover more than a patient leaflet. It may need to include:
- the programme rationale and scope;
- patient eligibility and enrolment arrangements;
- scripts used by nurses, call-centre staff or other personnel;
- training materials;
- digital journeys and automated messages;
- adherence reminders;
- escalation instructions;
- patient-facing forms;
- treatment accessories and support kits;
- data-collection fields;
- complaint and product-quality processes; and
- the proposed pharmacovigilance workflow.
The review should also be proportionate to the programme’s risk. A static educational resource and a service involving repeated clinical conversations do not create identical control needs. The approval process should reflect the nature of the interaction, the vulnerability of the patient population and the extent to which staff may discuss treatment or respond to patient questions.
Certification records should identify the approved version, the date of review, the programme reference and the responsible signatory. If approval is conditional, the conditions should be captured rather than left in email correspondence. If the programme is amended, the company should be able to show whether the change was assessed as minor or whether it required renewed medical review.
Version control is part of the evidence
A common weakness in PSP governance is a gap between the material that was approved and the material that patients actually received. This can occur when a vendor updates a script, a digital team changes an automated message or a call-centre agent works from an outdated document.
Version control should therefore be operational, not decorative. Staff should have access to the current approved version, obsolete versions should be withdrawn from use, and material changes should trigger a defined review. A record of approval without evidence of controlled implementation does not fully demonstrate oversight.
The same principle applies to translations, local adaptations and accessible formats. If the meaning changes, or if a local version introduces new claims or instructions, it should be assessed on its own terms. A translated document is not automatically compliant merely because the English version was approved.
The Summary of Product Characteristics and clinical boundaries
Patient materials should remain consistent with the Summary of Product Characteristics and other applicable regulatory materials. That does not mean every communication must reproduce the product information. It means that the programme must not introduce unapproved indications, unsupported benefits, misleading comparisons or instructions that conflict with the authorised use of the medicine.
The signatory should also consider how staff are expected to respond when patients ask questions outside the programme’s remit. A patient support service may provide practical assistance without becoming a substitute for a prescriber or a general medical advice line. Escalation instructions should make that boundary clear.
Integrating Pharmacovigilance into Patient-Facing Services
A PSP is a source of safety information because it creates direct contact with patients and caregivers. Conversations about treatment may reveal adverse events, lack of effect, medication errors, misuse, product complaints or changes in the patient’s condition. Those signals can arise even when the programme is designed only to support adherence or administration.
The marketing authorisation holder retains responsibility for ensuring that information from the programme reaches its pharmacovigilance system. Outsourcing the service does not outsource accountability. A call-centre provider, nurse service, logistics company or technology vendor may perform part of the process, but the MAH must define, train, monitor and audit the pathway.
Pharmacovigilance should be involved at the concept stage. Waiting until the programme is ready for commercial launch creates avoidable problems: data fields may be missing, staff may not know what constitutes a report, contracts may lack escalation provisions and the vendor may have designed a workflow that cannot be reconciled with the safety database.
A workable operating model should address:
- how staff identify possible adverse events;
- what information must be captured from the patient or reporter;
- how quickly the information is transferred;
- who reviews the initial report;
- how follow-up information is obtained;
- how product complaints and medication errors are handled;
- how duplicate reports are identified;
- how PSP records are reconciled with the safety database;
- how urgent safety issues are escalated; and
- how vendor performance is monitored.
Training should be practical. Staff do not need to diagnose an adverse event, but they do need to recognise when a patient has described a possible safety issue and know what to do next. The process should not depend on a patient using formal regulatory language. A complaint about feeling unwell, a report that a device did not work as expected or a statement that treatment was taken incorrectly may all require assessment.
Vendor oversight and audit
The vendor agreement should specify reporting expectations, contact points, timeframes, training obligations and record-access rights. It should also describe what happens when a report is incomplete, late or inconsistent with the agreed procedure.
Periodic oversight may include training checks, sample reviews, reconciliation exercises, issue logs and targeted audits. The purpose is not to create paperwork for its own sake. It is to test whether the process works when a real patient interaction produces information that was not anticipated in the programme script.
A PSP that treats patient contact solely as a service-delivery channel may miss the safety function built into that contact. Pharmacovigilance must be embedded in the workflow rather than added as a separate compliance paragraph.
Transparency and Disclosure: Managing Annual Reporting Obligations
Transparency is most reliable when it is designed into the programme from the beginning. The company should know at launch whether the programme involves a patient organisation, whether support is financial or non-financial, which records will establish value and where the relevant public information will appear.
The annual reporting process should distinguish between different kinds of activity. A patient organisation may receive a grant, sponsorship, payment for services, support for a meeting, training or in-kind assistance. Each arrangement can raise different questions about documentation and valuation. Combining them into a single unexplained figure makes the disclosure harder to verify and the internal review harder to perform.
The company should also avoid assuming that a link to Disclosure UK resolves every transparency issue. The link supports access to the relevant public record; it does not replace the underlying disclosure, the company’s website information or the records supporting the reported relationship.
A controlled process usually assigns ownership across several functions:
- the medical or compliance team confirms the Code classification;
- procurement and legal teams maintain the written agreement;
- finance records payments and supporting invoices;
- the programme team records delivery and non-financial support;
- pharmacovigilance monitors safety information;
- the transparency owner prepares the annual submission; and
- the website owner maintains the public information and relevant link.
This division is useful only if the hand-offs are documented. An annual disclosure can fail because a programme team did not tell finance about an in-kind contribution, because a vendor invoice did not identify the patient organisation or because a website link was not updated after publication.
Documented Compliance Failures and Operational Risk
The PMCPA’s published rulings show why apparently minor programme details can become central to a breach assessment. In the case identified as AUTH/2498/4/12, the Panel considered items supplied to patients alongside treatment accessories. The assessment focused on whether the items directly benefited patient care and were connected to treatment management. A rucksack was found not to satisfy that test in the circumstances considered, while the cool bag intended for treatment accessories was assessed differently.
The significance of the case is not limited to one product or therapeutic area. It illustrates the need to explain the function of every item supplied through a PSP. A general-purpose product may be perceived as a benefit rather than a treatment-management aid, particularly where its size, design or use extends beyond what the patient needs for the treatment.
The case also demonstrates why financial value is not the whole analysis. A low-cost item may still be inappropriate if its clinical connection is weak. Conversely, the existence of a clinical rationale does not remove the need for medical signatory review, controlled distribution and appropriate documentation.
Operational risk commonly appears in four forms:
1. Scope drift. The programme accumulates brand-led messages, broader patient targeting or additional materials that were not part of the original non-promotional rationale.
2. Approval gaps. Materials are used before certification, or a vendor deploys a revised version without renewed review.
3. Evidence gaps. The company cannot show which version was used, who approved it or how an item’s treatment-related purpose was assessed.
4. Reporting gaps. A patient-organisation relationship or non-financial contribution is not captured in the records needed for annual transparency reporting.
These risks reinforce one another. Scope drift makes medical review more difficult. Weak approval records make it harder to establish the programme’s original purpose. Poor vendor documentation affects both pharmacovigilance and disclosure. A compliance review should therefore examine the programme as a connected system rather than as separate legal, medical and operational files.
Building a defensible PSP operating model
A defensible programme does not depend on a single approval document. It depends on a chain of decisions that remain intelligible months after launch.
Before implementation, the company should be able to answer:
- What patient need does the programme address?
- Why is the proposed interaction necessary?
- What makes the service non-promotional?
- Which materials and items will be used?
- How has the treatment-management connection been assessed?
- Who has approved the content and operating model?
- Which activities are delegated to a vendor?
- How will safety information be identified and escalated?
- Does the programme involve a patient organisation or reportable support?
- Where will the relevant transparency information and Disclosure UK link appear?
- What records will be retained, and who owns them?
During operation, monitoring should test the assumptions made at launch. Patient feedback, complaints, staff questions, safety reports and vendor deviations can all indicate that the programme no longer functions as originally approved. Changes should be logged and assessed rather than absorbed informally into day-to-day delivery.
The 2024 Code therefore changes the practical meaning of PSP compliance. The issue is not simply whether a programme can be described as educational, supportive or patient-centred. The company must show that the description matches the materials, the interactions, the contracts, the reporting and the evidence.
Patient Support Programmes remain valuable when they help patients use medicines safely and appropriately. But their legitimacy depends on disciplined boundaries. Non-promotional intent, medical signatory oversight, pharmacovigilance integration and accurate transparency reporting are not separate formalities. Together, they define whether the programme remains within the regulatory space the company intended to occupy.