Business Continuity for the Pharmacovigilance System: Keeping Safety Reporting Running When Things Go Wrong

Pharmacovigilance obligations continue through a cyber attack, an IT outage, a vendor failure or the unexpected absence of the QPPV. Expedited reporting timelines still run, and signals still need to be detected. EU good pharmacovigilance practice (GVP) expects marketing authorisation holders to plan for this in advance, and inspectors regularly test whether those plans would actually work.

What regulators expect

GVP Module I, on pharmacovigilance systems and their quality systems, expects MAHs to have business continuity arrangements for their pharmacovigilance activities. In practice this means:

  • identifying the critical PV processes that must continue during a disruption
  • back-up arrangements for the people, systems and data those processes depend on
  • documented procedures, held in the quality system and referenced in the pharmacovigilance system master file
  • evidence that the arrangements have been tested.

The critical processes

Not every activity needs the same level of protection. Priorities usually include:

  • Case intake and expedited reporting: receiving, processing and submitting serious ICSRs to EudraVigilance within 15 days.
  • QPPV availability: continuous access to the QPPV or a qualified deputy, including out of hours.
  • Safety database and gateway access: the ability to log in to EudraVigilance and submit electronically, with a documented fallback if the normal route fails.
  • Signal management and urgent safety issues: the ability to assess and communicate emerging risks, including direct healthcare professional communications.
  • Literature screening and medical information, which are often outsourced and therefore exposed to vendor risk.

Scenarios to plan for

  • Cyber incident affecting email, the safety database or document systems.
  • Vendor failure by a PV service provider or database host, which makes contract exit and data-return clauses essential.
  • Loss of key people, including the QPPV, the deputy and the local contact person for pharmacovigilance.
  • Site unavailability, such as office closure, power loss or natural events, which in Greece should include the risk of wildfires and earthquakes.

Testing the plan

A plan that has never been tested gives limited assurance. Useful practices include:

  • annual tabletop exercises covering a realistic scenario end to end
  • a periodic test submission through the back-up reporting route
  • checks that out-of-hours contact details really reach the QPPV or deputy
  • recording findings as CAPAs and following them through.

Inspectors often ask to see evidence of the last test and what changed afterwards.

How PQRA helps

PQRA designs and reviews pharmacovigilance business continuity arrangements for MAHs of every size. We map critical processes, draft procedures and PSMF content, review vendor contracts for continuity clauses, and run tabletop exercises that prepare teams and give inspectors the evidence they look for.

Review your PV continuity planning with PQRA →

CATEGORIES:

Uncategorized

Tags:

No responses yet

Αφήστε μια απάντηση

Η ηλ. διεύθυνση σας δεν δημοσιεύεται. Τα υποχρεωτικά πεδία σημειώνονται με *