Swiss pharmacovigilance: RPPV duties, deputy and reporting

Key takeaways

• The Swiss RPPV is a functional responsibility, not a name placed in an organisation chart.
• External delivery is possible, while regulatory accountability and provider oversight remain with the responsible company.
• Swiss intake, reporting, risk measures and product information interfaces must connect to the global safety system.
• Readiness is demonstrated through records, training, metrics, deputies and tested escalation paths.

What does the Swiss RPPV actually own?

Swissmedic describes the responsible person for pharmacovigilance as the central safety contact for the authority. The role coordinates complete and timely submissions, supports inspections, ensures Swiss risk-minimisation measures are implemented and keeps contact details available. The work reaches beyond individual case reports: it includes the local quality system, training, archiving and an overview of interfaces that can affect medicine safety.

The MAH should distinguish accountability from execution. A vendor may process cases or monitor literature, and a global team may run signal detection, but the Swiss role still needs enough authority, information and access to see whether local obligations are met. Written delegation is therefore a control document, not a transfer of regulatory accountability.

• Name the RPPV and a capable deputy.
• Give both access to current product and safety information.
• Document authority to escalate risks and quality failures.

Sources and further reading: [1][3]

Which operating model fits the Swiss portfolio?

Three models are common: an internal Swiss RPPV, an external RPPV with outsourced operations, or a hybrid in which the responsible person oversees a combination of local and global teams. Swissmedic permits the RPPV and deputy to be external and does not require Swiss residence. The decisive question is whether they are qualified, reachable through a resilient process and able to exercise oversight.

Use portfolio complexity to choose the model. Product count, risk profile, launch activity, language coverage, partner network and the maturity of the global safety system all affect workload. Our suggested method is to map every obligation to an owner, backup, input, output and retained record before comparing providers.

Sources and further reading: [1]

How should Swiss safety information move through the system?

All relevant entry points need a documented route into pharmacovigilance. This includes medical information, complaints, distributors, digital channels and staff who may receive a safety report. The practical design must define intake, minimum data capture, privacy-aware transfer, duplicate checks, medical review, follow-up and reconciliation. It should also identify which team decides Swiss reportability and which team transmits the record.

Swissmedic requires company individual case safety reports electronically in ICH E2B format through ElViS or an E2B gateway. Its industry guidance states that serious Swiss adverse reactions and non-serious unexpected Swiss reactions are reportable, with 15 days given for serious reports. Exact classification and clock-start decisions require trained review of the current rules, so the procedure should point users to controlled regulatory instructions rather than rely on a memory-based summary.

• Inventory every local intake channel.
• Set documented handoffs and reconciliation frequency.
• Test weekend and absence coverage.
• Retain evidence of submission and follow-up.

Sources and further reading: [2][4]

What belongs in the local PV quality system?

A defendable local system links procedures, role descriptions, training, deviations, corrective actions, audits and management review. Swissmedic expects a documented and functional quality management system. Its current RPPV guidance also calls for orderly retention of pharmacovigilance-relevant documents and datasets for at least ten years after the Swiss authorisation expires.

Do not build a parallel library simply to look local. A better design identifies which global procedures apply, where a Swiss annex is necessary and who approves changes. The local index should make Swiss requirements and records easy to retrieve, including authority correspondence, reporting evidence, risk-minimisation implementation, training status and vendor performance.

Sources and further reading: [1]

How do signal, risk and product-information interfaces work?

Swiss responsibility does not end when a case enters the global database. The RPPV needs a route for nationally or internationally identified safety issues, company signals, periodic reports, risk-management commitments and changes requested by Swissmedic. The interface with regulatory affairs must make safety-driven product-information changes visible, owned and traceable.

A useful governance forum reviews Swiss relevance, required action, submission ownership, local-language materials and distribution evidence. This is a suggested working method rather than a prescribed committee format. The regulatory outcome matters: decisions should be documented, deadlines tracked and unresolved disagreements escalated.

• Define the Swiss signal notification trigger.
• Connect RMP measures to implementation owners.
• Reconcile safety variations and current product information.
• Track distribution and effectiveness of additional risk materials.

Sources and further reading: [1][2]

How should an MAH assess an external pharmacovigilance provider?

Start with the real scope. Confirm whether the provider supplies only the named RPPV, full local operations, case processing, literature work, medical review or inspection support. Then test qualifications, deputy resilience, system access, data security, subcontracting and experience with Swissmedic processes. Marketing claims are not evidence of an operating system.

Swissmedic expects written responsibilities and structured, verifiable oversight where tasks are delegated. The authority identifies performance monitoring, audits, quality reviews, clear escalation channels and assurance of provider qualifications as elements of oversight. The MAH should therefore agree meaningful metrics and obtain records that show performance, rather than treating a signed agreement as sufficient.

Sources and further reading: [1]