Discover More Tips and Techniques on This Blog

MedDRA and WHODrug Coding

Though there are other Coding dictionaries available along with MedDRA (ex: COSTART and WHOART), MedDRA dictionary is typically used in the US for Adverse Events coding.

AE\MedDRA coding is not the SAS programmers work; it is usually done by medical coder or database programmer. Coding basically involves a process of finding a dictionary term that matches the verbatim term reported on the CRF, and getting the other related dictionary derived variables useful for the analysis like System Organ Class (SOC), Preferred Term (PT) and Lowest Level Term (LLT), etc.

Some times this process may take more time than expected, because Misspellings and other differences would delay the process of coding. In that case, person responsible for coding has to look for the dictionary term that which is the best possible match from the MedDRA dictionary.

So the question here comes is what SAS programmer can do in this process.

Here is the Answer….

SAS programmer has to work hard to make this process successful. In other words he is also a key player in this game.

SAS Programmer provides a list of reported AE terms on the CRF to the medical coder in a flat file/excel file, who then search for a best possible match and related terms for AE term of CRF in the MedDRA dictionary. He then enters them in the supplied flat/excel file and returns back to the SAS programmer.

The next SAS programmer duty is to assign the Dictionary derived Term, SOC, LLT and PT to the AE Terms in the AE dataset by merging. (Use Proc SQL or Simple Merge)

MedDRA dictionary gets updated twice a year, so it is important to be aware of the version used for the coding.

If the data is clean (Assuming that there are no misspelling of AE terms or other problems then MedDRA coding is easy…. What you have to do is locate the MedDRA SAS dataset and then merge the MedDRA dataset with the AE dataset using the preferred term.
















Making Code Review Painless

ABSTRACT:
Code review is an essential step in the development of concise and accurate SAS® programs. It is a required verification step in performing validation in a regulated environment. This paper will present techniques and a macro that can be freely downloaded to automate this task. The %coderev macro will perform many of the common tasks during a code review including:

1. Spell checking headers and comments
2. Reviewing all input and output datasets of the program
3. Comparing defined macro variables versus macro variable usage
4. Checking for multiple macro calls that are not in a macro library
5. Evaluating hard code logic
6. Evaluating sort order of all datasets

These tasks are normally performed by an independent reviewer instead of the original programmer. By automating the tasks, the code review process will ensure that the smallest mistake can be captured through reports to ensure the highest quality and integrity. What normally is a dreaded task can now be done with ease.
Thanks to Sy Truong, Meta-Xceed, Inc, Fremont, CA

Disclosure:

In the spirit of transparency and innovation, I want to share that some of the content on this blog is generated with the assistance of ChatGPT, an AI language model developed by OpenAI. While I use this tool to help brainstorm ideas and draft content, every post is carefully reviewed, edited, and personalized by me to ensure it aligns with my voice, values, and the needs of my readers. My goal is to provide you with accurate, valuable, and engaging content, and I believe that using AI as a creative aid helps achieve that. If you have any questions or feedback about this approach, feel free to reach out. Your trust and satisfaction are my top priorities.