Brodalumab Pharmacovigilance Knowledge Assessment

Maintain documented links among case narratives, medical assessments, follow-up, signal evaluations, quality interfaces and governance decisions Store only the final causality category and delete the supporting source information Use one unstructured exposure field for all products and treatment regimens Separate safety cases from medical-information and quality systems so that each function works independently

Exact product and presentation, batch, dose, route, administration date, treatment phase and relevant storage or preparation details Only the active-substance name and the date on which the adverse event was reported The patient's preferred method of communication and unrelated demographic details Only the number of doses prescribed, without administration dates or product identification

The regimen makes administration timing, treatment phase, injection circumstances and interruptions important elements of case reconstruction The route makes batch and presentation information unnecessary The induction phase has no relevance to adverse-event chronology Subcutaneous administration means that acute reactions cannot be considered in pharmacovigilance

It may support a dechallenge signal, but interpretation can be confounded by rescue treatment, other medication changes, persistent biological activity or natural fluctuation It proves that brodalumab caused the event in every case It has no value because treatment interruption is never relevant to causality It establishes a positive rechallenge because the patient improved after stopping treatment

A patient develops neutropenia after treatment, but a recently introduced concomitant medicine is also known to cause neutropenia A patient develops an event after treatment and no other information is available A patient improves after receiving treatment for the event A patient has a documented administration date for brodalumab

Establish treatment intent and baseline status, reconstruct exposure, characterise onset and evolution, document findings and outcome, then weigh causality Assign causality from the preferred term, then collect exposure information only if the event is serious Start with the suspected mechanism and omit baseline disease because it may bias the assessment Begin with aggregate signal results and use them as the sole basis for the individual case conclusion

Different terms may represent one syndrome, while the same term may include clinically different mechanisms or phenotypes Preferred terms are never permitted in pharmacovigilance databases Counts are sufficient only when the event is unrelated to the mechanism of action Preferred-term counts automatically adjust for background disease and exposure denominators

The key question is whether the evolving balance remains acceptable for the authorised population under the applicable conditions of use Any increase in adverse-event reports means that the benefit-risk balance is no longer acceptable Benefit-risk evaluation should consider safety events without regard to treatment exposure or disease burden The presence of labelled adverse reactions is sufficient to determine that benefits outweigh risks

2015 2017 2019 2021

State the denominator limitation and avoid presenting a precise-looking rate that implies unsupported certainty Estimate an exact denominator from the number of reports and present the resulting rate without qualification Discard all reports because a rate cannot be calculated with certainty Treat the reporting rate as an incidence rate without further explanation