Back to Blog
Patient Support

Patient Support Programs Under ICH E2D(R1): What Changes

ICH E2D(R1) defines what counts as a patient support program and explains how companies should document programs, assess adverse events and oversee vendors.

6 min read

The revised ICH guideline on post-approval safety data gives patient support programs (PSPs) their first harmonised definition and a clear documentation standard. For companies running programs in Morocco and across the region, it is the right moment to make sure every nurse call, adherence app and reimbursement helpline is designed for pharmacovigilance from day one.

A guideline twenty years in the making

The original ICH E2D guideline, adopted in 2003, set common definitions for handling post-marketing safety reports. Since then, the way companies interact with patients has changed profoundly: helplines, home nursing, mobile apps, social listening and market research now generate safety information that the 2003 text never anticipated. The revision, ICH E2D(R1), was endorsed at Step 4 on 15 September 2025. It came into legal effect in the European Union on 18 March 2026, and the European Medicines Agency (EMA) has published an implementation strategy that specifically addresses the transition to the new PSP definition and to the documentation now expected for data collection activities run without a protocol. The US Food and Drug Administration (FDA) issued the guideline as guidance for industry in March 2026. With the EU and the US aligned, the new definitions are quickly becoming the reference for global safety teams and their partners.

What now counts as a patient support program

E2D(R1) places PSPs within a broader family called organised data collection systems (ODCS): planned activities that gather data on a company's product or disease area in a way that allows review. A PSP is an ODCS initiated by the marketing authorisation holder (MAH), in which patients enrol to support the use of its product or the management of their condition, and which includes a two-way communication channel between the MAH, or a third party acting for it, and patients or healthcare professionals. A program qualifies when it actively solicits medical information about a patient's use of the product, or when its design means such information will foreseeably reach the MAH, for example when a nurse administers treatment or gives medical advice. Typical examples include adherence support, disease management and certain educational or reimbursement programs. Equally important is what falls outside the definition: Stand-alone one-way services, such as home delivery or vouchers, provided the MAH does not request medical information. Clinical trials and non-interventional studies, including post-authorisation safety studies. All forms of compassionate use and named patient supply. The guideline also settles a frequent grey zone. When a program combines several services, and at least one of them meets the PSP criteria, adverse events received through any part of the program are managed as PSP reports. A delivery service bundled with nurse-assisted administration is therefore a PSP in its entirety.

From spontaneous to solicited: what it means for case handling

Safety reports from PSPs are solicited reports, a position EU pharmacovigilance practice had already taken under GVP Module VI. E2D(R1) now makes the operational consequences explicit across ICH regions: Causality matters. Solicited reports require a causality assessment and are submitted only when a causal relationship is at least a reasonable possibility, as judged by the reporter or the MAH. Clear coding. They are classified as "report from study" in ICH E2B format, with a dedicated PSP value for the study type, so authorities can distinguish them from trial data. EMA has indicated that EU implementation of the new code values will follow later through EudraVigilance change management. The clock starts early. Day zero is the date any personnel of the MAH, including service providers, holds the minimum information for a valid case. Serious, unexpected cases must be reported within 15 calendar days of that date. One-way activities stay spontaneous. Events arising from stand-alone deliveries or coupons, outside any ODCS, are handled as spontaneous reports.

The documentation every program now needs

Because PSPs are not run under a study protocol, E2D(R1) asks MAHs to keep documentation that describes, at a minimum, the objectives of the activity, the data sources, the dataset collected (including its duration), the review method, and the process for collecting and managing adverse events and other observations. When a vendor operates all or part of the program, contractual agreements must ensure that adverse events flow back to the MAH, with defined timelines. The guideline is unambiguous on accountability: whatever the contract says, the MAH remains responsible for reporting on time, so partners should keep data exchange periods as short as possible.

Applying the standard in Morocco and the region

E2D(R1) repeatedly defers to regional and local requirements, and MAHs are expected to check them for each country. In Morocco, a PSP processes health data, which places it under Law 09-08 on the protection of personal data and the oversight of the national data protection authority, the CNDP. In November 2025, the CNDP adopted a deliberation setting out a model authorisation request for patient follow-up processing, a useful reference when structuring consent, information notices and data transfers. In practice, a robust regional program aligns three layers: the ICH framework, local pharmacovigilance and data protection rules, and the operating reality of call centres, nurses and digital tools. Training front-line staff to recognise and capture adverse events, reconciling safety data between vendor and MAH, and auditing the flow before launch are what turn a compliant design into a compliant program.

Key takeaways

ICH E2D(R1) defines a PSP by enrolment and two-way communication; one-way services such as delivery or coupons are excluded on their own. Adverse events from any part of a combined program are solicited reports that need a causality assessment and expedited reporting when serious and unexpected. Every PSP needs written documentation of objectives, data, review method and safety process, plus vendor agreements that protect the MAH's reporting timelines.

Building programs that are safe by design

The revised guideline rewards companies that treat patient support and pharmacovigilance as a single design exercise rather than two separate workstreams. MSHealth designs and operates patient support programs and pharmacovigilance services aligned with EU GVP and ICH requirements, from documentation and vendor oversight to adverse event intake and reconciliation. To review an existing program or plan a new one in Morocco and the wider region, submit your RFP and our team will get back to you.

Sources

ICH E2D(R1) Guideline, final version adopted 15 September 2025 (PMDA-hosted copy): https://www.pmda.go.jp/files/000277432.pdf (accessed 19 November 2026) EMA, ICH E2D post-approval safety data management, scientific guideline and EU implementation strategy (EMA/11141/2026): https://www.ema.europa.eu/en/scientific-guidelines/ich-e2d-post-approval-safety-data-management (accessed 19 November 2026) FDA, E2D(R1) Postapproval Safety Data, Guidance for Industry, March 2026: https://www.fda.gov/media/176977/download (accessed 19 November 2026) MHRA Inspectorate, Patient Support Programmes (GVP Module VI context): https://mhrainspectorate.blog.gov.uk/2020/05/07/patient-support-programmes/ (accessed 19 November 2026) Law 09-08 on the protection of individuals with regard to the processing of personal data, B.O. n° 5714 of 5 March 2009 (Adala, Ministry of Justice): adala.justice.gov.ma (accessed 19 November 2026) CNDP, Deliberation n° D-941-2025 of 28 November 2025 on the model authorisation request for patient follow-up processing: cndp.ma (accessed 19 November 2026)