This blog highlights:
- The challenges commonly faced by coders when coding with MedDRA.
- The common causes that may impact regulatory submissions.
- Strategies for effectively handling these challenges.
Table of Contents
Introduction
MedDRA coding is pivotal in case processing, yet its complexity often poses challenges. While selecting a code may seem straightforward, ensuring it’s the right and most suitable one is often arduous.
Despite clear reporting, erroneous code selection remains a common issue.
Moreover, the prevalence of complex and confusing verbatim further complicates matters. So, how do we navigate this intricate landscape effectively?
“In the realm of MedDRA, challenges are not obstacles, but rather opportunities for growth, precision, and the advancement of pharmacovigilance.”
Hurdles in MedDRA Coding
Common Problems Encountered by Medical Coding Experts:
- Unclear Verbatim Terms
- Illegible Verbatim Terms
- Spelling Errors
- Usage of Abbreviations
- Recording Multiple Signs and Symptoms as Separate Events that may lead to diagnosis
- Lack of Mention of Normal Ranges for Lab Data
- Absence of Units of Measurement for Lab Data
- Recording Multiple Medical Concepts Together, Requiring Splitting for Coding
- Lack of Specificity in Recorded Events, such as Unspecified Site for Ulcers
- Recording Surgical Procedures and Injury Causes Without Clarification
- Reporting Medication Terms Without Specifying Allergic Reactions or Outcomes.
Examples of Confused Scenarios
- “Pt prsntd wth c/o abdmnl pn, hst fnd no ecchymosis, trmt prcdr stppd d/t decrn ptn’t cond.”
This might be deciphered as: “Patient presented with complaint of abdominal pain, history found no ecchymosis, treatment procedure stopped due to decrease in patient’s condition.”
- Some verbatim only report signs and symptoms without mentioning a clear diagnosis. This can lead to confusion, especially during follow-up (FU) reports. For example, in many pneumonia cases, only symptoms like cough and a runny nose are reported. Consequently, during FU reports, the case scenario may change dramatically. Initially, signs and symptoms coded as individual events, but later, the primary event could be identified as pneumonia.
- Some cases miss reporting the normal range of lab data or the units of measurements, complicating the capture of significant lab data for an event.
Downsides of Often Faced Obstacles
- Frequently Dealing with Action Items
- Cases Frequently Rerouted
- Regulatory Submissions Delayed in Crucial Pending Inquiries
- This Could Altered the Entire Case Scenario in Follow-up Reports
- Frequently Overlooked in Capturing Events
Efficient Management of Such Scenarios
- Raise an inquiry if the case is not urgent.
- Consult with a medical reviewer and finalize the data until clarity is obtained from follow-up reports.
- Google can assist with a few cases.
- Refrain from capturing or referencing any additional information unless it has been officially reported, even if you are confident about it. Wait for follow-up reports and process the information strictly as reported.
- Understand the verbatim, which may include signs and symptoms, and associate/connect/correlate/hierarchically link them with the appropriate events.
Wrap-up
This write-up specifically discusses the situations that have been hectic and time-consuming to sort out, which may lead to facing action items.
However, it’s important to note that the responsibility lies with the individual who wrote the report, and not within your control.
Nonetheless, you can reduce the chances of error by effectively handling these frequently encountered situations.
We hope this blog enlightens your thoughts, especially if you are a beginner. Feel free to comment below if anything has been overlooked or if you find any mistakes. Additionally, if you wish to add extra information, your input is welcomed.
Leave a Reply