This blog covers:
- The concept of case merging
- Conditions that apply when merging cases
- Key takeaways from the case merging process
Table of Contents:
- Introduction
- Merging of cases: Definition
- Key Factors to Consider Merging Cases
- Key Takeaways
- Conclusion
Introduction
In this comprehensive blog, we will delve into the nuances and criteria that determine when cases need merging.
In one of our previous article, we explored what is a duplicated case and why merging is necessary.
Here, we take a deeper look at the key factors that drive the need for merging cases and when it becomes essential.
Merging of Cases: Definition
In pharmacovigilance, case merging refers to the process of identify duplicate instances related to the same patient and merge into a single case.
This involves identifying and combining the relevant details, while determining which information is redundant or unnecessary and should be excluded from the final case.
“Just as duplicate DNA strands seamlessly merge in nature, we handle case merging with the same precision and sophistication—offering bespoke services through Drugvigil.”
Key Factors to Consider Merging Cases
Below are certain conditions to consider before and during the case merging process:
- Identifying the Right Duplicates: The first step before merging is to identify the right duplicates. (To learn more…)
- Effective Management of Duplicate Cases: The management of duplicates through the process of merging and deactivation.
- Same Patient, Same Information: In general, multiple cases involving the same patient and the same details repeated are often duplicates. For example, an adverse event might be processed in multiple cases for the same patient, but it should be consolidated into one case.
- Non-Duplicative Information: Meanwhile certain information that repeated in multiple cases are not duplicates. For instance, patient medical history, reporter details, and patient demographics may be consistent across cases but are not grounds for merging.
- Unnecessary Baby Cases: Unnecessary baby cases are registered, which may need to be reviewed before merging.
- Merging Exact Duplicates: Several cases that are exact duplicates can be merged into a single case.
- Separate Cases for Certain Events: Some specific adverse events require individual cases and those are not duplicates. This may depend on product-specific guidelines and the temporal relationship between events.
Once all these conditions have been checked and confirmed, the identified duplicates can be merged into one master case.
Key Takeaways
Merging is a crucial step in managing duplicates.
Nullification (deactivation) of cases is necessary once duplicates are merged.
Ensure that the right duplicates are identified and merged, before deactivating the case.
Never merge cases without a thorough review and conclusion.
During merging, ensure never missing of any significant information to the master case, including sources—unless it is a true duplicate.
Merging and deactivation aren’t just for duplicates; sometimes, many unnecessary booked individual cases.
Conclusion
This blog provides an overview of the merging process and the criteria involved. While merging is essential for managing duplicates to keep regulatory workflow clean.
This discussion is a brief introduction; a more detailed review of the merging process would be beneficial.
We welcome your valuable comments and feedback. If you have insights or think there are areas that need further exploration, leave a comment below and don’t forget to share!
Leave a Reply