Arabic Pharmacovigilance Translation by a Pharmacist-Led Team
Pharmacovigilance documents carry regulatory clocks and clinical consequences. An adverse-event narrative that loses a dose, a date or a causality statement in translation is not a style problem. It is a reporting error. Lingoarabia translates safety documentation between Arabic and English with a pharmacist reading every narrative, so the clinical facts survive the language change.
Dr. Ola Siam, B.Pharm., leads the work. She has translated medical and pharmaceutical content for 17+ years, with 5.8 million medical words behind her, and pharmacovigilance reports and adverse-event documentation are part of that record.
What we translate
Safety work runs in both directions. Spontaneous reports and hospital records arrive in Arabic and must reach the global safety database in English. Aggregate reports and risk communications come the other way, from English into Arabic for the Egyptian Drug Authority (EDA), the Saudi Food and Drug Authority (SFDA) and other regional authorities.
- Individual case safety reports (ICSRs) and adverse-event narratives, Arabic to English and English to Arabic
- Source documents behind the case: discharge summaries, lab reports, prescriptions, physician and consumer correspondence
- Periodic safety update reports (PSURs) and periodic benefit-risk evaluation reports (PBRERs)
- Risk management plans (RMPs) and local RMP annexes
- Direct healthcare professional communications (DHPC letters)
- Patient safety cards, patient alert cards and educational risk-minimisation materials
- Signal assessment summaries, safety sections of SmPC and PIL updates, and local PV procedures
Arabic to English case translation
Most ICSR work we see starts as an Arabic document written under pressure: a handwritten referral, a hospital discharge note, a pharmacist’s email. The reporter uses local drug brand names, Egyptian or Gulf colloquial expressions for symptoms, and abbreviations that only a clinician recognises. A translator without a pharmacy background will render the words. A pharmacist will also recognise that “the patient took two strips” means a specific number of tablets, and will flag it rather than guess.
We keep the narrative faithful to the source, including gaps and ambiguities, and mark anything that needs a query back to the reporter. The English output is written so the case processor can code it without re-reading the Arabic.
MedDRA-consistent terminology
Reactions, indications and medical history terms are translated to match MedDRA lowest level terms wherever the source supports it, and the preferred term is suggested in a comment when the source wording is loose. Drug names follow the INN plus the local brand as reported. Dates, units, dose frequencies and lab values are checked line by line, because those are the fields that most often shift in translation.
Regional requirements
The EDA requires marketing authorisation holders in Egypt to submit ICSRs, PSURs and RMPs through its pharmacovigilance centre, and local literature and spontaneous reports frequently arrive in Arabic. The SFDA runs its own National Pharmacovigilance Centre with Arabic-language patient reporting, so Saudi cases often need Arabic to English handling on short timelines. We know the document formats these centres expect and the register they use for Arabic patient-facing safety material.
Working to regulatory timelines
Expedited reports leave little room. Our senior linguists translate 4,000 to 5,000 words a day each and review 7,000 words a day, and short ICSR batches are handled the same day they arrive when scheduled in advance. For PSURs and RMPs that run to tens of thousands of words, we agree a delivery plan at the start, deliver in sections where that helps your submission, and keep a project glossary live from the first batch.
Confidentiality is built into the process. Patient identifiers are handled under NDA, files move through encrypted channels, and we work inside your safety system or secure portal when that is how your team operates.
Process
Every safety document goes through translation by a pharmacist or medical linguist, independent revision by a second qualified linguist, and a final QA pass on numbers, dates, units and terminology. The process is ISO 17100-aligned, and you receive a revision record on request. Read more on our process and quality page.
Ask for a quote
Send a sample ICSR or the table of contents of your PSUR, with your deadline, to request a quote. We reply during working hours, Cairo time.
Frequently asked questions
Yes. Arabic to English case translation is a core part of our pharmacovigilance work. Source documents are often informal or handwritten, and a pharmacist reads every narrative so that doses, dates and reaction terms are rendered accurately rather than guessed.
We translate reaction and indication terms to match MedDRA lowest level terms where the source supports it, and we flag the suggested preferred term in a comment when the source wording is loose. Drug names follow the INN plus the reported local brand.
Short ICSR batches scheduled in advance are handled the same day they arrive. Capacity per senior linguist is 4,000 to 5,000 words a day for translation and 7,000 words a day for review. For urgent work, tell us the regulatory clock date and we plan around it.
Both. Full PSURs, PBRERs and RMPs are delivered in sections where that helps your submission, with a project glossary kept live from the first batch. Local RMP annexes and risk-minimisation materials for Egypt and the Gulf are a regular request.
Our team works to the formats and register expected by the Egyptian Drug Authority (EDA) and the Saudi Food and Drug Authority (SFDA), and we translate for submissions to the UAE Ministry of Health and Prevention (MOHAP) and other Gulf authorities.
All work is done under NDA, with files moved through encrypted channels. Where your team works inside a safety database or secure portal, we work there too, so patient data stays within your system.