What Goes Into the Union Pharmacovigilance Database: Veterinary Reporting Scope

Veterinary pharmacovigilance covers much more than an animal that reacts badly to a product. Under Regulation (EU) 2019/6, the Union Pharmacovigilance Database is the single place where a wider set of events must be recorded, and holders need collection processes that capture all of them.

The reporting duty

Marketing authorisation holders must record suspected adverse events in the Union Pharmacovigilance Database under Article 73 of the Regulation. National authorities such as Ireland’s HPRA set out in their guidance what this includes, and the detailed practice is in the VGVP module on collecting and recording adverse events and in the EVVet user documentation.

The categories to capture

  • Unexpected or harmful responses in animals after use of a veterinary medicine.
  • Lack of efficacy, where a product fails to work as expected when used correctly.
  • Environmental incidents linked to a veterinary medicine.
  • Harmful reactions in humans exposed to the product.
  • Residues in food above legal limits, including after the withdrawal period.
  • Suspected transmission of infectious agents through a medicine.
  • Reactions in animals to medicines authorised for human use.

Human-authorised products used in animals

When a human medicine is reported in an animal, EMA best practice asks that the product be flagged with “(H)” after its name in the database. This simple convention allows later analysis of off-label use and is easy to get wrong when intake is handled by several people.

Outsourced collection

If a holder works with a third party, explicit procedures and detailed agreements must ensure that suspected events are collected and recorded as the law requires. A call centre or distributor that receives a farmer’s complaint is in effect part of your pharmacovigilance system.

Practical checks

  • Train customer service, sales and technical teams to recognise the categories above, especially lack of efficacy and human exposure.
  • Include quality complaints in the review, since many have a safety dimension.
  • Test the path from a field call to a recorded case, with timing.
  • Check that contracts with distributors define who receives, forwards and records reports.

Embedding the process

Reporting is only as reliable as the first conversation. Written procedures should say who may receive a report, how quickly it must be passed to pharmacovigilance and what minimum information is needed to make it a valid case. Periodic checks, such as sampling call logs or distributor complaints, show whether events are being missed. Where products are sold by partners, include reporting clauses and test them with sample cases.

  • Define a clear internal clock from first receipt to recording.
  • Log all contacts that mention product performance or health problems.
  • Audit partners at a frequency based on risk.

How PQRA helps

PQRA can map your collection channels, review contracts with partners for pharmacovigilance clauses, write or update intake procedures and run mock case-handling exercises that test what really reaches the database.

Questions about this topic? Contact PQRA to discuss your veterinary portfolio.

CATEGORIES:

Uncategorized

Tags:

No responses yet

Αφήστε μια απάντηση

Η ηλ. διεύθυνση σας δεν δημοσιεύεται. Τα υποχρεωτικά πεδία σημειώνονται με *