Skip to main content

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

Detailed view of a RxNorm file intake process

Updated on April 23, 2021

The rules in the next few sections are shown using RXCONSO file as an example. Each RxNorm file has similar rules associated with it.

Service Package

All the RxNorm file listeners belong to HCDDS service package.


Source location for the above listener is configured through D_AppExtension data page. For more information, see Dynamic class referencing).

After all the RxNorm files are succesfully loaded, we can use the RxNorm data for drug data Search functionality.

Exception handling
As we know we are using file listeners to consume the RxNorm data files, and 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 PegaHC-DDS-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.
Below is another report, which gives the summary on processed, unprocessed, and total records corresponding to a particular file.
Users may correct the records with exceptions and import them again to prevents the data loss.

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