Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Detailed view of a MedDRA file intake process

Updated on April 23, 2021

The rules shown in next few sections are shown using ProcessSocBaseFile file as an example. Each Hierarchical level file has similar rules associated with it.

Service Package
All the MedDRA File listeners belong to ‘MedDRACodes’ Service package.
File Listener

Source location for the above listener is configured through D_AppExtension data page. For more information, see Step 5: Dynamic Class Referencing in the PegaHC Core Layer.

Once all the MedDRA files are loaded successfully, we can leverage the MedDRA data for Search functionality.

Exception handling
As we know that we are using file listeners to consume the MedDRA data files, the possibility of something going wrong always exists. We are handling those exceptions/errors encountered while saving the RxNorm drug data. These exceptions will be caught in the exception table of class PegaHealth-Codes-Data-Exception.
Running the below report gives the information about the records with the exception message along with the record number, file name, file type.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us