> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/7-task-oriented-analytics/7.2-population-based-analytics/7.2.2-pharmacovigilance.md).
# Pharmacovigilance
Pharmacovigilance is the collection, detection, assessment, monitoring and prevention of adverse effects with pharmaceutical products. It is concerned with identifying the hazards associated with pharmaceutical products and minimizing the risk of any harm that may come to patients. An important part of pharmacovigilance is postmarketing surveillance, which monitors the safety of a pharmaceutical drug or medical device after it has been released on the market. Since drugs are approved on the basis of clinical trials, which involve relatively small numbers of people, postmarketing surveillance plays an important part in further refining, confirming or denying the safety of a drug in the general population.
Pharmacovigilance uses a number of data sources to assess and monitor the safety of licensed drugs, including clinical trial data, medical literature, spontaneous reporting databases, prescription events, electronic health records, and patient registries. Data mining of large volumes of clinical data can be used to highlight potential safety concerns. However, current mechanisms to analyze this data is often both costly and insensitive.
The availability of large datasets of richly encoded SNOMED CT data within longitudinal healthcare records can greatly assist pharmacovigilance. Where SNOMED CT is not used natively to capture clinical data, free text narrative and other code systems may be mapped to SNOMED CT to support a homogeneous approach to querying across diseases, signs and symptoms, lab results, medications, devices, procedures, allergies, adverse reactions, body sites and substances. SNOMED CT's polyhierarchy and defining relationships, which provide links between these domains provide a rich source of meaning-based information across which queries can be performed.
Many drug regulatory authorities and pharmaceutical companies currently use the Medical Dictionary for Regulatory Activities (MedDRA) to classify adverse drug events. MedDRA is an international standard adverse event classification used from pre-marketing through to post-marketing activities. However, as MedDRA was not designed to support routine clinical data collection, its penetration into clinical systems is limited. Therefore mapping from SNOMED CT to MedDRA would enable both styles of analysis and reporting to be performed from the same clinical data. The UK Medicines and Healthcare products Regulatory Agency (MHRA) is working (with input from the MedDRA Maintenance and Support Services Organization) to develop a mapping from a subset of SNOMED CT to MedDRA for this purpose.
***
Provide Feedback
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/7-task-oriented-analytics/7.2-population-based-analytics/7.2.2-pharmacovigilance.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.