Authorised EV/EVDAS proxy
Supabase and Render proxy layers are prepared for lawful institutional endpoints and credentials.
Build note · pharmacovigilance software
EudraVigilance API Workbench
A prototype for authorised EudraVigilance/EVDAS-style API access, public ADR aggregate analysis, live public FAERS API queries and exploratory disproportionality metrics.
What changed
The app now separates restricted European pharmacovigilance access from public API access. EudraVigilance remains behind an authorised proxy because there is no unrestricted public REST API. The working public API mode uses the openFDA FAERS drug adverse event endpoint through a Supabase Edge Function.
Live public API
The public API app queries the openFDA FAERS drug-event endpoint through Supabase pv-public-api.
Disproportionality
ROR and PRR are exploratory screening statistics, not incidence, causality or clinical advice.
Regulatory boundary
EudraVigilance is the European system for managing and analysing information on suspected adverse reactions. EMA publishes public European suspected adverse reaction reports through adrreports.eu, while access to richer EudraVigilance data is governed by the access policy.
The correct public architecture is therefore: official European public reports as public source, open public pharmacovigilance APIs where they exist, and authorised proxy mode only where lawful credentials exist.