Pharmacovigilance differences between the EU and Switzerland
Switzerland is a third country for EU pharmacovigilance. It is not part of EudraVigilance, it does not adopt EU decisions automatically, and it assesses expectedness against its own product information. A global system can serve Switzerland well, but only with a defined Swiss branch.
- Last reviewed:
- Reading time: 4 min
- Reviewed by Swiss Pharmacovigilance
Switzerland is a third country
There is no mutual recognition of pharmacovigilance decisions and no shared database. A submission to EudraVigilance does not reach Swissmedic, a PRAC outcome does not change a Swiss label, and an EU QPPV appointment does not discharge the Swiss role. Everything else follows from that.
The six differences that change your process
Most of the framework is shared, because both systems build on ICH. The differences are few, but each of them sits at a point where your process branches, which is why ignoring them produces systematic rather than occasional failures.
- The responsible person: a Swiss RPPV alongside or instead of the EU QPPV
- The submission channel: ElViS, with its own access and acknowledgements
- The expectedness reference: the Swiss product information, not the EU SmPC
- The PSUR interval: set by Swissmedic per authorisation, not by the EURD list
- Literature: no EMA monitoring service to rely on, so your own search covers it
- Decisions: EU label changes and referral outcomes have to be actively transposed
The EU and Switzerland point by point
The table is the one to hand to a global PV team that is taking on Switzerland for the first time. Each row is a place where a European process needs a Swiss branch rather than a translation.
| Topic | EU | Switzerland |
|---|---|---|
| Legal basis | Regulation 726/2004, Directive 2001/83, GVP modules | Art. 59 TPA, Art. 61 ff. TPO, Swissmedic guidance |
| Responsible person | QPPV, resident and operating in the EU | RPPV, reachable in Swiss business hours, no residence rule |
| Case database | EudraVigilance | ElViS, portal or gateway |
| Case format | ICH E2B(R3) | ICH E2B(R3) |
| Expectedness reference | EU SmPC | Swiss product information |
| Literature monitoring | EMA medical literature monitoring for some substances | Own documented search, no equivalent service |
| Periodic reports | EURD list, PSUSA single assessment | Interval set per Swiss authorisation |
| Signal management | EMA signal detection, PRAC assessment | Holder's own process, own decision, own record |
| Risk management | EU RMP template and PRAC review | Swiss adaptation, agreed with Swissmedic |
| Inspections | National competent authority under EU rules | Swissmedic, against the TPO and its guidance |
What does not transfer automatically
This is the list that catches global teams. None of it flows to Switzerland on its own, and all of it needs a named owner and a timeline on the Swiss side.
- EU label changes: the Swiss product information needs its own variation
- PRAC recommendations and referral outcomes: assessed and transposed deliberately
- EU direct healthcare professional communications: agreed with Swissmedic and translated
- Additional risk minimisation measures: re-agreed and re-issued in Swiss languages
- EU PSUR assessment outcomes: reflected in the Swiss submission and label
- Urgent safety restrictions taken in the EU: notified to Swissmedic without delay
One global system with a compliant Swiss branch
The goal is not a parallel Swiss system but one system that knows Switzerland exists. Six steps get you there, and all of them are configuration and documentation rather than new infrastructure.
- Flag Swiss cases in the global database at intake, by country of occurrence.
- Store the current Swiss product information where case assessors actually look.
- Route Swiss cases through a Swiss expectedness assessment before release.
- Submit through ElViS and file the acknowledgement in the global case record.
- Add Switzerland to the signal and label change workflow as a named market with an owner.
- Maintain a Swiss annex to the system description, covering the RPPV, ElViS and the SDEAs.
Frequently asked questions
Does a EudraVigilance submission cover Switzerland?
No. Switzerland does not participate in EudraVigilance. Swiss cases have to be submitted to Swissmedic through ElViS, separately, with their own acknowledgement.
Can we use the EU SmPC to assess expectedness?
Not for Switzerland. Expectedness is assessed against the product information approved in Switzerland. A reaction listed in the EU can be unexpected here, which changes reportability and the deadline.
Does an EU label change apply in Switzerland?
Not automatically. You submit a variation to change the Swiss product information. Until it is approved, the existing Swiss text is the reference for case assessment.
Do we follow the EURD list for our Swiss PSURs?
No. Swissmedic sets the interval for each Swiss authorisation. The EU cycle can be a useful alignment for data cuts, but the obligation and its dates are Swiss.
Is GVP applicable in Switzerland?
Not as binding law, but it is treated in practice as the state of the art. Building on GVP and adding the Swiss roles, channels and reference documents is a defensible approach.
Do we need a separate Swiss safety database?
No, and it is usually a bad idea. One database with Swiss cases flagged, Swiss expectedness assessed and ElViS acknowledgements filed is easier to run and easier to inspect than two systems that drift apart.
Do you need an RPPV in Switzerland?
We act as the qualified person responsible for pharmacovigilance, run case processing and write the PSURs for your Swiss authorisations.