πŸ”’ Coding of Adverse Events and Drugs: A quick-view

β€”

by

β€”

This blog covers:

  1. Analyzing Data for Data-Entry
  2. Coding of Reported Drugs and Adverse Events

Table of Contents:

  1. Introduction
  2. How to Analyze and What to Look for in the Given Data
  3. Coding of Drugs and Reported Medical conditions From The Given Data
  4. Conclusion
  5. References

Introduction

After triage and book-in the case into the database, the next step involves coding events and drugs. This process forms a crucial part of complete data entry.

So, what is complete data entry?

Complete data entry is a process requires the processor to enter all relevant details and data into the database, which is provided in the source.

This includes all the information such as reporter information, patient details, Patient medical history, suspected drug, events and so on.

πŸ“’ Recommendations: I recommend referring to three key topics we previously discussed. Firstly, he importance of triage in pharmacovigilance. Second, the step-by-step process of an effective book-in process. And third, the what is end to end of pharmacovigilance data entry.

Analyze the given data

Before proceeding with coding, it is crucial to identify the suspected drugs and adverse events.

  1. In many cases, patients may be prescribed multiple drugs, and in such situations, coders primarily focus their suspicion on our own product. However, if the report clearly indicates that our drug is not responsible for a specific event, the case should be deactivated upon confirmation.
  2. When analysing the medical history and events, it is essential to evaluate between the events and medical history of the patient. In Many instances that may cause a huge error. To learn more insights in to common errors that may possibly happen in data-entry.
  3. During follow-up cases, If you found out any errors made from previous versions through your source. Any mismatches with your current source. So you should correct the inaccuracies and ensure there are no delays.

Coding of Drugs and Events

The next step after analysing the data is to proceed with coding the events and drugs.

Coding of Suspected Drug(s)

Suspected drug:

A suspected drug is the medication associate with the Adverse Drug Reaction (ADR) as determine by the initial reporter. It is possible that there may be one or more drugs involved, based on the available information from the source.

Any remaining drugs considered as associated concomitant drugs.

The suspected drug(s) need to code using the company’s product dictionary for company drugs and the WHO Drug Dictionary (WHO DD) for non-company concomitant drugs.

πŸ“’ I suggest checking out our blog where we delve into the thorough assessment of suspected drugs and concomitant medications, and explore how concomitant drugs can become suspects themselves.

What is WHO-DD?

The WHO-DD is an international classification of medicines created by the WHO Program for International Drug Monitoring and managing by the Uppsala Monitoring Centre.

The associate will also add other information for the suspect drug which includes indication, therapy details, and action taken with the suspect drug in response to the event.

The case processor will identify and categorise the drugs provided by the primary reporter as either suspect, concomitant, or interacting. They will then code these drugs in the appropriate drug dictionaries configured in the company’s database.

Additionally, relevant information about the suspected drug, such as indication, therapy details, and any actions taken in response to the event, should also recorded.

πŸ“’ Recommendation: Explore here, If you’re curious about the diverse databases utilized in pharmacovigilance systems and their features.

Coding of Adverse Event(s)

In this step, the process of adverse events coding with using the Medical Dictionary for Regulatory Activities (MedDRA).

MedDRA is an internationally standardization of medical dictionary using for regulatory communication and evaluation of data relate to medicinal products for human use.

Keen to dive deeper into MedDRA? Explore our blog for an in-depth exploration.

  1. Structure of MedDRA Hierarchy
  2. Best practices to minimize the error in MedDRA coding

The case processor can automatically code the event term (auto code) if an exact match exists in MedDRA. If an exact match is not available, the event term is to code manually which is more appropriate. The purpose is to ensure uniformity in language across countries, companies, and regulatory bodies.

Conclusion

From the above write-up, you can delve into the conditions required for analyzing the given data before importing it into the database. Furthermore, you might uncover nuances in the coding of drugs and patient medical conditions.

We encourage you to suggest or mention any specific topics for our upcoming articles.

Feel free to comment below if anything has been overlooked in this blog.

References:
  1. ncbi.nlm
  2. WHO-Drug-Global

Disclaimer: We write this blog based on our experience and extensive knowledge, supported by references. Please note that we are not responsible for the content on the referenced websites. If you come across any misinformation or misguidance or spelling mistakes, kindly inform us promptly.



Bala Avatar

Meet Bala, the founder of Drugvigil, a service provider specializing in pharmacovigilance. He’s not only an expert in this field, but also a passionate entrepreneur who enjoys creating new opportunities and helping others grow. Despite starting from scratch, he’s determined to develop his company from the ground up. If you’re interested in his work, be sure to show your support and share his message with others.




Just a fancy image. www.drugvigil.com






Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.