Using Resources for Scientific-Driven Pharmacovigilance
- PDF / 131,104 Bytes
- 8 Pages / 498.9 x 714.33 pts Page_size
- 96 Downloads / 180 Views
CURRENT OPINION
Adis ª 2012 Springer International Publishing AG. All rights reserved.
Using Resources for Scientific-Driven Pharmacovigilance From Many Product Safety Documents to One Product Safety Master File Giovanni Furlan EU QPPV, Helsinn Birex Pharmaceuticals, Dublin, Ireland
Abstract
Current regulations require a description of the overall safety profile or the specific risks of a drug in multiple documents such as the Periodic and Development Safety Update Reports, Risk Management Plans (RMPs) and Signal Detection Reports. In a resource-constrained world, the need for preparing multiple documents reporting the same information results in shifting the focus from a thorough scientific and medical evaluation of the available data to maintaining compliance with regulatory timelines. Since the aim of drug safety is to understand and characterize product issues to take adequate risk minimization measures rather than to comply with bureaucratic requirements, there is the need to avoid redundancy. In order to identify core drug safety activities that need to be undertaken to protect patient safety and reduce the number of documents reporting the results of these activities, the author has reviewed the main topics included in the drug safety guidelines and templates. The topics and sources that need to be taken into account in the main regulatory documents have been found to greatly overlap and, in the future, as a result of the new Periodic Safety Update Report structure and requirements, in the author’s opinion this overlap is likely to further increase. Many of the identified inter-document differences seemed to be substantially formal. The Development Safety Update Report, for example, requires separate presentation of the safety issues emerging from different sources followed by an overall evaluation of each safety issue. The RMP, instead, requires a detailed description of the safety issues without separate presentation of the evidence derived from each source. To some extent, however, the individual documents require an in-depth analysis of different aspects; the RMP, for example, requires an epidemiological description of the indication for which the drug is used and its risks. At the time of writing this article, this is not specifically required by other documents. The author has identified signal detection (intended not only as adverse event disproportionate reporting, but including non-clinical, laboratory, clinical analysis data and literature screening) and characterization as the basis for the preparation of all drug safety documents, which can be viewed as different ways of presenting the results of this activity. Therefore, the author proposes to merge all the aggregate reports required by current regulations
Furlan
616
into a single document – the Drug Safety Master File. This report should contain all the available information, from any source, regarding the potential and identified risks of a drug. It should be a living document updated and submitted to regulatory authorities on an ongoi
Data Loading...
