An individual case safety report is only as useful as its weakest field. Between the first email from a reporter and the E2B(R3) file that reaches EudraVigilance sit a dozen decisions, and most inspection findings on case quality trace back to one of them.
What makes a case valid
Under EU good pharmacovigilance practice, a report becomes a valid ICSR when four minimum elements are present: an identifiable reporter, an identifiable patient, at least one suspected medicinal product and at least one suspected adverse reaction. “Identifiable” does not mean named; initials, age, sex or a reference number can be enough. Missing any one element means the case is not yet reportable, but the company must still keep the information and make reasonable efforts to obtain what is missing.
The processing chain
A well-run case moves through defined steps, each with its own control:
- Receipt and triage: log every report, whatever the channel, and establish the date of receipt.
- Duplicate check: search before creating a new case, so that two reporters of one event do not become two cases.
- Data entry: capture the source data faithfully, including dates, doses, indications and outcomes.
- Coding: medical terms, products and indications are coded consistently.
- Narrative and medical review: a clear account of the chronology, followed by seriousness and causality assessment.
- Quality control and submission: a check against the source before the file is sent.
- Follow-up: targeted queries, with each new piece of information documented.
Why E2B(R3) raises the bar
E2B(R3) is the ICH format for transmitting ICSRs, and it has been the format used for EudraVigilance submissions in the EU since November 2017. It is built on an ISO standard for ICSR transmission and is far more structured than its predecessor. More information has a dedicated field, relationships such as parent and child cases can be expressed, and product information is designed to fit identification standards derived from ISO IDMP. For the processor this means less free text and more discipline. A case that was acceptable as a narrative blob in the old format may now fail validation, or pass it while carrying poor data.
Common weak points
- Dates recorded at the wrong precision, or onset dates that follow the report date.
- Suspect and concomitant products confused, or batch numbers lost.
- Narratives that restate the data fields rather than explaining the clinical sequence.
- Follow-up information received but not recognised as new information.
- Different coding of the same reported term by different processors.
These are process problems, not system problems, and they are cheap to find through periodic quality review of a sample of closed cases.
How PQRA helps
PQRA reviews case processing procedures, work instructions and quality control checks against current EU expectations, and supports the set-up and oversight of outsourced case processing. We can also run a sample-based case quality review so that you see where errors cluster before an inspector does.
Contact PQRA to discuss your pharmacovigilance system, in Greece and across the EU.


No responses yet